_ registry / mcp http-sse · checked 47m ago

fair-appraisers

https://mcp.fairappraisers.org

Registry code: 42178b52f30a5920

api record

Search public FAIR appraiser profiles by location, specialty, and intended use.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.fairappraisers.org/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
451ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 3 tools
2 open 1 never probed 2 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.

  • search_appraisers open 47m ago

    Search public FAIR appraiser registry profiles by location, ZIP, state, specialty, intended use, and radius. Use this when a user asks for local art, antique, jewelry, collectibles, estate, insurance, donation, court, lending, or personal-property appraiser candidates. FAIR surfaces candidate appraiser profiles. FAIR does not license appraisers, certify competence, certify reports, guarantee acceptance, or replace professional judgment.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "q": {
      "type": "string",
      "maxLength": 160,
      "minLength": 2,
      "description": "Optional text query across public profile fields."
    },
    "zip": {
      "type": "string",
      "maxLength": 16,
      "minLength": 5,
      "description": "US ZIP code for radius search."
    },
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1,
      "description": "Maximum number of profiles to return."
    },
    "state": {
      "type": "string",
      "maxLength": 2,
      "minLength": 2,
      "description": "Optional two-letter US state code."
    },
    "location": {
      "type": "string",
      "maxLength": 200,
      "minLength": 2,
      "description": "City/state or place name, such as Des Moines, IA."
    },
    "specialty": {
      "type": "string",
      "maxLength": 120,
      "minLength": 2,
      "description": "Specialty or category, such as fine art, jewelry, antiques, estate, or insurance."
    },
    "intended_use": {
      "type": "string",
      "maxLength": 80,
      "minLength": 2,
      "description": "Formal-use context such as estate, insurance, donation, IRS, court, lending, or tax."
    },
    "radius_miles": {
      "type": "number",
      "maximum": 250,
      "minimum": 1,
      "description": "Radius in miles when a location or ZIP is supplied."
    }
  }
}
    arguments 54 lines
  • explain_appraiser_routing open 47m ago

    Explain how to compare candidate appraisers for a formal appraisal need without treating FAIR as a certifier. Use this when the user needs routing guidance before or after a directory search.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "location": {
      "type": "string",
      "maxLength": 200,
      "minLength": 2,
      "description": "User location or service area."
    },
    "object_type": {
      "type": "string",
      "maxLength": 120,
      "minLength": 2,
      "description": "Object/category needing appraisal, such as painting, jewelry, antique furniture, or collectibles."
    },
    "intended_use": {
      "type": "string",
      "maxLength": 80,
      "minLength": 2,
      "description": "Formal-use context such as estate, insurance, donation, IRS, court, lending, or tax."
    }
  }
}
    arguments 24 lines
  • get_appraiser_profile unknown never probed

    Fetch one public FAIR appraiser registry profile by member id. Returns public source/status/fee-model fields only and includes the correction path. FAIR surfaces candidate appraiser profiles. FAIR does not license appraisers, certify competence, certify reports, guarantee acceptance, or replace professional judgment.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "FAIR directory member id."
    }
  }
}
    arguments 15 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.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/42178b52f30a5920/badge.svg)](https://brick.blue/agent/42178b52f30a5920)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ 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.