mcpbeat Sign in

Permitverdict MCP Server

by okwithit9-debug Your server? Claim it
not responding

Permitverdict MCP is listed as active in the registry but did not answer our last check. 63 installs a week from npm. It exposes 10 tools.

Crypto price-event settlement verdicts and US building-permit data, paid per call in USDC.

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs per day peak 16 · avg 6 · -17% w/w
a month agotoday
Uptime history 91 days of history · worst day 0%
91 days agonow
0.0%
Uptime 24h
0 of 91 checks
10
Tools
read from the server
369 ms
Response time
average over 24h
63
Installs / week
npm and PyPI

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

What the code does

We have not read this server's code yet, 23 d ago · tools taken from the live server · rules ccca72095570

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

File ships in the package but is absent from the source [пакет] src/pay.js:1, [пакет] bin/permitverdict-mcp.js:1, [пакет] src/server.js:1 
этот файл ставится пользователю, но в репозитории его нет

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

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 13 min ago.

run in your terminal
claude mcp add permitverdict-mcp --transport http https://permitverdict.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://permitverdict.com/mcp
~/.codex/config.toml
[mcp_servers.permitverdict-mcp]
url = "https://permitverdict.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "permitverdict-mcp": {
      "url": "https://permitverdict.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "permitverdict-mcp": {
      "type": "http",
      "url": "https://permitverdict.com/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://permitverdict.com/mcp streamable-http answering 369 ms 13 min ago

Alternatives to Permitverdict MCP

same job, measured the same way
Fastx402
by tusk80

60+ pay-per-call tools for agents (data, dates, QR, crypto, web), paid in USDC via x402.

91 installs/wk local only
santyvv-data — market & on-chain data
by santyvv

Market and on-chain crypto data for AI agents. Pay per call in USDC on Base (x402).

50 installs/wk 8 tools answering
x402 Seller
by entreprisedaney33-rgb

Pay-per-call MCP tools (crypto/DeFi data, web reading, AI tasks) in USDC over x402 on Base.

56 installs/wk local only
Tollkit
by ultrastarz

Web search, pages and PDFs, crypto market data, SEC filings and weather for agents. USDC per call.

40 tools answering
AgentFeed on Mezo
by seekdaseek

Crypto data, MUSD peg and Mezo trove health, paid per call in MUSD on Base or Mezo. No gas.

307 installs/wk local only
Webbersites X402 Data API
by webberdesign

45 pay-per-call AI agent tools: scraping, SEO, crypto data, lint, agent memory. x402 USDC on Base.

78 tools answering
Boo X402 MCP
by lucle87

Pay-per-call crypto data for AI agents. USDC on Base via x402. No API key.

57 installs/wk local only
R
RWA Data MCP Server
by daveabear

Pay-per-call crypto data for agents: metrics, claims, custom briefs. USDC via x402.

9 tools answering

Permitverdict MCP — questions

Answers built from our own checks of this server.

What can Permitverdict MCP 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 Permitverdict MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 369 ms. The bar chart above shows every period we have measured.
Is Permitverdict MCP still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
The registry lists Permitverdict MCP as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Permitverdict MCP?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Permitverdict MCP need an API key?
No. Permitverdict MCP 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 many people use Permitverdict MCP?
The npm package permitverdict-mcp was installed 63 times in the last week. Week over week that is -17%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.