# Should I Live Here? (remote · mcp.shouldilivehere.org)

Rank and compare US counties on health, hazards, crime, rent, internet and air, from public data.

- Trust score: 28/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.shouldilivehere.org`: 28/100 (this document), [markdown](https://verifymcp.io/servers/gdtilghman-should-i-live-here/mcp.md), [page](https://verifymcp.io/servers/gdtilghman-should-i-live-here/mcp)

## Channel facts

- Endpoint: `https://mcp.shouldilivehere.org/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `0.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-05.

- **Endpoint Security**: 71/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 403, 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**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

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

## Install

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

### Claude

```bash
claude mcp add --transport http gdtilghman-should-i-live-here 'https://mcp.shouldilivehere.org/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "gdtilghman-should-i-live-here": {
      "url": "https://mcp.shouldilivehere.org/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "gdtilghman-should-i-live-here": {
      "type": "http",
      "url": "https://mcp.shouldilivehere.org/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.gdtilghman-should-i-live-here]
url = "https://mcp.shouldilivehere.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gdtilghman-should-i-live-here": {
      "type": "remote",
      "url": "https://mcp.shouldilivehere.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add gdtilghman-should-i-live-here --url 'https://mcp.shouldilivehere.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  gdtilghman-should-i-live-here:
    url: "https://mcp.shouldilivehere.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "gdtilghman-should-i-live-here": {
      "Transport": "http",
      "Url": "https://mcp.shouldilivehere.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add gdtilghman-should-i-live-here -t streamable-http -u 'https://mcp.shouldilivehere.org/mcp'
```

### Other

```json
{
  "mcpServers": {
    "gdtilghman-should-i-live-here": {
      "type": "http",
      "url": "https://mcp.shouldilivehere.org/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-05 (score 28, −35)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → unverified
- [security regression] Stability: 0.03 → unverified
- [security regression] Authorization: partial → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-04 (score 63, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-03 (score 62)

First indexed and scored.

## MCP tools (6)

### `list_measures` (~57 tokens)

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.

Input parameters:

- `filter` (string)

### `find_measure` (~76 tokens)

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.

Input parameters:

- `terms` (array, required)

### `get_county` (~50 tokens)

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.

Input parameters:

- `county` (string, required)

### `compare_counties` (~37 tokens)

Compare 2 to 10 counties side by side on chosen measures.

Input parameters:

- `counties` (array, required)
- `measures` (array, required)

### `rank_counties` (~150 tokens)

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.

Input parameters:

- `count` (integer): How many counties to return. Default 10.
- `measures` (array, required)
- `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.

### `request_measure` (~48 tokens)

Report a measure a user wanted that the atlas lacks, for example "schools". Only the measure name and the day are counted.

Input parameters:

- `measure` (string, required)
- `reason` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/gdtilghman-should-i-live-here/mcp#diagnostics

## Score history

- 2026-11-05: 28
- 2026-11-04: 63
- 2026-11-03: 62

## Common questions

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

## Links

- Remote endpoint: https://mcp.shouldilivehere.org/mcp
- Repository: https://github.com/gdtilghman/should-i-live-here-atlas
- Website: https://shouldilivehere.org/
- Changelog RSS feed: https://verifymcp.io/servers/gdtilghman-should-i-live-here/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/gdtilghman-should-i-live-here/mcp.json
- HTML version of this page: https://verifymcp.io/servers/gdtilghman-should-i-live-here/mcp