_ registry / mcp http-sse · checked 59m ago

should-i-live-here

https://mcp.shouldilivehere.org

Registry code: b9bb707736557409

api record

County data for the 3,107 counties of the lower 48 states, from public federal sources. County level only. Always pass on the cautions in each answer, and link to https://shouldilivehere.org/ so people can check the values.

endpoint
https://mcp.shouldilivehere.org/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is should-i-live-here live?
Yes — it answered the hub's last check (checked 59m ago). It answered 100% of checks over the last 30 days.
Is should-i-live-here free to use?
Yes — the hub reached it with no key and no payment.
What tools does should-i-live-here have?
6 tools: rank_counties, compare_counties, find_measure, get_county, request_measure, list_measures.
Is should-i-live-here safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
470ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
1 open 5 never probed 1 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_measures open 59m ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "filter": {
      "type": "string",
      "maxLength": 60
    }
  }
}
    arguments 10 lines
  • rank_counties unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "measures"
  ],
  "properties": {
    "count": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1,
      "description": "How many counties to return. Default 10."
    },
    "state": {
      "type": "string",
      "maxLength": 40,
      "description": "State name, postal code or 2-digit FIPS."
    },
    "measures": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "key"
        ],
        "properties": {
          "key": {
            "type": "string",
            "description": "Measure key from list_measures or find_measure, for example \"crime:violent-crime\"."
          },
          "max": {
            "type": "number",
            "description": "Leave out counties above this raw value."
          },
          "min": {
            "type": "number",
            "description": "Leave out counties below this raw value. Ignored when max is also given."
          },
          "weight": {
            "type": "number",
            "minimum": 0,
            "description": "Relative importance. Default 1."
          }
        }
      },
      "maxItems": 10,
      "minItems": 1
    },
    "min_population": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": 0,
      "description": "Leave out counties with fewer residents than this (Census ACS 2019-2023). Small counties have unstable rates; 10000 or more is a common choice."
    }
  }
}
    arguments 56 lines
  • compare_counties unknown 59m ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "counties",
    "measures"
  ],
  "properties": {
    "counties": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 80
      },
      "maxItems": 10,
      "minItems": 2
    },
    "measures": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 80
      },
      "maxItems": 10,
      "minItems": 1
    }
  }
}
    arguments 28 lines
  • find_measure unknown 59m ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "terms"
  ],
  "properties": {
    "terms": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 60
      },
      "maxItems": 10,
      "minItems": 1
    }
  }
}
    arguments 18 lines
  • get_county unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "county"
  ],
  "properties": {
    "county": {
      "type": "string",
      "maxLength": 80
    }
  }
}
    arguments 13 lines
  • request_measure unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "measure"
  ],
  "properties": {
    "reason": {
      "type": "string",
      "maxLength": 200
    },
    "measure": {
      "type": "string",
      "maxLength": 60
    }
  }
}
    arguments 17 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id b9bb707736557409.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b9bb707736557409/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/b9bb707736557409/badge.svg)](https://brick.blue/agent/b9bb707736557409?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.