General Tools
permitverdict.com
Provides general-purpose tools through the Model Context Protocol.
ENDPOINT 1
https://permitverdict.com/mcp
MCP server metadata
- Name
- permit-intelligence
- Version
- 0.5.0
Known tools 10
list_jurisdictionsList cities covered by the Permit Intelligence API, with pricing and payment details.
Potential side effectsverify_decisionRe-resolve an attested settlement against the price venues right now and report whether it still holds: CONFIRMED, CHANGED or INDETERMINATE.
Inferred read-onlyattest_price_eventSettlement verdict plus a citable record: a signed decision_id, an integrity hash over the evidence, and every candle that determined the outcome.
Inferred read-onlyget_permit_verdictAddress-level building-permit intelligence for a covered city: normalized permit history + activity signals + a decision-ready verdict with cited public records.
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.permit-intelligence]
url = "https://permitverdict.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"permit-intelligence": {
"type": "http",
"url": "https://permitverdict.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: permit-intelligence
Remote MCP URL: https://permitverdict.com/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": {
"permit-intelligence": {
"url": "https://permitverdict.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"permit-intelligence": {
"type": "http",
"url": "https://permitverdict.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "permit-intelligence",
"transport": "streamable-http",
"url": "https://permitverdict.com/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.