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.

LocalProof

REMOTE · LOCALPROOF.DAVISVILLELABS.COM

Local government intelligence for AI agents.

0 this week 23 Trust /100

Last scanned (12 hours ago)

Scores higher than 7% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (5)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (6)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Oct 26 −54
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: fail → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • HSTS header: pass → fail ▼ security
    • HTTPS: unverified → pass ▲ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 55 to 59.

  • 2 Oct 26 0
    • Stability: 0.10 → fail ▼ security
    • Tool “localproof.check_local_changes” was removed ▼ security
    • Tool “localproof.check_property” was removed ▼ security
    • Tool “localproof.development_due_diligence” was removed ▼ security
    • Tool “localproof.property_intelligence_pack” was removed ▼ security
    • Tool “localproof.site_selection_compare” was removed ▼ security
    • Tool “localproof.check_code_enforcement” rewrote its description, which is the text the model reads security
    • Tool “localproof.check_parcel_context” rewrote its description, which is the text the model reads security
    • Tool “localproof.check_permit_routing” rewrote its description, which is the text the model reads security
    • Tool “localproof.check_permits” rewrote its description, which is the text the model reads security
    • Tool “localproof.check_planning_activity” rewrote its description, which is the text the model reads security
    • Tool “localproof.check_property_changes” rewrote its description, which is the text the model reads security
    • Tool “localproof.check_zoning_context” rewrote its description, which is the text the model reads security
    • Tool “localproof.get_coverage” rewrote its description, which is the text the model reads security
    • Tool “localproof.get_source_catalog” rewrote its description, which is the text the model reads security
    • Tool “localproof.get_source_health” rewrote its description, which is the text the model reads security
    • Tool “localproof.resolve_jurisdiction” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • Tool coverage: 0% → 100% ▲ functional
    • Schema quality: good → excellent functional
    • Server version: 0.31.31 → 0.31.32 functional
    • New tool “localproof.build_development_due_diligence” functional
    • New tool “localproof.build_property_intelligence_pack” functional
    • New tool “localproof.compare_sites” functional
    • “localproof.check_code_enforcement” reworded the description of “address” cosmetic
    • “localproof.check_code_enforcement” reworded the description of “city” cosmetic
    • “localproof.check_code_enforcement” reworded the description of “state” cosmetic
    • “localproof.check_code_enforcement” reworded the description of “unit” cosmetic
    • “localproof.check_parcel_context” reworded the description of “address” cosmetic
    • “localproof.check_parcel_context” reworded the description of “city” cosmetic
    • “localproof.check_parcel_context” reworded the description of “state” cosmetic
    • “localproof.check_parcel_context” reworded the description of “unit” cosmetic
    • “localproof.check_permit_routing” reworded the description of “address” cosmetic
    • “localproof.check_permit_routing” reworded the description of “city” cosmetic
    • “localproof.check_permit_routing” reworded the description of “state” cosmetic
    • “localproof.check_permit_routing” reworded the description of “unit” cosmetic
    • “localproof.check_permits” reworded the description of “address” cosmetic
    • “localproof.check_permits” reworded the description of “city” cosmetic
    • “localproof.check_permits” reworded the description of “state” cosmetic
    • “localproof.check_permits” reworded the description of “unit” cosmetic
    • “localproof.check_planning_activity” reworded the description of “address” cosmetic
    • “localproof.check_planning_activity” reworded the description of “city” cosmetic
    • “localproof.check_planning_activity” reworded the description of “state” cosmetic
    • “localproof.check_planning_activity” reworded the description of “unit” cosmetic
    • “localproof.check_property_changes” reworded the description of “address” cosmetic
    • “localproof.check_property_changes” reworded the description of “city” cosmetic
    • “localproof.check_property_changes” reworded the description of “since” cosmetic
    • “localproof.check_property_changes” reworded the description of “state” cosmetic
    • “localproof.check_property_changes” reworded the description of “unit” cosmetic
    • “localproof.check_zoning_context” reworded the description of “address” cosmetic
    • “localproof.check_zoning_context” reworded the description of “city” cosmetic
    • “localproof.check_zoning_context” reworded the description of “state” cosmetic
    • “localproof.check_zoning_context” reworded the description of “unit” cosmetic
    • “localproof.get_coverage” reworded the description of “city” cosmetic
    • “localproof.get_coverage” reworded the description of “jurisdiction_id” cosmetic
    • “localproof.get_coverage” reworded the description of “state” cosmetic
    • “localproof.get_source_catalog” reworded the description of “city” cosmetic
    • “localproof.get_source_catalog” reworded the description of “jurisdiction_id” cosmetic
    • “localproof.get_source_catalog” reworded the description of “state” cosmetic
    • “localproof.get_source_health” reworded the description of “city” cosmetic
    • “localproof.get_source_health” reworded the description of “jurisdiction_id” cosmetic
    • “localproof.get_source_health” reworded the description of “state” cosmetic
    • “localproof.resolve_jurisdiction” reworded the description of “address” cosmetic
    • “localproof.resolve_jurisdiction” reworded the description of “city” cosmetic
    • “localproof.resolve_jurisdiction” reworded the description of “state” cosmetic
    • “localproof.resolve_jurisdiction” reworded the description of “unit” cosmetic
  • 29 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 0.31.30 → 0.31.31 functional
    • Server version: 0.31.28 → 0.31.30 functional
    • Server version: 0.31.27 → 0.31.28 functional
  • 28 Sept 26 0

    First indexed and scored.

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 21 Nov 2026 · Probed https://localproof.davisvillelabs.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=davisvillelabs.com CN=WE1,O=Google Trust Services,C=US 27 Sept 2026 26 Dec 2026 ECDSA 256 ECDSA-SHA256 a4aba0a8e7dee1eb0ef0d40ca600ef23
SANs: davisvillelabs.com, localproof.davisvillelabs.com, *.localproof.davisvillelabs.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of localproof.davisvillelabs.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
davisvillelabs.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 301

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://localproof.davisvillelabs.com/mcp Redirected 301 https://davisvillelabs.com/
http (plaintext) http://localproof.davisvillelabs.com/mcp HTTPS enforced 301 https://davisvillelabs.com/
MCP tools · 14 exposed · ~2,033 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
localproof.build_development_due_diligence ~173

Paid $2.95 USD. Build the deepest released San Francisco development evidence package with cross-source chronology, attention items, completeness, source gaps, provenance, and repeat-poll guidance through check_property_changes. Use this for development due diligence; use build_property_intelligence_pack for a lighter current snapshot. Unsupported or held jurisdictions fail before payment.

NameTypeReqDescription
addressstringyesStreet address or place to research. Include locality information when available.
citystring–Optional city used to disambiguate the address and route it to a supported LocalProof jurisdiction.
statestring–Optional state name or abbreviation. Current released jurisdictions are in California; use CA or California.
unitstring–Optional unit, suite, or apartment identifier when it is relevant to property identity.

Structured output declared, but exposes no named fields.

No examples provided.

localproof.build_property_intelligence_pack ~166

Paid $0.25 USD. Build the broad released multi-source property package with completeness, source gaps, provenance, and repeat-poll guidance through check_property_changes. Use this for a comprehensive current property view; use focused check_* tools when only one evidence class is needed. Unsupported or held jurisdictions fail before payment.

NameTypeReqDescription
addressstringyesStreet address or place to research. Include locality information when available.
citystring–Optional city used to disambiguate the address and route it to a supported LocalProof jurisdiction.
statestring–Optional state name or abbreviation. Current released jurisdictions are in California; use CA or California.
unitstring–Optional unit, suite, or apartment identifier when it is relevant to property identity.

Structured output declared, but exposes no named fields.

No examples provided.

localproof.check_code_enforcement ~147

Paid $0.25 USD. Reconcile released code-enforcement and complaint records for one property. Use this for enforcement evidence; use build_property_intelligence_pack for a broader package. Unsupported or held jurisdictions fail before payment.

NameTypeReqDescription
addressstringyesStreet address or place to research. Include locality information when available.
citystring–Optional city used to disambiguate the address and route it to a supported LocalProof jurisdiction.
statestring–Optional state name or abbreviation. Current released jurisdictions are in California; use CA or California.
unitstring–Optional unit, suite, or apartment identifier when it is relevant to property identity.

Structured output declared, but exposes no named fields.

No examples provided.

localproof.check_parcel_context ~161

Paid $0.06 USD. Return privacy-minimized official parcel and land-use attributes where a supported parcel source is released. Use this for parcel facts; use check_zoning_context for released zoning context or build_property_intelligence_pack for cross-source context. Unsupported or held jurisdictions fail before payment.

NameTypeReqDescription
addressstringyesStreet address or place to research. Include locality information when available.
citystring–Optional city used to disambiguate the address and route it to a supported LocalProof jurisdiction.
statestring–Optional state name or abbreviation. Current released jurisdictions are in California; use CA or California.
unitstring–Optional unit, suite, or apartment identifier when it is relevant to property identity.

Structured output declared, but exposes no named fields.

No examples provided.

localproof.check_permit_routing ~151

Paid $0.25 USD. Trace released San Francisco permit review routing, departments, holds, timing, and recorded outcomes. Use this for administrative routing state; use check_permits for permit records. Unsupported or held jurisdictions fail before payment.

NameTypeReqDescription
addressstringyesStreet address or place to research. Include locality information when available.
citystring–Optional city used to disambiguate the address and route it to a supported LocalProof jurisdiction.
statestring–Optional state name or abbreviation. Current released jurisdictions are in California; use CA or California.
unitstring–Optional unit, suite, or apartment identifier when it is relevant to property identity.

Structured output declared, but exposes no named fields.

No examples provided.

localproof.check_permits ~162

Paid $0.09 USD. Reconcile current official permit records for one resolved property where permit coverage is released. Use this for permit detail; use check_permit_routing for San Francisco review routing and holds or build_property_intelligence_pack for cross-source context. Unsupported or held jurisdictions fail before payment.

NameTypeReqDescription
addressstringyesStreet address or place to research. Include locality information when available.
citystring–Optional city used to disambiguate the address and route it to a supported LocalProof jurisdiction.
statestring–Optional state name or abbreviation. Current released jurisdictions are in California; use CA or California.
unitstring–Optional unit, suite, or apartment identifier when it is relevant to property identity.

Structured output declared, but exposes no named fields.

No examples provided.

localproof.check_planning_activity ~155

Paid $0.25 USD. Reconcile released planning applications and entitlement activity for one property. Use this for planning records; use check_zoning_context for current zoning context or build_property_intelligence_pack for multi-source context. Unsupported or held jurisdictions fail before payment.

NameTypeReqDescription
addressstringyesStreet address or place to research. Include locality information when available.
citystring–Optional city used to disambiguate the address and route it to a supported LocalProof jurisdiction.
statestring–Optional state name or abbreviation. Current released jurisdictions are in California; use CA or California.
unitstring–Optional unit, suite, or apartment identifier when it is relevant to property identity.

Structured output declared, but exposes no named fields.

No examples provided.

localproof.check_property_changes ~202

Paid $0.03 USD. Find timestamped changes after an ISO 8601 since value across released evidence dimensions for a resolved property, currently comprehensive in San Francisco. Use this for repeat polling; use check_permits for current permit detail or build_property_intelligence_pack for a full current snapshot. Unsupported or held jurisdictions fail before payment.

NameTypeReqDescription
addressstringyesStreet address or place to research. Include locality information when available.
citystring–Optional city used to disambiguate the address and route it to a supported LocalProof jurisdiction.
sincestringyesISO 8601 date or date-time. LocalProof returns supported changes observed after this instant; the value cannot be in the future.
statestring–Optional state name or abbreviation. Current released jurisdictions are in California; use CA or California.
unitstring–Optional unit, suite, or apartment identifier when it is relevant to property identity.

Structured output declared, but exposes no named fields.

No examples provided.

localproof.check_zoning_context ~150

Paid $0.01 USD. Return released official zoning context for a resolved property. Use this for zoning evidence, not a proposed-use or legal determination; use check_parcel_context for parcel attributes. Unsupported or held jurisdictions fail before payment.

NameTypeReqDescription
addressstringyesStreet address or place to research. Include locality information when available.
citystring–Optional city used to disambiguate the address and route it to a supported LocalProof jurisdiction.
statestring–Optional state name or abbreviation. Current released jurisdictions are in California; use CA or California.
unitstring–Optional unit, suite, or apartment identifier when it is relevant to property identity.

Structured output declared, but exposes no named fields.

No examples provided.

localproof.compare_sites ~88

Paid $0.49 USD. Compare two or three distinct candidate San Francisco sites across the same released evidence dimensions without selecting a winner. Use this for side-by-side site evidence; use build_property_intelligence_pack for one site. Unsupported or held jurisdictions fail before payment.

NameTypeReqDescription
sitesarrayyesTwo or three candidate sites to compare. Each site must resolve to a distinct supported property.

Structured output declared, but exposes no named fields.

No examples provided.

localproof.get_coverage ~107

Free. Return released and held jurisdiction and operation coverage without querying property records. Use this to plan routing; use resolve_jurisdiction when you have a specific address.

NameTypeReqDescription
citystring–Optional city name used when jurisdiction_id is not supplied.
jurisdiction_idstring–Canonical LocalProof jurisdiction identifier returned by resolve_jurisdiction or get_coverage.
statestring–Optional state name or abbreviation paired with city. Current released jurisdictions are in California.

Structured output declared, but exposes no named fields.

No examples provided.

localproof.get_source_catalog ~104

Free. Return registered authoritative sources and freshness expectations for a jurisdiction. Use this to understand evidence sources; use get_source_health for current endpoint reachability.

NameTypeReqDescription
citystring–Optional city name used when jurisdiction_id is not supplied.
jurisdiction_idstring–Canonical LocalProof jurisdiction identifier returned by resolve_jurisdiction or get_coverage.
statestring–Optional state name or abbreviation paired with city. Current released jurisdictions are in California.

Structured output declared, but exposes no named fields.

No examples provided.

localproof.get_source_health ~114

Free. Probe registered official-source reachability for a jurisdiction without returning source records. Use this for current source availability; use get_source_catalog for source identity and freshness expectations. Reachability is not completeness.

NameTypeReqDescription
citystring–Optional city name used when jurisdiction_id is not supplied.
jurisdiction_idstring–Canonical LocalProof jurisdiction identifier returned by resolve_jurisdiction or get_coverage.
statestring–Optional state name or abbreviation paired with city. Current released jurisdictions are in California.

Structured output declared, but exposes no named fields.

No examples provided.

localproof.resolve_jurisdiction ~153

Free. Resolve one address or place to a supported LocalProof jurisdiction and coverage state before deeper research. Use this when jurisdiction support is unknown; use get_coverage to inspect published coverage without resolving a property. Held or unsupported jurisdictions fail closed before paid work.

NameTypeReqDescription
addressstringyesStreet address or place to research. Include locality information when available.
citystring–Optional city used to disambiguate the address and route it to a supported LocalProof jurisdiction.
statestring–Optional state name or abbreviation. Current released jurisdictions are in California; use CA or California.
unitstring–Optional unit, suite, or apartment identifier when it is relevant to property identity.

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the LocalProof MCP server?

LocalProof is a hosted endpoint at https://localproof.davisvillelabs.com/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.

remote · localproof.davisvillelabs.com

# add to Claude Code
claude mcp add --transport http davisvillelabs-localproof 'https://localproof.davisvillelabs.com/mcp'
Common questions

What is the LocalProof MCP server?

LocalProof is an MCP server listed in the public MCP registry as io.github.davisvillelabs/localproof. Local government intelligence for AI agents. This page covers its hosted endpoint (https://localproof.davisvillelabs.com/mcp).

Is the LocalProof MCP server safe to use?

LocalProof scores 23 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 LocalProof MCP server expose?

LocalProof exposes 14 tools: localproof.resolve_jurisdiction, localproof.get_coverage, localproof.get_source_catalog, localproof.get_source_health, localproof.check_property_changes, and 9 more. Their descriptions and schemas cost roughly 2,033 tokens of context every time the server is loaded.

Does the LocalProof MCP server require authentication?

Its publisher declares no required credentials for LocalProof. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the LocalProof MCP server still maintained?

LocalProof is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the LocalProof MCP server?

VerifyMCP ran 5 checks on LocalProof, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about LocalProof: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.