io.github.okwithit9-debug/permitverdict-mcp
NPM · PERMITVERDICT-MCP · 2 COMPONENTS · SCANNED SEP 21
Crypto price-event settlement verdicts and US building-permit data, paid per call in USDC.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 114 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to okwithit9-debug/permitverdict-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 44 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1414 tokens (~128/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.okwithit9-debug/permitverdict-mcp server?
io.github.okwithit9-debug/permitverdict-mcp runs locally as an npm package, launched with npx -y permitverdict-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · permitverdict-mcp
claude mcp add okwithit9-debug-permitverdict-mcp -- npx -y permitverdict-mcp
{
"mcpServers": {
"okwithit9-debug-permitverdict-mcp": {
"command": "npx",
"args": [
"-y",
"permitverdict-mcp"
]
}
}
} {
"servers": {
"okwithit9-debug-permitverdict-mcp": {
"command": "npx",
"args": [
"-y",
"permitverdict-mcp"
]
}
}
} codex mcp add okwithit9-debug-permitverdict-mcp -- npx -y permitverdict-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"okwithit9-debug-permitverdict-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"permitverdict-mcp"
],
"enabled": true
}
}
} openclaw mcp add okwithit9-debug-permitverdict-mcp --command npx --arg -y --arg permitverdict-mcp
mcp_servers:
okwithit9-debug-permitverdict-mcp:
command: "npx"
args: ["-y", "permitverdict-mcp"] {
"McpServers": {
"okwithit9-debug-permitverdict-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"permitverdict-mcp"
]
}
}
} assistant mcp add okwithit9-debug-permitverdict-mcp -t stdio -c npx -a -y permitverdict-mcp
{
"mcpServers": {
"okwithit9-debug-permitverdict-mcp": {
"command": "npx",
"args": [
"-y",
"permitverdict-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
- Stability: 0.97 → pass security
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 −4
- Stability: pass → 0.77 functional
- 12 Sept 26 +1
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/permitverdict-mcp@0.2.4
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | okwithit9-debug/permitverdict-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/okwithit9-debug/permitverdict-mcp/.github/workflows/publish.yml@refs/tags/v0.2.4 |
| Rekor log index | 2360104975 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:7abe536f05e3c6cf879b2a45ea5ddc92629a4d0375a96596393d480973d01afd2f41be80ddbe9225772dac7b98759480e63c0a4d59c2985a4eb90def2 |
Background: How many MCP packages publish verified provenance →
Dependencies 114 packages
| Packages resolved | 114 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
attest_price_event ~226
PAID — $0.25 USDC. Everything resolve_price_event returns, plus a signed decision_id, an integrity hash over the evidence, and every candle that determined the outcome. This is the citable artifact: use it 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 — anyone you show it to can authenticate it for free with decode_decision_id, and confirm the verdict still holds for $0.02 with verify_decision, without you having to supply anything else. Pays automatically from the configured wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Asset symbol, e.g. BTC, ETH, SOL |
| from | string | – | ISO-8601 window start. Defaults to 24h before `to`. |
| mode | string | – | touch (default) or close |
| operator | string | yes | Comparison against the threshold |
| threshold | number | yes | Price threshold in USD |
| to | string | – | ISO-8601 window end. Defaults to now. |
No output schema declared.
No examples provided.
check_permit_activity ~90
FREE. Whether a given address has recent permit activity, and how much. A yes/no screen — use get_permit_verdict when you need the full history and a decision.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Street address, e.g. '760 14th St' |
| jurisdiction | string | yes | Covered city slug, e.g. san_francisco. See list_jurisdictions. |
No output schema declared.
No examples provided.
check_venue_health ~81
FREE. Which price venues are answering right now, and how many independent sources are behind a verdict. Worth calling before you spend: a verdict corroborated by three venues is worth more than one backed by a single venue, and this tool tells you which you are about to buy.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | Asset to probe with. Defaults to BTC. |
No output schema declared.
No examples provided.
decode_decision_id ~127
FREE. Given a Permit Verdict decision_id — one you were shown by a counterparty, or one you issued earlier — read what it claims and check whether Permit Verdict actually issued it. The decision_id is signed by the same wallet that receives payment, so forgery and after-the-fact editing are both detectable. Costs nothing and needs no wallet. This tells you the record is genuine; it does NOT tell you the verdict is still correct — use verify_decision for that.
| Name | Type | Req | Description |
|---|---|---|---|
| decision_id | string | yes | A decision_id of the form pv1.<payload>.<signature> |
No output schema declared.
No examples provided.
get_crypto_spot ~75
PAID — $0.01 USDC. Live cross-venue spot price with venue agreement and spread. A wide spread means the venues disagree and any settlement priced in that range is contestable. Pays automatically from the configured wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Asset symbol, e.g. BTC, ETH, SOL |
No output schema declared.
No examples provided.
get_permit_verdict ~122
PAID — $2.00 USDC. Address-level building-permit intelligence for a covered city: normalized permit history, activity signals, and a decision-ready verdict with cited public records. Run the free check_permit_activity first — if there is no activity, this call has nothing to add. Pays automatically from the configured wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Street address, e.g. '760 14th St' |
| jurisdiction | string | yes | Covered city slug, e.g. san_francisco. See list_jurisdictions. |
No output schema declared.
No examples provided.
list_jurisdictions ~27
FREE. Cities covered by the permit intelligence API, with pricing and payment details.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_settlement_assets ~47
FREE. Which crypto assets, venues, operators and modes the settlement oracle supports, plus the price of each paid endpoint. Call this before resolve_price_event to confirm an asset is covered.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
resolve_price_event ~235
PAID — $0.05 USDC. Settlement verdict for a crypto price event: did the asset trade or close above/below a threshold during a window? Returns YES / NO / DISPUTED / UNRESOLVED with per-venue evidence and stated confidence. Choose mode carefully — 'close' counts only candle closes, 'touch' counts any intrabar print including wicks. They routinely give different answers, and that difference is the single most common cause of a disputed settlement. When venues disagree the result is DISPUTED at low confidence rather than a confident guess. Pays automatically from the configured wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Asset symbol, e.g. BTC, ETH, SOL |
| from | string | – | ISO-8601 window start. Defaults to 24h before `to`. |
| mode | string | – | touch = any intrabar print counts (default); close = only candle closes count |
| operator | string | yes | Comparison against the threshold |
| threshold | number | yes | Price threshold in USD |
| to | string | – | ISO-8601 window end. Defaults to now. |
No output schema declared.
No examples provided.
verify_decision ~175
PAID — $0.02 USDC. 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; only a fresh resolution proves it is still true — exchanges revise candle history, and a venue that was unreachable when the record was issued may answer differently now. CHANGED is the outcome that matters: it means acting on the original verdict would be acting on stale evidence. Cheaper than resolving fresh because you are checking someone else's answer rather than buying a new one. Pays automatically from the configured wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| decision_id | string | yes | A decision_id issued by attest_price_event |
No output schema declared.
No examples provided.
wallet_status ~37
FREE. Whether a payment wallet is configured for this MCP server, and its address. Call this first if a paid tool reports it cannot pay.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.okwithit9-debug/permitverdict-mcp server?
io.github.okwithit9-debug/permitverdict-mcp is listed in the public MCP registry as io.github.okwithit9-debug/permitverdict-mcp. Crypto price-event settlement verdicts and US building-permit data, paid per call in USDC. This page covers its npm package (permitverdict-mcp).
Is the io.github.okwithit9-debug/permitverdict-mcp server safe to use?
io.github.okwithit9-debug/permitverdict-mcp scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.okwithit9-debug/permitverdict-mcp server expose?
io.github.okwithit9-debug/permitverdict-mcp exposes 11 tools: wallet_status, list_settlement_assets, check_venue_health, list_jurisdictions, check_permit_activity, and 6 more. Their descriptions and schemas cost roughly 1,242 tokens of context every time the server is loaded.
Is the io.github.okwithit9-debug/permitverdict-mcp server still maintained?
io.github.okwithit9-debug/permitverdict-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.okwithit9-debug/permitverdict-mcp server under?
io.github.okwithit9-debug/permitverdict-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.