# permitverdict-mcp

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

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.2.4
- **Author:** io.github.okwithit9-debug
- **License:** Unknown
- **npm:** permitverdict-mcp
- **Endpoints:** streamable-http https://permitverdict.com/mcp
- **Source:** https://github.com/okwithit9-debug/permitverdict-mcp
- **Endpoint health:** reachable (last checked 2026-08-29T02:10:00.390Z, 1 sample) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 10 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-08-18T14:49:50.165Z
- **Version scanned:** 0.2.4
- **CVEs:** none found by OSV at scan time

## Tools

11 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `wallet_status`
- `list_settlement_assets`
- `check_venue_health`
- `list_jurisdictions`
- `check_permit_activity`
- `get_crypto_spot`
- `resolve_price_event`
- `decode_decision_id`
- `verify_decision`
- `attest_price_event`
- `get_permit_verdict`

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"permitverdict\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"permitverdict-mcp\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to extensive — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs locally and hosted; read-only tool surface.
- Floor 17, ceiling 35 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/permitverdict-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/permitverdict-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/permitverdict-mcp
- HTML page: https://forgeregistry.com/registry/permitverdict-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.