Should I Live Here?
REMOTE · MCP.SHOULDILIVEHERE.ORG
Rank and compare US counties on health, hazards, crime, rent, internet and air, from public data.
Available components
Last scanned (8 hours ago)
Scores higher than 13% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
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 Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 403, 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 & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
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.
- 5 Nov 26 −35
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Authorization: partial → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 4 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 62
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 5 Nov 2026 · Probed https://mcp.shouldilivehere.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=shouldilivehere.org | CN=WE1,O=Google Trust Services,C=US | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | c1ab539991599c610e54a03ae080299d |
| SANs: shouldilivehere.org, mcp.shouldilivehere.org, *.mcp.shouldilivehere.org | ||||||
| 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 mcp.shouldilivehere.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 725, 26974 | 8, 8 | Verified |
| shouldilivehere.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 403 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'none'; script-src 'nonce-DP5CQLUzJRmiuOdVov2725' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blob:; child-src 'self' https://challenges.cloudflare.com blob:; worker-src blob:; form-action http: https:; base-uri 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
| permissions-policy | accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=(),xr-spatial-tracking=* |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.shouldilivehere.org/mcp | Auth required | 403 | |
| http (plaintext) | http://mcp.shouldilivehere.org/mcp | Inconclusive | 403 |
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 →
compare_counties ~37
Compare 2 to 10 counties side by side on chosen measures.
| Name | Type | Req | Description |
|---|---|---|---|
| counties | array | yes | – |
| measures | array | yes | – |
No output schema declared.
No examples provided.
find_measure ~76
Map plain words (for example "internet", "cancer", "crime", "cost of living") to atlas measure keys. Words the atlas has no data for come back in not_available. Those words are counted (word and day only, no personal data) so the owner can consider new data.
| Name | Type | Req | Description |
|---|---|---|---|
| terms | array | yes | – |
No output schema declared.
No examples provided.
get_county ~50
All atlas values for one county, by 5-digit FIPS or "Name, State" (state name or postal code). Missing values stay null with their status.
| Name | Type | Req | Description |
|---|---|---|---|
| county | string | yes | – |
No output schema declared.
No examples provided.
list_measures ~57
List the county measures in the Should I Live Here? atlas: key, label, unit, period, direction, and how many of the 3,107 counties have a value. Optional text filter.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | – |
No output schema declared.
No examples provided.
rank_counties ~150
Rank counties in the lower 48 states on weighted measures, with the same scoring as the site's My priorities. Rank 1 has the lowest concern score. Counties with missing data are left out, never scored as low. Optional limits and state filter. Read the cautions in every answer.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many counties to return. Default 10. |
| measures | array | yes | – |
| min_population | integer | – | Leave out counties with fewer residents than this (Census ACS 2019-2023). Small counties have unstable rates; 10000 or more is a common choice. |
| state | string | – | State name, postal code or 2-digit FIPS. |
No output schema declared.
No examples provided.
request_measure ~48
Report a measure a user wanted that the atlas lacks, for example "schools". Only the measure name and the day are counted.
| Name | Type | Req | Description |
|---|---|---|---|
| measure | string | yes | – |
| reason | string | – | – |
No output schema declared.
No examples provided.
How do I install the Should I Live Here? MCP server?
Should I Live Here? is a hosted endpoint at https://mcp.shouldilivehere.org/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 · mcp.shouldilivehere.org
claude mcp add --transport http gdtilghman-should-i-live-here 'https://mcp.shouldilivehere.org/mcp'
What is the Should I Live Here? MCP server?
Should I Live Here? is an MCP server listed in the public MCP registry as io.github.gdtilghman/should-i-live-here. Rank and compare US counties on health, hazards, crime, rent, internet and air, from public data. This page covers its hosted endpoint (https://mcp.shouldilivehere.org/mcp).
Is the Should I Live Here? MCP server safe to use?
Should I Live Here? scores 28 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 Should I Live Here? MCP server expose?
Should I Live Here? exposes 6 tools: list_measures, find_measure, get_county, compare_counties, rank_counties, request_measure. Their descriptions and schemas cost roughly 418 tokens of context every time the server is loaded.
Does the Should I Live Here? MCP server require authentication?
Yes. Should I Live Here? asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Should I Live Here? MCP server still maintained?
Should I Live Here? is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.