Mmcp.market

Permit Verdicts MCP server

by okwithit9-debug·io.github.okwithit9-debug/permit-verdicts·v0.3.0

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

C67/100grade C
What users say
No reviews yet
Be the first
Safety scan
C67/100

full report

Adoption
New

Little public usage data yet

Reviews

Write one

Nobody has reviewed Permit Verdicts yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Permit Verdicts tools (10)

write = sends, deletes, buys or posts
  • attest_price_eventFree

    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.

  • check_permit_activityFree

    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

  • decode_decision_idFree

    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

  • find_active_projectsFree

    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

  • get_crypto_spotFree

    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.

  • get_permit_verdictFree

    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.

  • list_jurisdictionsFree

    List cities covered by the Permit Intelligence API, with pricing and payment details. Free. Full paid feeds for humans: https://permitverdict.com/pricing

  • list_settlement_assetsFree

    FREE. Which crypto assets, venues, operators and modes the settlement oracle supports, plus pricing. Full paid feeds for humans: https://permitverdict.com/pricing

  • resolve_price_eventFree

    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.

  • verify_decisionFree

    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.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

1 low
  • Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 738ms20/20
  • Tool poisoning10 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenanceno repository listed3/15
  • Maintainer identityno repository or website to verify2/10

Findings (1)

  • lowNo source repository listedmaint.no-repo
Overall 67/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

Install directly

claude mcp add --transport http permit-verdicts https://permit-api-production-7375.up.railway.app/mcp
Add to Cursor

Permit Verdicts: common questions

Is Permit Verdicts MCP server safe?
With care: it is graded C, so read the findings first (67/100). Read the Permit Verdicts safety report
How do I install Permit Verdicts?
It runs remotely at permit-api-production-7375.up.railway.app. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Permit Verdicts need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Permit Verdicts maintained?
The latest release is v0.3.0.
Is Permit Verdicts up?
100% of our last 20 checks got an answer. We check remote servers about four times a day.

More from okwithit9-debug