Permit Verdicts MCP server
io.github.okwithit9-debug/permit-verdictsokwithit9-debugstreamable-httpv0.3.0Scanned
Building-permit verdicts by address, with cited records. SF, Seattle, Austin, NYC. Pay per call.
10 tools: 1 do something that can't be undone, 3 change things and 6 only read.
- Reads private data · 0
- Reads text others write · 10
- Can send data out · 1
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Permit Verdicts MCP server can do
The Permit Verdicts MCP server is published by the GitHub account okwithit9-debug. It has 10 tools. It can do things that cannot be undone, such as sending, paying or publishing (attest_price_event) and create or change data (3 tools: check_permit_activity, decode_decision_id and verify_decision), but cannot delete data. 6 tools only read.
10 tools bring in text other people can write (list_jurisdictions, check_permit_activity, find_active_projects and 7 more); 1 tool can send data out of your system (attest_price_event).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 21, 2026, version 0.3.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
10 tools
Can't be undone 1Claude Code: ask
attest_price_eventSettlement verdict plus a citable record: a signed decision_id, an integrity hash over the evidence, and every candle that determined the outcome.Reads text others writeCan send data out1 finding
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "attest_price_event" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.
Description, as the server wrote it 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.
Annotations the server declares
- title: Attested settlement record
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Changes things 3Claude Code: ask
check_permit_activityFREE.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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
Annotations the server declares
- title: Check permit activity (free)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
decode_decision_idFREE.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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
Annotations the server declares
- title: Decode and authenticate a decision_id (free)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
verify_decisionRe-resolve an attested settlement against the price venues right now and report whether it still holds: CONFIRMED, CHANGED or INDETERMINATE.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Verify an attested settlement
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 6Show 6 read-only tools
find_active_projectsFREE PREVIEW (5 results).Reads text others writeNo findings
Why it is in this group
- The name "find_active_projects" says "find": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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
Annotations the server declares
- title: Find active construction projects (free preview)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_crypto_spotLive cross-venue spot price with venue agreement and spread.Reads text others writeNo findings
Why it is in this group
- The name "get_crypto_spot" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Cross-venue spot price
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_permit_verdictAddress-level building-permit intelligence for a covered city: normalized permit history + activity signals + a decision-ready verdict with cited public records.Reads text others writeNo findings
Why it is in this group
- The name "get_permit_verdict" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get permit verdict for an address
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
list_jurisdictionsList cities covered by the Permit Intelligence API, with pricing and payment details.Reads text others writeNo findings
Why it is in this group
- The name "list_jurisdictions" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it List cities covered by the Permit Intelligence API, with pricing and payment details. Free. Full paid feeds for humans: https://permitverdict.com/pricing
Annotations the server declares
- title: List covered cities
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
list_settlement_assetsFREE.Reads text others writeNo findings
Why it is in this group
- The name "list_settlement_assets" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it FREE. Which crypto assets, venues, operators and modes the settlement oracle supports, plus pricing. Full paid feeds for humans: https://permitverdict.com/pricing
Annotations the server declares
- title: List settlement oracle coverage (free)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
resolve_price_eventSettlement verdict for a crypto price event.Reads text others writeNo findings
Why it is in this group
- The name "resolve_price_event" says "resolve": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Resolve a crypto price event
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write10
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:09 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://permit-api-production-7375.up.railway.app/mcp: tools/list returned 10 tools to an anonymous client, including attest_price_event (irreversible), check_permit_activity (write), decode_decision_id (write), verify_decision (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "attest_price_event" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.3.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http permit-verdicts https://permit-api-production-7375.up.railway.app/mcpclaude mcp add --transport http permit-verdicts https://permit-api-production-7375.up.railway.app/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__permit-verdicts__list_jurisdictions",
"mcp__permit-verdicts__find_active_projects",
"mcp__permit-verdicts__list_settlement_assets",
"mcp__permit-verdicts__resolve_price_event",
"mcp__permit-verdicts__get_crypto_spot",
"mcp__permit-verdicts__get_permit_verdict"
],
"ask": [
"mcp__permit-verdicts__check_permit_activity",
"mcp__permit-verdicts__decode_decision_id",
"mcp__permit-verdicts__verify_decision",
"mcp__permit-verdicts__attest_price_event"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as permit-verdicts. Review it before you use it.
Capability tags behind 10 rules
- mcp__permit-verdicts__list_jurisdictions untrusted-input
- mcp__permit-verdicts__check_permit_activity untrusted-input
- mcp__permit-verdicts__find_active_projects untrusted-input
- mcp__permit-verdicts__list_settlement_assets untrusted-input
- mcp__permit-verdicts__resolve_price_event untrusted-input
- mcp__permit-verdicts__get_crypto_spot untrusted-input
- mcp__permit-verdicts__decode_decision_id untrusted-input
- mcp__permit-verdicts__verify_decision untrusted-input
- mcp__permit-verdicts__attest_price_event untrusted-input, outbound
- mcp__permit-verdicts__get_permit_verdict untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.okwithit9-debug/permit-verdicts/verify?hash=ade9e716cca787b8cef5070e94c9284d55f33280b04b36abe8e95132ec1b25f3" | jq -e '.changed == false'Pinned hash ade9e716cca7, from Nov 21, 2026, 01:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.okwithit9-debug/permit-verdicts/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.okwithit9-debug/permit-verdicts)Source: MCP Registry. Synced Oct 21, 2026, 18:42 UTC.
Permit Verdicts MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Permit Verdicts MCP server safe?
- No scan can promise that. What its definitions show: 10 tools, 4 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Permit Verdicts MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Permit Verdicts MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: attest_price_event.
What tools does the Permit Verdicts MCP server have?
- 10 tools: 1 irreversible, 3 write, 6 read. attest_price_event, check_permit_activity, decode_decision_id, verify_decision, list_jurisdictions, find_active_projects, list_settlement_assets, resolve_price_event and 2 more.
Does the Permit Verdicts MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Permit Verdicts MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): attest_price_event.
Has the Permit Verdicts MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.