# SOS.city public record (remote · api.sos.city)

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

- Trust score: 67/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `api.sos.city`: 67/100 (this document), [markdown](https://verifymcp.io/servers/proof-layer-sos-city/api.md), [page](https://verifymcp.io/servers/proof-layer-sos-city/api)

## Channel facts

- Endpoint: `https://api.sos.city/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 82/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 46% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http proof-layer-sos-city 'https://api.sos.city/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "proof-layer-sos-city": {
      "url": "https://api.sos.city/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "proof-layer-sos-city": {
      "type": "http",
      "url": "https://api.sos.city/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.proof-layer-sos-city]
url = "https://api.sos.city/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "proof-layer-sos-city": {
      "type": "remote",
      "url": "https://api.sos.city/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add proof-layer-sos-city --url 'https://api.sos.city/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  proof-layer-sos-city:
    url: "https://api.sos.city/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "proof-layer-sos-city": {
      "Transport": "http",
      "Url": "https://api.sos.city/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add proof-layer-sos-city -t streamable-http -u 'https://api.sos.city/mcp'
```

### Other

```json
{
  "mcpServers": {
    "proof-layer-sos-city": {
      "type": "http",
      "url": "https://api.sos.city/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-19 (score 67, +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.

### 2026-11-17 (score 66, +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.

### 2026-11-15 (score 65, +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.

### 2026-11-14 (score 64, 0)

- [functional] Server version: 1.4.0 → 1.5.0

### 2026-11-13 (score 64, +1)

- [functional] New tool “check_compliance”

### 2026-11-12 (score 63, +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.

### 2026-11-10 (score 62, +1)

- [security] Tool “buy” rewrote its description, which is the text the model reads
- [cosmetic] “buy” added an optional parameter “list”

### 2026-11-09 (score 61, −1)

- [security] 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
- [functional regression] Schema quality: 1210 → 2649
- [functional regression] Tool coverage: 58% → 43%
- [functional improvement] 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”

## MCP tools (21)

### `search_library` (~195 tokens)

Search the public record

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.

Input parameters:

- `department` (string): Shelf id: water, power, safety, housing, laws, funding, services, transport, environment, health, people, consumer, education, jobs, portals.
- `limit` (integer)
- `place` (string): Place id, e.g. 'us-ca-los-angeles', 'us-ca', 'us', 'germany'. Use list_places to find ids.
- `query` (string, required): What you're looking for, e.g. 'open code enforcement cases' or 'boil water notices'.

### `get_source` (~49 tokens)

Get one source

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

Input parameters:

- `id` (integer, required)

### `list_places` (~69 tokens)

List places

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

Input parameters:

- `kind` (string)
- `name` (string): Part of a place name.
- `parent` (string)

### `list_departments` (~27 tokens)

List shelves

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

### `list_gaps` (~50 tokens)

What's missing

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.

Input parameters:

- `place` (string)
- `status` (string)

### `search_records` (~290 tokens)

Search the records themselves

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.

Input parameters:

- `address` (string): Street address, e.g. '200 N Spring St'. Matches by house number and street name.
- `full_history` (boolean): Past the plan's history window (1 credit).
- `kind` (string)
- `limit` (integer): Over 100 is paid (1 credit per extra 100 rows).
- `place` (string): Place id, e.g. 'us-ca-los-angeles'.
- `since` (string): YYYY-MM-DD.
- `zip` (string): Five-digit ZIP.

### `request_record` (~64 tokens)

Request a record

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.

Input parameters:

- `email` (string)
- `place` (string)
- `question` (string, required)

### `get_store` (~79 tokens)

See prices and how to pay

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.

### `buy` (~239 tokens)

Buy credits or a city data pack

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.

Input parameters:

- `agree_data_use` (boolean, required): True once the person accepts: no tenant, employment, credit or insurance screening, and no locating or profiling anyone.
- `email` (string, required): Email of the person paying. Receipts and the account go there.
- `list` (string): For compliance_list: a list id from list_compliance, e.g. sb721-cited.
- `personhood` (string): Optional 5arz proof-of-personhood credential (pop_jwt) showing a verified human stands behind this agent. Recorded with the order.
- `place` (string): For city_pack: a place id, e.g. us-ca-los-angeles.
- `product` (string, required)

### `get_city_pack` (~85 tokens)

Get a city data pack

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.

Input parameters:

- `place` (string, required): Place id, e.g. us-ca-los-angeles.

### `check_compliance` (~162 tokens)

Is this address on a compliance list?

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.

Input parameters:

- `address` (string, required): Street address with a house number, e.g. 200 N Spring St.
- `zip` (string): 5-digit ZIP.

### `list_compliance` (~126 tokens)

Compliance lists: who owes an inspection, filing or fix

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.

Input parameters:

- `list` (string): Optional list id for its full numbers, e.g. sb721-cited. Leave out to see every list.

### `get_compliance_items` (~174 tokens)

Get rows of a compliance list

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).

Input parameters:

- `limit` (integer)
- `list` (string, required)
- `offset` (integer)
- `q` (string): An address or part of one.
- `since` (string): Only rows dated on or after this day (YYYY-MM-DD).
- `stacked` (boolean)
- `status` (string)
- `type` (string)
- `zip` (string)

### `get_compliance_changes` (~173 tokens)

What changed on a compliance list

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.

Input parameters:

- `kind` (string): added, removed, changed (comma-separated).
- `limit` (integer)
- `list` (string, required)
- `offset` (integer)
- `since` (string): YYYY-MM-DD, default 7 days ago.
- `stacked` (boolean): Only addresses also on another list.
- `until` (string)
- `zip` (string): One or more 5-digit ZIPs, comma-separated.

### `watch_compliance` (~161 tokens)

Set up a compliance alert

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.

Input parameters:

- `cadence` (string)
- `kinds` (array)
- `list` (string, required)
- `name` (string)
- `stacked` (boolean)
- `status` (string)
- `track` (array)
- `type` (string)
- `webhook_url` (string)
- `zips` (array)

### `list_compliance_watches` (~43 tokens)

List my compliance alerts

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.

### `get_bank_access` (~173 tokens)

Bank access for a ZIP, county or state

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.

Input parameters:

- `county` (string): 5-digit county FIPS, e.g. 26125
- `place` (string): County or state place id, e.g. us-mi
- `state` (string): 2-letter state, e.g. MI
- `zip` (string): 5-digit ZIP

### `list_bank_gaps` (~106 tokens)

ZIPs that just lost their bank

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).

Input parameters:

- `alert` (string)
- `full` (boolean)
- `state` (string)

### `find_lenders` (~66 tokens)

Who can serve a county

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.

Input parameters:

- `county` (string, required): 5-digit county FIPS
- `kind` (string)

### `order_bank_report` (~114 tokens)

Buy a bank watch or report

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.

Input parameters:

- `agree_data_use` (boolean, required)
- `email` (string, required)
- `product` (string, required)
- `scope` (string): For reports: the market, deal or target
- `states` (string): 2-letter states, comma-separated

### `get_city_risk` (~128 tokens)

Natural-hazard risk for a U.S. city

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.

Input parameters:

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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/proof-layer-sos-city/api#diagnostics

## Score history

- 2026-11-21: 67
- 2026-11-20: 67
- 2026-11-19: 67
- 2026-11-18: 66
- 2026-11-17: 66
- 2026-11-16: 65
- 2026-11-15: 65
- 2026-11-14: 64
- 2026-11-13: 64
- 2026-11-12: 63
- 2026-11-11: 62
- 2026-11-10: 62
- 2026-11-09: 61
- 2026-11-08: 62

## 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.

## Links

- Remote endpoint: https://api.sos.city/mcp
- Website: https://sos.city/connect
- Changelog RSS feed: https://verifymcp.io/servers/proof-layer-sos-city/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/proof-layer-sos-city/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/proof-layer-sos-city/api.json
- HTML version of this page: https://verifymcp.io/servers/proof-layer-sos-city/api
