Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

co.addressintel/permits

NPM · ADDRESSINTEL-MCP

SF Peninsula building permits and parcel buildability: SB 9, ADU and redevelopment leads.

Available components

+3 this week 94 Trust /100

Last scanned (17 hours ago)

Scores higher than 97% of npm servers

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to RantumBits/addressintel-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 58 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 867 tokens (~144/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 16 Oct 26 0
    • Stability: 0.97 → pass security
  • 15 Oct 26 +1

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

  • 13 Oct 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 11 Oct 26 +1
    • Security disclosure: fail → unverified ▼ functional
  • 3 Oct 26 −3
    • Stability: pass → 0.77 functional
  • 2 Oct 26 0
    • Stability: 0.97 → pass security
  • 1 Oct 26 +1

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

  • 29 Sept 26 +1

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

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 16 Oct 2026 · Analysed npm/addressintel-mcp@1.1.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo RantumBits/addressintel-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/RantumBits/addressintel-mcp/.github/workflows/publish.yml@refs/tags/v1.1.2
Rekor log index 2511877681
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:ca05782044f7a3eb583a6ba0757e8e09515add6623c54993f79f6635ccef2174dd726de79660901eed911ccae4d6cfdc36ebfce6d0d27140cf1e461f0

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~867 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_property_intelligence ~129

Get detailed AI intelligence for a specific property. Takes an id from list_market_signals. Returns teardown and flippability scores, a market heat index, an AI briefing, comparable-sale counts with an average price per sqft, and parcel enrichment (zoning, lot size, development class). Those scores rank candidates; none of them is a return. This endpoint carries no ROI figure at all: for that, read proformaROI from list_market_signals, which is arithmetic rather than a model estimate.

NameTypeReqDescription
idstringyesThe unique identifier (ID) of the property to analyze

No output schema declared.

No examples provided.

list_adu_leads ~101

List parcels ranked by ADU (accessory dwelling unit) feasibility, including estimated max units, buildable square footage and the lot geometry behind the score.

NameTypeReqDescription
excludeBlockersboolean–Drop parcels carrying any development blocker.
limitnumber–Max rows to return. Clamped to your API key's tier ceiling.
minScorenumber–Minimum ADU feasibility score, 0-100. Defaults to 60.

No output schema declared.

No examples provided.

list_market_signals ~209

Search for high-signal real estate investment opportunities (teardowns, flips). Use this to find properties before diving into specific details. Each result carries proformaROI, a net teardown ROI computed by arithmetic rather than by a model, with a proforma object holding its inputs and assumptions ($400/sqft build, 5% cost of sale, build sized to the zoning envelope). Quote those assumptions alongside the number. null means not modellable, with unmodellableReason naming the missing input: treat it as unknown, never as zero. Negatives are normal here; most of this market does not pencil.

NameTypeReqDescription
addressstring–Search for a specific address
citystring–Filter by city name (e.g. 'Atherton')
limitnumber–Max rows to return. Clamped to your API key's tier ceiling.
marketstring–Filter by market (e.g. 'sf-peninsula' or 'nantucket')

No output schema declared.

No examples provided.

list_redevelopment_leads ~121

List underbuilt parcels: small, older homes using a low share of their allowable building envelope on sizable lots. Ranked by redevelopment score, with the FAR headroom that produced it.

NameTypeReqDescription
classstring–Narrow to scrape-and-rebuild candidates or expansion candidates.
excludeBlockersboolean–Drop parcels carrying any development blocker.
limitnumber–Max rows to return. Clamped to your API key's tier ceiling.
minScorenumber–Minimum redevelopment score, 0-100. Defaults to 60.

No output schema declared.

No examples provided.

list_sb9_inventory ~133

List active listings that are eligible for an SB 9 lot split or duplex conversion, with the per-parcel block reasons where they are not. California-only; this is a parcel-level buildability read, not a generic lead list.

NameTypeReqDescription
excludeBlockersboolean–Drop parcels carrying any development blocker.
limitnumber–Max rows to return. Clamped to your API key's tier ceiling.
minUnitsnumber–Only parcels supporting at least this many SB 9 units.
statusstring–Filter by SB 9 status. Defaults to any non-blocked parcel.

No output schema declared.

No examples provided.

search_permits ~174

Search issued building permits across the SF Peninsula and adjacent Silicon Valley cities. Filter by city, keyword (address, project type, scope description, contractor, architect or permit number) and minimum valuation. Use this to find what construction has actually been permitted at an address or in a city.

NameTypeReqDescription
citystring–City name, e.g. 'Menlo Park'. Partial matches allowed.
limitnumber–Max rows to return. Clamped to your API key's tier ceiling.
minValuationnumber–Only permits valued at or above this dollar amount.
offsetnumber–Row offset for paging.
qstring–Keyword matched against address, project type, scope description, contractor, architect and permit number, e.g. 'demolition' or '123 Main St'.

No output schema declared.

No examples provided.

Install

How do I install the co.addressintel/permits MCP server?

co.addressintel/permits runs locally as an npm package, launched with npx -y addressintel-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · addressintel-mcp

# add to Claude Code
claude mcp add co-addressintel-permits -- npx -y addressintel-mcp
Common questions

What is the co.addressintel/permits MCP server?

co.addressintel/permits is an MCP server listed in the public MCP registry as co.addressintel/permits. SF Peninsula building permits and parcel buildability: SB 9, ADU and redevelopment leads. This page covers its npm package (addressintel-mcp).

Is the co.addressintel/permits MCP server safe to use?

co.addressintel/permits scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 co.addressintel/permits MCP server expose?

co.addressintel/permits exposes 6 tools: search_permits, list_sb9_inventory, list_adu_leads, list_redevelopment_leads, list_market_signals, get_property_intelligence. Their descriptions and schemas cost roughly 867 tokens of context every time the server is loaded.

Is the co.addressintel/permits MCP server still maintained?

co.addressintel/permits is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the co.addressintel/permits MCP server under?

co.addressintel/permits declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.