Skip to content

shinnslist MCP server

com.shinnslist/shinnslistshinnslist.comstreamable-httpv0.2.0Scanned

Public-record parcel signals for off-market real estate. Free beta; only proven signals listed.

7 tools: 3 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 3 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the shinnslist MCP server can do

The shinnslist MCP server is published by shinnslist.com, a domain the MCP Registry verified. It has 7 tools. It can create or change data (3 tools: town_stats, check_parcel and run_signal), but cannot delete data. 4 tools only read.

1 tool brings in text other people can write (run_signal).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 8, 2026, version 0.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 3Claude Code: ask
  • check_parcelOne 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) ever…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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, code cases, permits, wildfire and flood. Find it by shinnslist key, by street address (with ZIP when you have it), or by latitude and longitude.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • run_signalRun one proven signal adapter live at a point in Colorado or Virginia (see list_signals for the ids).Reads text others write1 finding

    Why it is in this group

    • The name "run_signal" says "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "run_signal" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "run_signal" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • town_statsHow 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 com…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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 county records, never estimates.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 4Show 4 read-only tools
  • explain_gradingHow 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 ranki…No findings

    Why it is in this group

    • The name "explain_grading" says "explain": a word for reading.
    Description, as the server wrote it
    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 value estimate comes to real sale prices (the buyer-price floor is the bar). Returns the current numbers and the page to cite.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • find_parcelsFind off-market parcels in a Colorado or Virginia county, town or ZIP from county records: who is likely to sell and why.No findings

    Why it is in this group

    • The name "find_parcels" says "find": a word for reading.
    Description, as the server wrote it
    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 value), flipper (dated homes next to updated sales), str_investor (mountain-town homes with absentee owners), developer (land is most of the value), cash_investor and brrr (rent against value), land (empty lots), two_households (a family compound: room for two households), realtor (estate, tax lien, code case or stalled permit). Returns parcels with address, county value, last sale, years held and a shinnslist link; never owner names.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_coverageWhich 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.No findings

    Why it is in this group

    • The name "list_coverage" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_signalsThe signals shinnslist has proven against their live public source, with the date, precision and recall of each proof.No findings

    Why it is in this group

    • The name "list_signals" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:24 UTC, unchanged since Oct 23, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://shinnslist.com/api/mcp: tools/list returned 7 tools to an anonymous client, including town_stats (write), check_parcel (write), run_signal (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "run_signal" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "run_signal" says "run": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff

Install

Pinned to version 0.2.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__shinnslist__find_parcels",
      "mcp__shinnslist__list_coverage",
      "mcp__shinnslist__list_signals",
      "mcp__shinnslist__explain_grading"
    ],
    "ask": [
      "mcp__shinnslist__town_stats",
      "mcp__shinnslist__check_parcel",
      "mcp__shinnslist__run_signal"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as shinnslist. Review it before you use it.

Capability tags behind 1 rule
  • mcp__shinnslist__run_signal untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.shinnslist/shinnslist/verify?hash=96352328b17d4b55619d50aa0e7b173a790c03d139aca4fc92561b65b7c1b2d6" | jq -e '.changed == false'

Pinned hash 96352328b17d, from Nov 8, 2026, 19:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.shinnslist/shinnslist/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.shinnslist/shinnslist
[![Anlyon Radar](https://radar.anlyon.com/badge/com.shinnslist/shinnslist.svg)](https://radar.anlyon.com/servers/com.shinnslist/shinnslist)

Source: MCP Registry. Synced Oct 23, 2026, 08:17 UTC.

shinnslist MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the shinnslist MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the shinnslist MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the shinnslist MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the shinnslist MCP server have?

7 tools: 3 write, 4 read. town_stats, check_parcel, run_signal, find_parcels, list_coverage, list_signals and explain_grading.

Does the shinnslist MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the shinnslist MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the shinnslist MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.