# shinnslist (remote · shinnslist.com)

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

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `shinnslist.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-shinnslist-shinnslist/api-mcp.md), [page](https://verifymcp.io/servers/com-shinnslist-shinnslist/api-mcp)

## Channel facts

- Endpoint: `https://shinnslist.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.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**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1253 tokens (~179/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the shinnslist MCP server?

shinnslist is a hosted endpoint at https://shinnslist.com/api/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 com-shinnslist-shinnslist 'https://shinnslist.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-shinnslist-shinnslist": {
      "url": "https://shinnslist.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-shinnslist-shinnslist": {
      "type": "http",
      "url": "https://shinnslist.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-shinnslist-shinnslist]
url = "https://shinnslist.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-shinnslist-shinnslist": {
      "type": "remote",
      "url": "https://shinnslist.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-shinnslist-shinnslist --url 'https://shinnslist.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-shinnslist-shinnslist:
    url: "https://shinnslist.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-shinnslist-shinnslist": {
      "Transport": "http",
      "Url": "https://shinnslist.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-shinnslist-shinnslist -t streamable-http -u 'https://shinnslist.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-shinnslist-shinnslist": {
      "type": "http",
      "url": "https://shinnslist.com/api/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-04 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-23 (score 69)

First indexed and scored.

## MCP tools (7)

### `find_parcels` (~633 tokens)

Find off-market 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 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.

Input parameters:

- `county` (string): County name as the county files it, for example Boulder, Larimer, Weld, Jefferson, Adams, Broomfield, Summit, Eagle, Grand (Colorado) or Henrico, Chesterfield (Virginia).
- `duplex_ok` (boolean): Zoning allows a duplex on the lot by right.
- `limit` (integer): How many parcels to return, at most 25 (default 10).
- `max_drive_city_mins` (integer): At most this many minutes by road to the nearest city.
- `max_drive_town_mins` (integer): At most this many minutes by road to the nearest town with a grocery store.
- `max_finished_sf` (integer): At most this many finished square feet.
- `max_tenure` (integer): Held at most this many years.
- `max_value` (integer): The county value is at most this many dollars.
- `max_year_built` (integer): Built in this year or earlier.
- `min_beds` (integer): At least this many bedrooms on the assessor's record.
- `min_finished_sf` (integer): At least this many finished square feet.
- `min_tenure` (integer): Held at least this many years since the last recorded sale.
- `min_value` (integer): The county value is at least this many dollars.
- `min_year_built` (integer): Built in this year or later.
- `offset` (integer): Skip this many parcels first (paging).
- `state` (string): CO or VA. Optional when county or zip is given.
- `teardown` (boolean): A teardown: an old or small house on land worth most of the value.
- `town` (string): A Colorado or Virginia town or city name, for example Lyons or Estes Park. Matched to the parcels within about five miles of the town.
- `trade` (string): The buyer's trade: one of the doors above. Omit for every parcel in the area.
- `water_rights` (boolean): Colorado only: a decreed water right whose point of diversion is on the lot. Virginia has no water rights to own.
- `wells` (boolean): Colorado only: a well permit on the lot.
- `zip` (string): A five-digit ZIP code.

### `town_stats` (~134 tokens)

Area parcel counts

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.

Input parameters:

- `county` (string): County name as the county files it.
- `state` (string): CO or VA. Optional when county or zip is given.
- `town` (string): A town or city name (parcels within about five miles).
- `zip` (string): A five-digit ZIP code.

### `check_parcel` (~187 tokens)

Check one 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, 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.

Input parameters:

- `address` (string): A street address, like 874 Cold Spring Rd.
- `key` (string): The shinnslist parcel key, like CO|Boulder|R0012345, from an earlier answer.
- `lat` (number): Latitude in decimal degrees, with lng.
- `lng` (number): Longitude in decimal degrees, with lat.
- `zip` (string): The five-digit ZIP, with address.

### `list_coverage` (~55 tokens)

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` (~53 tokens)

List proven 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` (~82 tokens)

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 value estimate comes to real sale prices (the buyer-price floor is the bar). Returns the current numbers and the page to cite.

### `run_signal` (~109 tokens)

Run a proven 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.

Input parameters:

- `lat` (number, required): Latitude in decimal degrees.
- `lng` (number, required): Longitude in decimal degrees.
- `signal` (string, required): A proven signal id from list_signals, like tax_delinquency_early_warning.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-shinnslist-shinnslist/api-mcp#diagnostics

## Score history

- 2026-11-05: 75
- 2026-11-04: 75
- 2026-11-03: 74
- 2026-11-02: 74
- 2026-11-01: 73
- 2026-10-31: 73
- 2026-10-30: 72
- 2026-10-29: 72
- 2026-10-28: 72
- 2026-10-27: 71
- 2026-10-26: 71
- 2026-10-25: 70
- 2026-10-24: 70
- 2026-10-23: 69

## Common questions

### What is the shinnslist MCP server?

shinnslist is an MCP server listed in the public MCP registry as com.shinnslist/shinnslist. Public-record parcel signals for off-market real estate. Free beta; only proven signals listed. This page covers its hosted endpoint (https://shinnslist.com/api/mcp).

### Is the shinnslist MCP server safe to use?

shinnslist scores 75 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 shinnslist MCP server expose?

shinnslist exposes 7 tools: find_parcels, town_stats, check_parcel, list_coverage, list_signals, and 2 more. Their descriptions and schemas cost roughly 1,253 tokens of context every time the server is loaded.

### Does the shinnslist MCP server require authentication?

No. We connected to shinnslist without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the shinnslist MCP server still maintained?

shinnslist 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://shinnslist.com/api/mcp
- Website: https://shinnslist.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-shinnslist-shinnslist/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-shinnslist-shinnslist/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-shinnslist-shinnslist/api-mcp