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.

FairPath Property-Tax Evidence

REMOTE · MCP.FAIRPATH.APP

Sourced property-tax protest facts; homeowner reviews and files. Not a law firm; no outcome claims.

Available components

0 this week 87 Trust /100

Last scanned (23 hours ago)

Scores higher than 94% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Finance and Payments

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 Security80
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 368 tokens (~122/item across 3 items; 3 tools + 0 resources), lean.Pass
  • 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 Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 83% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (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.

  • 15 Oct 26 0
    • Stability: 0.97 → pass security
  • 14 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.

  • 12 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 90. That category is still filling its 30-day observation window: 25 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.

  • 10 Oct 26 +1

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

  • 7 Oct 26 +1

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

  • 5 Oct 26 +1

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

  • 3 Oct 26 +1

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

  • 28 Sept 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
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 4 Nov 2026 · Probed https://mcp.fairpath.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.fairpath.app CN=YR2,O=Let's Encrypt,C=US 12 Oct 2026 10 Jan 2027 RSA 2048 SHA256-RSA 5d7b78af9e6af12ca3d8e1bb1f4182d57d0
SANs: mcp.fairpath.app
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.fairpath.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
fairpath.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(self)

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.fairpath.app/mcp Verified 200
http (plaintext) http://mcp.fairpath.app/mcp HTTPS enforced 308 https://mcp.fairpath.app/mcp
MCP tools · 3 exposed · ~294 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
fairpath_check_property ~157

Look up a homeowner-provided address and return bounded property context. This requires explicit address consent, creates a private audit record, and may create or reuse short-lived scoped session and consent records. It does not expose owner, payment, or raw county records or change an external system.

NameTypeReqDescription
addressstringyesThe homeowner-provided property address to check.
addressConsentGrantedbooleanyesMust be true only after the homeowner explicitly consents to address lookup.
consentEvidenceIdstringyesOpaque, non-PII id for the client-side consent event. FairPath stores only its hash.
consentedAtstringyesWhen the homeowner explicitly approved this address lookup.
contextobject––
NameTypeReqDescription
complianceFooterobjectyes–
confidenceLevelstringyes–
countyCaveatsarrayyes–
countyKnowledgeDensityobject––
dataobjectyes–
directAnswerstringyes–
evidenceGapsarrayyes–
informationPosturestring–Transitional compatibility field: current broker responses include it, while older broker deployments may omit it during the coordinated rollout.
nextAvailableFairPathActionobjectyes–
redactionobjectyes–
sourcesUsedarrayyes–

No examples provided.

fairpath_explain_evidence_packet ~56

Explain the evidence categories FairPath can organize into a homeowner-reviewed property-tax evidence packet. This creates a private FairPath audit record but does not recommend a filing position, predict an outcome, or change an external system.

Input schema present but exposes no named parameters.

NameTypeReqDescription
complianceFooterobjectyes–
confidenceLevelstringyes–
countyCaveatsarrayyes–
countyKnowledgeDensityobject––
dataobjectyes–
directAnswerstringyes–
evidenceGapsarrayyes–
informationPosturestring–Transitional compatibility field: current broker responses include it, while older broker deployments may omit it during the coordinated rollout.
nextAvailableFairPathActionobjectyes–
redactionobjectyes–
sourcesUsedarrayyes–

No examples provided.

fairpath_get_county_requirements ~81

Return public, CIE-backed county property-tax filing guidance and source metadata. This creates a private FairPath audit record but does not make a filing recommendation or change an external system.

NameTypeReqDescription
countyIdstringyesFairPath county id in the form county_state, for example johnson_ks, cook_il, or harris_tx.
NameTypeReqDescription
complianceFooterobjectyes–
confidenceLevelstringyes–
countyCaveatsarrayyes–
countyKnowledgeDensityobject––
dataobjectyes–
directAnswerstringyes–
evidenceGapsarrayyes–
informationPosturestring–Transitional compatibility field: current broker responses include it, while older broker deployments may omit it during the coordinated rollout.
nextAvailableFairPathActionobjectyes–
redactionobjectyes–
sourcesUsedarrayyes–

No examples provided.

Install

How do I install the FairPath Property-Tax Evidence MCP server?

FairPath Property-Tax Evidence is a hosted endpoint at https://mcp.fairpath.app/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 · mcp.fairpath.app

# add to Claude Code
claude mcp add --transport http heintzsight-fairpath-property-tax-evidence 'https://mcp.fairpath.app/mcp'
Common questions

What is the FairPath Property-Tax Evidence MCP server?

FairPath Property-Tax Evidence is an MCP server listed in the public MCP registry as io.github.Heintzsight/fairpath-property-tax-evidence. Sourced property-tax protest facts; homeowner reviews and files. Not a law firm; no outcome claims. This page covers its hosted endpoint (https://mcp.fairpath.app/mcp).

Is the FairPath Property-Tax Evidence MCP server safe to use?

FairPath Property-Tax Evidence scores 87 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 FairPath Property-Tax Evidence MCP server expose?

FairPath Property-Tax Evidence exposes 3 tools: fairpath_get_county_requirements, fairpath_explain_evidence_packet, fairpath_check_property. Their descriptions and schemas cost roughly 294 tokens of context every time the server is loaded.

Does the FairPath Property-Tax Evidence MCP server require authentication?

No. We connected to FairPath Property-Tax Evidence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the FairPath Property-Tax Evidence MCP server still maintained?

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