Permit Verdicts
REMOTE · PERMIT-API-PRODUCTION-7375.UP.RAILWAY.APP · SCANNED AUG 3
Building-permit verdicts by address, with cited records. SF, Seattle, Austin, NYC. Pay per call.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 383 tokens (~95/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · permit-api-production-7375.up.railway.app
claude mcp add --transport http okwithit9-debug-permit-verdicts https://permit-api-production-7375.up.railway.app/mcp
[mcp_servers.okwithit9-debug-permit-verdicts] url = "https://permit-api-production-7375.up.railway.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"okwithit9-debug-permit-verdicts": {
"type": "remote",
"url": "https://permit-api-production-7375.up.railway.app/mcp",
"enabled": true
}
}
} openclaw mcp add okwithit9-debug-permit-verdicts --url https://permit-api-production-7375.up.railway.app/mcp --transport streamable-http
mcp_servers:
okwithit9-debug-permit-verdicts:
url: "https://permit-api-production-7375.up.railway.app/mcp" {
"mcpServers": {
"okwithit9-debug-permit-verdicts": {
"type": "http",
"url": "https://permit-api-production-7375.up.railway.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 26 69
First indexed and scored.
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 3 Aug 2026 · Probed https://permit-api-production-7375.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC insecure
Validation of permit-api-production-7375.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://permit-api-production-7375.up.railway.app/mcp | Verified | 200 | |
| http (plaintext) | http://permit-api-production-7375.up.railway.app/mcp | HTTPS enforced | 301 | https://permit-api-production-7375.up.railway.app/mcp |
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.
check_permit_activity ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Street address, e.g. '760 14th St' |
| jurisdiction | string | yes | Covered city, e.g. san_francisco |
No output schema declared.
No examples provided.
find_active_projects ~140
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).
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | — | Lookback window, default 30 |
| feed | string | — | contractor = newly filed/issued permits (default); investor = expired/stalled |
| jurisdiction | string | yes | Covered city, e.g. san_francisco |
| max_cost | number | — | Maximum declared job value, 0 = no ceiling |
| min_cost | number | — | Minimum declared job value, default 50000 |
No output schema declared.
No examples provided.
get_permit_verdict ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Street address, e.g. '760 14th St' |
| jurisdiction | string | yes | Covered city, e.g. san_francisco |
| payment_header | string | — | Optional X-PAYMENT header value from a completed x402 payment. Omit on first call to receive payment requirements. |
No output schema declared.
No examples provided.
list_jurisdictions ~28
List cities covered by the Permit Intelligence API, with pricing and payment details. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.