mcpbeat Sign in

Permit Verdicts MCP Server

answering

Permit Verdicts is answering right now. Last checked moments ago. It exposes 10 tools.

Building-permit verdicts by address, with cited records. SF, Seattle, Austin, NYC. Pay per call.

Uptime history 50 days of history · worst day 99%
50 days agonow
100.0%
Uptime 24h
92 of 92 checks
10
Tools
read from the server
352 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 5

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 August 2026. No other catalogue keeps this.

9 Aug 5 tool descriptions were rewritten check_permit_activity, decode_decision_id, find_active_projects and 2 more

Nothing serious here today

Today is the operative word: we check Permit Verdicts every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add permit-verdicts --transport http https://permit-api-production-7375.up.railway.app/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "permit-verdicts": {
      "url": "https://permit-api-production-7375.up.railway.app/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.permit-verdicts]
url = "https://permit-api-production-7375.up.railway.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "permit-verdicts": {
      "url": "https://permit-api-production-7375.up.railway.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "permit-verdicts": {
      "url": "https://permit-api-production-7375.up.railway.app/mcp"
    }
  }
}

Available tools 10

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

permit
check_permit_activity
FREE. Quick check on whether a street address has building-permit activity on record: how many permits, how many are open, and when the last activity was. No permit detail and no verdict — use get_permit_verdict for those. Full paid feeds for humans: https://permitverdict.com/pricing
get_permit_verdict
Address-level building-permit intelligence for a covered city: normalized permit history + activity signals + a decision-ready verdict with cited public records. Paid: $2.00 in USDC on base via x402.
active
find_active_projects
FREE PREVIEW (5 results). Recently permitted construction projects in a covered city, filtered by declared budget. Use feed='investor' instead to surface expired and abandoned permits (stalled projects, often motivated owners). Full paid feeds for humans: https://permitverdict.com/pricing
attest
attest_price_event
Settlement verdict plus a citable record: a signed decision_id, an integrity hash over the evidence, and every candle that determined the outcome. Use this when the answer may later have to be defended to a counterparty, not when you just need to know. KEEP THE decision_id — it is self-contained, so anyone you show it to can authenticate it for free and re-check it for $0.02 without you supplying anything else. Paid: $0.25 in USDC via x402.
crypto
get_crypto_spot
Live cross-venue spot price with venue agreement and spread. A wide spread means venues disagree and any settlement in that range is contestable. Paid: $0.01 in USDC via x402.
decode
decode_decision_id
FREE. Read what a Permit Verdict decision_id claims and check whether we actually issued it. The id is signed by the same wallet that receives payment, so forgery and after-the-fact editing are both detectable. Needs no payment. This tells you the record is genuine; it does NOT tell you the verdict is still correct — use verify_decision for that. Full paid feeds for humans: https://permitverdict.com/pricing
jurisdictions
list_jurisdictions
List cities covered by the Permit Intelligence API, with pricing and payment details. Free. Full paid feeds for humans: https://permitverdict.com/pricing
resolve
resolve_price_event
Settlement verdict for a crypto price event. Answers 'did this asset trade or close above/below a threshold during a window?' with YES/NO/DISPUTED/UNRESOLVED, per-venue evidence from Hyperliquid, Coinbase and Kraken, and stated confidence. (Binance is configured but blocks this host's region; it is reported unavailable rather than silently counted.) Use mode='close' when a market settles on candle closes and mode='touch' when any intrabar print counts — they give different answers and that difference is the most common settlement dispute. Paid: $0.05 in USDC via x402.
settlement
list_settlement_assets
FREE. Which crypto assets, venues, operators and modes the settlement oracle supports, plus pricing. Full paid feeds for humans: https://permitverdict.com/pricing
verify
verify_decision
Re-resolve an attested settlement against the price venues right now and report whether it still holds: CONFIRMED, CHANGED or INDETERMINATE. Call this whenever someone hands you a decision_id you are about to rely on — an attestation proves what was said at the time, but only a fresh resolution proves it is still true. Exchanges revise candle history, and a venue that was unreachable at issue time may answer differently now. Paid: $0.02 in USDC via x402 — cheaper than resolving fresh because you are checking someone else's answer rather than buying a new one.

Endpoints

URLTransportStateLatencyChecked
https://permit-api-production-7375.up.railway.app/mcp streamable-http answering 372 ms 0 min ago

Alternatives to Permit Verdicts

same job, measured the same way
O
Nsgoods MCP
by nsgoods

MCP server for the nsgoods x402 oracle suite: signed pay per call verdicts, with free previews.

50 installs/wk local only
Ausca
by ausca

Pay-per-call APIs and MCP services for agents, no accounts or keys, with verifiable receipts.

254 installs/wk 14 tools answering
Odoo Pulse
by minhhq-a1

An AI business analyst for Odoo ERP (18+) — one-call reports with verdicts, over MCP

234 installs/wk local only
Ranch
by ranch

Read and write cattle and sheep records with farm-scoped, revocable access.

113 installs/wk local only
SourcePilot Research
by kduailabs

Pay-per-call web research with citations for AI agents, billed in USDC on Base via x402.

local only
Pageaudit
by pageaudit

Technical SEO audit with the ready-made fix for each finding. Pay per call via x402 or credit.

18 tools answering
Agentpay Gateway MCP
by rumblingb

Centralized API gateway routing to MCP servers with per-call billing

local only
MCP Gauge
by changchinfu

Verify official facts with Bitcoin-anchored proof. 180+ signals, x402 pay-per-call.

5 tools answering

Permit Verdicts — questions

Answers built from our own checks of this server.

What can Permit Verdicts do?
It exposes 10 tools, read directly from the server on our last check. Among them: attest_price_event, check_permit_activity, decode_decision_id, find_active_projects, get_crypto_spot, get_permit_verdict and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Permit Verdicts working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 352 ms. The bar chart above shows every period we have measured.
How do I connect Permit Verdicts?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Permit Verdicts need an API key?
No. Permit Verdicts completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Permit Verdicts?
It answers our handshake in 352 ms on average, which is faster than 47% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.