_ registry / mcp streamable-http · checked 2h ago

fairpath-public-mcp

https://mcp.fairpath.app

Registry code: 63b3904a52cdc71a

api record

FairPath exposes public informational property-tax tools. Calls create internal audit records, and property checks require explicit homeowner address consent and may create or reuse short-lived scoped session and consent records. The tools do not file, purchase, message, publish, or change public or external systems. FairPath prepares evidence packets; homeowners submit county filings themselves.

endpoint
https://mcp.fairpath.app/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is fairpath-public-mcp live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is fairpath-public-mcp free to use?
Not measured yet.
What tools does fairpath-public-mcp have?
3 tools: fairpath_explain_evidence_packet, fairpath_get_county_requirements, fairpath_check_property.
Is fairpath-public-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.7%· all time 99.7%

latency
315ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 303 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • look up property context for an address
  • get county property tax filing requirements
  • explain a property tax evidence packet
takes → gives
text → data, text
tools
3 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
3 never probed 0 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • fairpath_explain_evidence_packet changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • fairpath_get_county_requirements changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "countyId"
      ],
      "properties": {
        "countyId": {
          "type": "string",
          "minLength": 1,
          "description": "FairPath county id in the form county_state, for example johnson_ks, cook_il, or harris_tx."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • fairpath_check_property changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "address",
        "addressConsentGranted",
        "consentedAt",
        "consentEvidenceId"
      ],
      "properties": {
        "address": {
          "type": "string",
          "minLength": 1,
          "description": "The homeowner-provided property address to check."
        },
        "context": {
          "type": "object",
          "properties": {
            "source": {
              "enum": [
                "homeowner_prompt",
                "public_site",
                "partner_agent",
                "internal"
              ],
              "type": "string"
            },
            "sessionId": {
              "type": "string"
            },
            "countyHint": {
              "type": "string"
            }
          },
          "additionalProperties": false
        },
        "consentedAt": {
          "type": "string",
          "format": "date-time",
          "description": "When the homeowner explicitly approved this address lookup."
        },
        "consentEvidenceId": {
          "type": "string",
          "minLength": 8,
          "description": "Opaque, non-PII id for the client-side consent event. FairPath stores only its hash."
        },
        "addressConsentGranted": {
          "type": "boolean",
          "const": true,
          "description": "Must be true only after the homeowner explicitly consents to address lookup."
        }
      },
      "additionalProperties": false
    }
    arguments 53 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 63b3904a52cdc71a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/63b3904a52cdc71a/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/63b3904a52cdc71a/badge.svg)](https://brick.blue/agent/63b3904a52cdc71a?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.