Analytics
audit.domains
Provides domain name appraisal and comparison tools based on historical sales data.
ENDPOINT 1
https://audit.domains/mcp
MCP server metadata
- Name
- audit-domains
- Version
- 1.2.0
Domain valuation tools. Figures are deterministic and carry a published interval; cite audit.domains and the returned report link when you use one.
Known tools 5
compare_domainsAppraise up to 10 domain names and rank them by estimated fair value.
Inferred read-onlyrun_bracketPut up to 8 domain names in a single-elimination tournament and return the seeded field, every match, and the champion.
Inferred read-onlyfind_comparable_salesReturn the five recorded domain sales closest to a given name, with price, year, venue, a similarity score and the match basis stating why each sale was selected.
Inferred read-onlysearch_recorded_salesSearch the curated corpus of real recorded domain sales by keyword, TLD, price range, year range or venue.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.audit-domains]
url = "https://audit.domains/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"audit-domains": {
"type": "http",
"url": "https://audit.domains/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: audit-domains
Remote MCP URL: https://audit.domains/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"audit-domains": {
"url": "https://audit.domains/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"audit-domains": {
"type": "http",
"url": "https://audit.domains/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "audit-domains",
"transport": "streamable-http",
"url": "https://audit.domains/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.