shinnslist

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

使うべきか

品質と安全性

A
説明の品質
100%
スキーマの完全性
66%
命名の品質
94%
ポイズニングのリスク
100%
権限の一致
100%
プロトコルへの準拠
100%

ツール定義とプロトコルへの準拠に関する自動分析に基づいています。

コンテキストコスト

~1,760トークン数(ツール定義)
~1.7 KB一般的なレスポンスサイズ
注意への影響は中程度(128k コンテキストの 1.38%)

これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。

インストール

ワンクリックインストール

これを `claude_desktop_config.json` ファイルに追加してください:

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

リモートエンドポイント

https://shinnslist.com/api/mcpstreamable-http

できること

ツール一覧

ツール(7)

🟢 読み取り専用🟡 書き込み🔴 削除⚪ 不明
🟢find_parcels(state, county, town, zip, trade, ...)

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.

入力スキーマ

{
  "type": "object",
  "properties": {
    "state": {
      "type": "string",
      "enum": [
        "CO",
        "VA"
      ],
      "description": "CO or VA. Optional when county or zip is given."
    },
    "county": {
      "type": "string",
      "description": "County name as the county files it, for example Boulder, Larimer, Weld, Jefferson, Adams, Broomfield, Summit, Eagle, Grand (Colorado) or Henrico, Chesterfield (Virginia)."
    },
    "town": {
      "type": "string",
      "description": "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."
    },
    "zip": {
      "type": "string",
      "description": "A five-digit ZIP code."
    },
    "trade": {
      "type": "string",
      "enum": [
        "wholesaler",
        "str_investor",
        "realtor",
        "flipper",
        "developer",
        "cash_investor",
        "brrr",
        "land",
        "two_households"
      ],
      "description": "The buyer's trade: one of the doors above. Omit for every parcel in the area."
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 25,
      "description": "How many parcels to return, at most 25 (default 10)."
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "description": "Skip this many parcels first (paging)."
    },
    "min_value": {
      "type": "integer",
      "minimum": 0,
      "description": "The county value is at least this many dollars."
    },
    "max_value": {
      "type": "integer",
      "minimum": 0,
      "description": "The county value is at most this many dollars."
    },
    "min_tenure": {
      "type": "integer",
      "minimum": 0,
      "description": "Held at least this many years since the last recorded sale."
    },
    "max_tenure": {
      "type": "integer",
      "minimum": 0,
      "description": "Held at most this many years."
    },
    "min_beds": {
      "type": "integer",
      "minimum": 1,
      "description": "At least this many bedrooms on the assessor's record."
    },
    "min_finished_sf": {
      "type": "integer",
      "minimum": 0,
      "description": "At least this many finished square feet."
    },
    "max_finished_sf": {
      "type": "integer",
      "minimum": 0,
      "description": "At most this many finished square feet."
    },
    "min_year_built": {
      "type": "integer",
      "minimum": 0,
      "description": "Built in this year or later."
    },
    "max_year_built": {
      "type": "integer",
      "minimum": 0,
      "description": "Built in this year or earlier."
    },
    "max_drive_town_mins": {
      "type": "integer",
      "minimum": 1,
      "description": "At most this many minutes by road to the nearest town with a grocery store."
    },
    "max_drive_city_mins": {
      "type": "integer",
      "minimum": 1,
      "description": "At most this many minutes by road to the nearest city."
    },
    "water_rights": {
      "type": "boolean",
      "description": "Colorado only: a decreed water right whose point of diversion is on the lot. Virginia has no water rights to own."
    },
    "wells": {
      "type": "boolean",
      "description": "Colorado only: a well permit on the lot."
    },
    "teardown": {
      "type": "boolean",
      "description": "A teardown: an old or small house on land worth most of the value."
    },
    "duplex_ok": {
      "type": "boolean",
      "description": "Zoning allows a duplex on the lot by right."
    }
  }
}
🟢town_stats(state, county, town, zip)

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.

入力スキーマ

{
  "type": "object",
  "properties": {
    "state": {
      "type": "string",
      "enum": [
        "CO",
        "VA"
      ],
      "description": "CO or VA. Optional when county or zip is given."
    },
    "county": {
      "type": "string",
      "description": "County name as the county files it."
    },
    "town": {
      "type": "string",
      "description": "A town or city name (parcels within about five miles)."
    },
    "zip": {
      "type": "string",
      "description": "A five-digit ZIP code."
    }
  }
}
🟢check_parcel(key, address, zip, lat, lng)

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.

入力スキーマ

{
  "type": "object",
  "properties": {
    "key": {
      "type": "string",
      "description": "The shinnslist parcel key, like CO|Boulder|R0012345, from an earlier answer."
    },
    "address": {
      "type": "string",
      "description": "A street address, like 874 Cold Spring Rd."
    },
    "zip": {
      "type": "string",
      "description": "The five-digit ZIP, with address."
    },
    "lat": {
      "type": "number",
      "description": "Latitude in decimal degrees, with lng."
    },
    "lng": {
      "type": "number",
      "description": "Longitude in decimal degrees, with lat."
    }
  }
}
🟢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.

入力スキーマ

{
  "type": "object",
  "properties": {}
}
🟢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.

入力スキーマ

{
  "type": "object",
  "properties": {}
}
🟢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.

入力スキーマ

{
  "type": "object",
  "properties": {}
}
🟢run_signal(signal, lat, lng)

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.

入力スキーマ

{
  "type": "object",
  "properties": {
    "signal": {
      "type": "string",
      "description": "A proven signal id from list_signals, like tax_delinquency_early_warning."
    },
    "lat": {
      "type": "number",
      "description": "Latitude in decimal degrees."
    },
    "lng": {
      "type": "number",
      "description": "Longitude in decimal degrees."
    }
  },
  "required": [
    "signal",
    "lat",
    "lng"
  ]
}

コミュニティ

このサーバーを評価する

エビデンス

最近の観測

検証済みバージョンは記録されていませんツール 7 件