Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Permit Verdicts is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
10
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Building-permit verdicts by address, with cited records. SF, Seattle, Austin, NYC. Pay per call.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http permit-verdicts-mcp https://permit-api-production-7375.up.railway.app/mcp
# 2 — ask your agent for something these tools do
# list_jurisdictions, check_permit_activity, find_active_projects and 7 more
Permit Verdicts costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ODAll 2 servers
okwithit9-debug2 servers
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http permit-verdicts-mcp https://permit-api-production-7375.up.railway.app/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List cities covered by the Permit Intelligence API, with pricing and payment details. Free. Full paid feeds for humans: https://permitverdict.com/pricing
No parameter schema on file.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jurisdiction | string | yes | Covered city, e.g. san_francisco |
| address | string | yes | Street address, e.g. '760 14th St' |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jurisdiction | string | yes | Covered city, e.g. san_francisco |
| feed | string | no | contractor = newly filed/issued permits (default); investor = expired/stalled |
| days | integer | no | Lookback window, default 30 |
| min_cost | number | no | Minimum declared job value, default 50000 |
| max_cost | number | no | Maximum declared job value, 0 = no ceiling |
FREE. Which crypto assets, venues, operators and modes the settlement oracle supports, plus pricing. Full paid feeds for humans: https://permitverdict.com/pricing
No parameter schema on file.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset | string | yes | Asset symbol, e.g. BTC, ETH, SOL |
| operator | string | yes | Comparison against the threshold |
| threshold | number | yes | Price threshold in USD |
| from | string | no | ISO-8601 window start. Defaults to 24h before to. |
| to | string | no | ISO-8601 window end. Defaults to now. |
| mode | string | no | touch = any intrabar print counts (default); close = only candle closes count |
| payment_header | string | no | X-PAYMENT header from a settled x402 payment. Omit on first call to receive payment requirements. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset | string | yes | Asset symbol, e.g. BTC, ETH, SOL |
| payment_header | string | no | X-PAYMENT header from a settled x402 payment. |
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.c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| decision_id | string | yes | A decision_id of the form pv1.<payload>.<signature> |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| decision_id | string | yes | A decision_id issued by /v1/oracle/attest |
| payment_header | string | no | X-PAYMENT header from a settled x402 payment. Omit on first call to receive payment requirements. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset | string | yes | Asset symbol, e.g. BTC, ETH, SOL |
| operator | string | yes | Comparison against the threshold |
| threshold | number | yes | Price threshold in USD |
| from | string | no | ISO-8601 window start. Defaults to 24h before to. |
| to | string | no | ISO-8601 window end. Defaults to now. |
| mode | string | no | touch (default) or close |
| payment_header | string | no | X-PAYMENT header from a settled x402 payment. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jurisdiction | string | yes | Covered city, e.g. san_francisco |
| address | string | yes | Street address, e.g. '760 14th St' |
| payment_header | string | no | Optional X-PAYMENT header value from a completed x402 payment. Omit on first call to receive payment requirements. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Permit Verdicts or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.3.0.
0.3.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Permit Verdicts can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.