
Permitverdict Mcp
io.github.okwithit9-debugPublished by GitHub account okwithit9-debugv0.2.4Updated Oct 24, 2026
Crypto price-event settlement verdicts and US building-permit data, paid per call in USDC.
Overview
Gives an assistant crypto price-event settlement verdicts and US building-permit data, with paid calls settled in USDC.
- What you can do
- Exposes eleven tools: six free ones cover wallet status, supported assets and venues, venue health, decision-id decoding, covered cities, and whether an address has recent permit activity. Paid tools return cross-venue spot prices, re-verify an attested settlement, resolve a price event in touch or close mode, issue a signed decision_id with the underlying candles, and produce a full permit history and verdict for an address. Verdicts are resolved independently across several exchanges, and disagreements are reported as DISPUTED at low confidence.
- When to use it
- Useful when an assistant must judge whether a crypto price event actually occurred, check a settlement attestation handed over by a counterparty, or pull building-permit history and activity signals for a US address. The free tools let you check venue health and coverage before spending anything.
- Requirements
- Runs remotely at permitverdict.com or locally via the npm package permitverdict-mcp over stdio, typically through npx. No account, signup, or API key. Free tools need nothing; paid tools need a funded wallet supplied through the WALLET_PRIVATE_KEY environment variable, holding USDC on Base. Network access to permitverdict.com and the x402 facilitator.
Installation
In SourceWeft
- Open Permitverdict Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.okwithit9-debug%2Fpermitverdict-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"permitverdict": {
"type": "http",
"url": "https://permitverdict.com/mcp"
}
}
}README
This repository has no README.
Tools
0Version history
1- v0.2.4LatestSep 16, 2026
Score
60% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.