Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SOS.city public record

REMOTE · API.SOS.CITY

Public records for every city: permits, alerts, wildfires, laws and funding, linked to the source.

Available components

+3 this week 67 Trust /100

Last scanned (13 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

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 → Why this is hard to score →

Endpoint Security63
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • 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
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2852 tokens (~135/item across 21 items; 21 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 Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 46% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 0
    • Server version: 1.4.0 → 1.5.0 functional
  • 13 Nov 26 +1
    • New tool “check_compliance” functional
  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 +1
    • Tool “buy” rewrote its description, which is the text the model reads security
    • “buy” added an optional parameter “list” cosmetic
  • 9 Nov 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “search_records” rewrote its description, which is the text the model reads security
    • Schema quality: 1210 → 2649 ▼ functional
    • Tool coverage: 58% → 43% ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 1.1.0 → 1.4.0 functional
    • New tool “find_lenders” functional
    • New tool “get_bank_access” functional
    • New tool “get_city_risk” functional
    • New tool “get_compliance_changes” functional
    • New tool “get_compliance_items” functional
    • New tool “list_bank_gaps” functional
    • New tool “list_compliance” functional
    • New tool “list_compliance_watches” functional
    • New tool “order_bank_report” functional
    • New tool “watch_compliance” functional
Diagnostics

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 21 Nov 2026 · Probed https://api.sos.city/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=sos.city CN=WE1,O=Google Trust Services,C=US 18 Oct 2026 16 Jan 2027 ECDSA 256 ECDSA-SHA256 1af2149fd2fec772138a2f2b9659914c
SANs: sos.city, api.sos.city, *.api.sos.city
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.sos.city. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
city. DS published 57326 8 Verified
sos.city. No DS 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.sos.city/mcp Verified 200
http (plaintext) http://api.sos.city/mcp Inconclusive 405
MCP tools · 21 exposed · ~2,573 tokens

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 →

Tool Tokens
buy ~239

Starts a one-time purchase and returns a Stripe Checkout link for the person who pays, plus a status_url to poll. product: credits_1k ($10), credits_10k ($79), city_pack ($29, needs place) or compliance_list ($99, one whole compliance list as CSV, needs list). The person must agree to the data-use terms (no screening or profiling people): pass agree_data_use=true only after they have.

NameTypeReqDescription
agree_data_usebooleanyesTrue once the person accepts: no tenant, employment, credit or insurance screening, and no locating or profiling anyone.
emailstringyesEmail of the person paying. Receipts and the account go there.
liststring–For compliance_list: a list id from list_compliance, e.g. sb721-cited.
personhoodstring–Optional 5arz proof-of-personhood credential (pop_jwt) showing a verified human stands behind this agent. Recorded with the order.
placestring–For city_pack: a place id, e.g. us-ca-los-angeles.
productstringyes–

No output schema declared.

No examples provided.

check_compliance ~162

Checks one street address against every compliance list at once (SB 721 balcony citations, LA energy benchmarking, open code cases, soft-story and concrete retrofit orders, industrial stormwater permits) and says which lists name it, with the agency's status, dates and a link to its own record. Free. Covers buildings in the City of Los Angeles. Give the ZIP: without it, the same number and street name in another ZIP can match. Not on a list means the agency's data does not name the address today, not that the building has met the law. About buildings, never people.

NameTypeReqDescription
addressstringyesStreet address with a house number, e.g. 200 N Spring St.
zipstring–5-digit ZIP.

No output schema declared.

No examples provided.

find_lenders ~66

Every bank and credit union with a branch in one county, with branch counts and assets. 25 credits from the API key (free with a watch for that state). Organizations only.

NameTypeReqDescription
countystringyes5-digit county FIPS
kindstring––

No output schema declared.

No examples provided.

get_bank_access ~173

Free. How many bank and credit union branches a ZIP, county or state has today, how far the nearest bank branch is, closings and openings in the last 120 days, ZIPs left with one bank or none, and the top lenders already there. From FDIC BankFind, the NCUA call report and Census files, rebuilt daily. Give zip, county (5-digit FIPS), place (a county or state place id) or state; none gives the US.

NameTypeReqDescription
countystring–5-digit county FIPS, e.g. 26125
placestring–County or state place id, e.g. us-mi
statestring–2-letter state, e.g. MI
zipstring–5-digit ZIP

No output schema declared.

No examples provided.

get_city_pack ~85

Every source that covers one place (with publisher, original link, licence and reuse terms) plus a year of records whose sources allow reuse. Costs 2900 credits from the API key's balance. Without credits, use buy (product city_pack) or the REST URL with x402.

NameTypeReqDescription
placestringyesPlace id, e.g. us-ca-los-angeles.

No output schema declared.

No examples provided.

get_city_risk ~128

Free. FEMA National Risk Index for the county of one of the 30 largest U.S. cities: overall rating and score, every hazard's share of the risk, rating, score and expected annual loss, plus (for verified cities) the federal disaster declarations and the official emergency alert sign-up. Omit city for the list. Every result names its source; FEMA rates counties, not cities.

NameTypeReqDescription
citystring–City id (e.g. dallas, new-york-city), city name or 5-digit county FIPS. Omit to list all 30.

No output schema declared.

No examples provided.

get_compliance_changes ~173

Buildings and facilities added to, taken off, or changed on a compliance list since a day (default the last 7 days), from the agency's own data. Counts are free; the first 10 rows are free, then credits per 100 rows. Off the list means the agency's data no longer lists the item, not proof the work was done.

NameTypeReqDescription
kindstring–added, removed, changed (comma-separated).
limitinteger––
liststringyes–
offsetinteger––
sincestring–YYYY-MM-DD, default 7 days ago.
stackedboolean–Only addresses also on another list.
untilstring––
zipstring–One or more 5-digit ZIPs, comma-separated.

No output schema declared.

No examples provided.

get_compliance_items ~174

Rows of one compliance list (address, ZIP, dates, status, the agency's id, a link to the original, and other lists the same address is on). The first 10 rows are free; more cost credits per 100 rows (see get_store). Filter by zip, address (q), status, type, since (YYYY-MM-DD) or stacked=true (addresses on more than one list).

NameTypeReqDescription
limitinteger––
liststringyes–
offsetinteger––
qstring–An address or part of one.
sincestring–Only rows dated on or after this day (YYYY-MM-DD).
stackedboolean––
statusstring––
typestring––
zipstring––

No output schema declared.

No examples provided.

get_source ~49

Full details of one source by id: publisher, original link, API endpoint, formats, update rate, last update, licence, location detail, check status and notes.

NameTypeReqDescription
idintegeryes–

No output schema declared.

No examples provided.

get_store ~79

The SOS.city data store: what's free, what costs credits (1 credit = 1 cent), credit packs, city data packs, building records and deep searches, and every way to pay (credits with an API key, x402 USDC, or a Stripe link for a person). Shows the caller's credit balance when an API key is sent.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_bank_gaps ~106

ZIPs where a branch closing left no bank, one bank, or a 10+ mile trip to the next branch, with the bank that left and the nearest one still open. Free: the last 30 days, 25 rows. full=true returns the whole 120-day window (100 credits from the API key, or free with a watch for that state).

NameTypeReqDescription
alertstring––
fullboolean––
statestring––

No output schema declared.

No examples provided.

list_compliance ~126

Buildings and facilities that owe a legally required inspection, filing or fix (SB 721 balcony inspections, LA energy benchmarking, open code cases, soft-story and concrete retrofits, industrial stormwater permits), read from the agency's dataset and refreshed daily. Free: what each law requires, who may sign, how many are on each list, by ZIP and status. For the firms that do this work. Not for finding or profiling people.

NameTypeReqDescription
liststring–Optional list id for its full numbers, e.g. sb721-cited. Leave out to see every list.

No output schema declared.

No examples provided.

list_compliance_watches ~43

The account's compliance watches: what each covers, how it's delivered, when it last went out and what it did, and its tracked items open and closed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_departments ~27

The 15 departments (shelves) every source sits on, with what each covers.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_gaps ~50

Records people need that the library doesn't hold yet, or that no agency publishes. Check this before telling a user a record doesn't exist.

NameTypeReqDescription
placestring––
statusstring––

No output schema declared.

No examples provided.

list_places ~69

The atlas: world, countries, states, counties and cities, with their ids. Filter by parent id (e.g. 'us' for US states) or kind.

NameTypeReqDescription
kindstring––
namestring–Part of a place name.
parentstring––

No output schema declared.

No examples provided.

order_bank_report ~114

Start a checkout for a Bank desert watch (state, regional, national, closing soon, branch sites) or a one-time report (market brief, acquisition screen, merger impact). Returns a Stripe link for the person who pays. See get_store for prices.

NameTypeReqDescription
agree_data_usebooleanyes–
emailstringyes–
productstringyes–
scopestring–For reports: the market, deal or target
statesstring–2-letter states, comma-separated

No output schema declared.

No examples provided.

request_record ~64

Ask SOS.city to find a public record that isn't in the library. It joins the gap board; give an email to hear back. Never for locating or profiling a person.

NameTypeReqDescription
emailstring––
placestring––
questionstringyes–

No output schema declared.

No examples provided.

search_library ~195

Find public-records sources (datasets, portals, registers, reports) by question or keywords. Use `place` to include everything covering a place, from the city up to federal and global sources. Returns the publisher, how to get the data (API endpoint or page), update rate, last update, licence and whether we verified it. Not for finding, profiling or screening people.

NameTypeReqDescription
departmentstring–Shelf id: water, power, safety, housing, laws, funding, services, transport, environment, health, people, consumer, education, jobs, portals.
limitinteger––
placestring–Place id, e.g. 'us-ca-los-angeles', 'us-ca', 'us', 'germany'. Use list_places to find ids.
querystringyesWhat you're looking for, e.g. 'open code enforcement cases' or 'boil water notices'.

No output schema declared.

No examples provided.

search_records ~290

The records SOS.city reads from agencies' open data, one row each: building permits, code-enforcement cases, inspections, certificates of occupancy, new business registrations, grants, weather alerts, earthquakes, US wildfires (NIFC), SCE power shutoffs, satellite fire detections (NASA FIRMS), bank branch openings, closings and mergers (FDIC), current drug shortages (openFDA) and county night-light drops that estimate power outages (NASA Black Marble). Filter by place, kind, ZIP or street address. Each row links to the agency's original. History depends on the plan (Free: 30 days, 100 rows). full_history=true (1 credit) and limit over 100 (1 credit per extra 100 rows, up to 1,000) are paid from the API key's credits; see get_store.

NameTypeReqDescription
addressstring–Street address, e.g. '200 N Spring St'. Matches by house number and street name.
full_historyboolean–Past the plan's history window (1 credit).
kindstring––
limitinteger–Over 100 is paid (1 credit per extra 100 rows).
placestring–Place id, e.g. 'us-ca-los-angeles'.
sincestring–YYYY-MM-DD.
zipstring–Five-digit ZIP.

No output schema declared.

No examples provided.

watch_compliance ~161

Save a watch on one compliance list (ZIPs, status, type, stacked) and get what changed daily or weekly by email and/or a signed webhook. Pass track (item keys) to follow items one by one: each closes on its own when the agency's data no longer lists it. Needs an API key. Rows past the first 10 in each delivery cost credits per 100.

NameTypeReqDescription
cadencestring––
kindsarray––
liststringyes–
namestring––
stackedboolean––
statusstring––
trackarray––
typestring––
webhook_urlstring––
zipsarray––

No output schema declared.

No examples provided.

Install

How do I install the SOS.city public record MCP server?

SOS.city public record is a hosted endpoint at https://api.sos.city/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.sos.city

# add to Claude Code
claude mcp add --transport http proof-layer-sos-city 'https://api.sos.city/mcp'
Common questions

What is the SOS.city public record MCP server?

SOS.city public record is an MCP server listed in the public MCP registry as io.github.Proof-Layer/sos-city. Public records for every city: permits, alerts, wildfires, laws and funding, linked to the source. This page covers its hosted endpoint (https://api.sos.city/mcp).

Is the SOS.city public record MCP server safe to use?

SOS.city public record scores 67 out of 100 on VerifyMCP. 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 SOS.city public record MCP server expose?

SOS.city public record exposes 21 tools: search_library, get_source, list_places, list_departments, list_gaps, and 16 more. Their descriptions and schemas cost roughly 2,573 tokens of context every time the server is loaded.

Does the SOS.city public record MCP server require authentication?

No. We connected to SOS.city public record without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SOS.city public record MCP server still maintained?

SOS.city public record is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the SOS.city public record MCP server?

VerifyMCP ran 12 checks on SOS.city public record, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about SOS.city public record: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.