Skip to content
shinnslist logo

shinnslist MCP server

Which MCP servers are shinnslist's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-28

← Back to shinnslist

Whose server it is
  • Registry namecom.shinnslist/shinnslistverified in the MCP registry

The registry name sits under shinnslist.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-28
  • Stateanswerschecked 2026-10-28
  • Tools7
  • Server calls itselfshinnslist
  • Server version0.2.0
  • Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 633 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 1 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-10-28
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer535 ms
  • Space in an agent's context≈ 1,677 tokensthe definitions of all its tools (7), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 7 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers7 tools · read 2026-10-28
  • find_parcels

    Find off-market parcels in a Colorado or Virginia county, town or ZIP from county records: who is likely to sell and why. Pick a trade for a buyer's list: wholesaler (absentee owners, held 10+ years, bought for under half of today's…

  • town_stats

    How many parcels shinnslist tracks in a county, town or ZIP, with the count behind each buyer's trade (wholesaler, flipper, STR investor, developer, cash investor, land, family compound, realtor) and the as-of date. Counts come from…

  • check_parcel

    One parcel's stored record and its checks: the county value, last sale, years held, lot, zoning line, water, outbuildings, the recorded signs an owner may sell, and (Colorado) every stored check such as tax delinquency, estate records…

  • list_coverage

    Which counties and cities shinnslist covers, how many parcels each holds, how fresh they are, which buyer's trades are open, and how many signals are proven. Call it first when unsure whether an area is covered.

  • list_signals

    The signals shinnslist has proven against their live public source, with the date, precision and recall of each proof. Only proven signals are listed; run one with run_signal. Nothing pending or planned appears here.

  • explain_grading

    How shinnslist grades itself, in plain words: personas open only after a hand check against county records, signals proven only by a test against their live source, the daily ranking graded against what actually sells, and how close the…

  • run_signal

    Run one proven signal adapter live at a point in Colorado or Virginia (see list_signals for the ids). Needs an API key (x-api-key; a free key from POST /api/keys) and counts against its daily quota; the aggregate tools above do not.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "shinnslist": {
      "type": "http",
      "url": "https://shinnslist.com/api/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http shinnslist https://shinnslist.com/api/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://shinnslist.com/api/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.