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

portlandmaps-mcp-v2

https://portlandmaps-mcp.vercel.app

Registry code: ef3754936e18a558

api record

Unofficial MCP server for PortlandMaps: public property, permit, zoning, land-use, sewer, and parcel data for Portland, Oregon (Multnomah, Clackamas, and Washington counties). Not affiliated with or endorsed by the City of Portland.

Most detail lookups are keyed by a Taxlots Property ID, not by address. Start with suggest_portlandmaps_address to turn an address, intersection, landmark, or partial ID into candidates carrying the IDs the other tools need. Then:

endpoint
https://portlandmaps-mcp.vercel.app/mcp/v2
protocol
http-sse ·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 portlandmaps-mcp-v2 live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is portlandmaps-mcp-v2 free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does portlandmaps-mcp-v2 have?
11 tools: query_intersects, convert_geometry, get_portlandmaps_detail, render_parcel_shape, search_sewer_records, suggest_portlandmaps_address, lookup_agol, list_detail_types, ….
Is portlandmaps-mcp-v2 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
781ms

last good check

priced tools
0

of 11 tools

_ answered our checks, 90 days 330 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • look up a portland property by address
  • get zoning and permit records
  • search land use review cases
  • get assessor data
  • render a parcel shape
takes → gives
text → data, images
tools
11 reads
_ 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 11 tools
2 open2 auth-required 7 never probed 4 of 11 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.

  • list_detail_types reads open 19h ago

    Return the detail_type values accepted by get_portlandmaps_detail and the identifier each expects.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • get_assessor_data reads open 19h ago

    1:1 wrapper for /api/assessor/. Search assessor records by address, property IDs, geometry, or assessor filters.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "city": {
          "type": "string"
        },
        "page": {
          "type": "integer",
          "exclusiveMinimum": 0
        },
        "cache": {
          "$ref": "#/properties/primary"
        },
        "count": {
          "type": "integer",
          "maximum": 1000,
          "exclusiveMinimum": 0
        },
        "county": {
          "enum": [
            "Multnomah",
            "Clackamas",
            "Washington"
          ],
          "type": "string"
        },
        "address": {
          "type": "string"
        },
        "primary": {
          "anyOf": [
            {
              "type": "boolean"
            },
            {
              "type": "number",
              "const": 0
            },
            {
              "type": "number",
              "const": 1
            }
          ]
        },
        "stateId": {
          "type": "string",
          "description": "Maps to state_id."
        },
        "zipCode": {
          "type": "string",
          "description": "Maps to zip_code."
        },
        "download": {
          "$ref": "#/properties/primary"
        },
        "geometry": {
          "anyOf": [
            {
              "type": "object",
              "additionalProperties": {}
            },
            {
              "type": "string"
            }
          ]
        },
        "soldAfter": {
          "type": "string",
          "description": "Maps to sold_after, mm/dd/yyyy."
        },
        "sortField": {
          "type": "string",
          "description": "Maps to sort_field."
        },
        "sortOrder": {
          "enum": [
            "asc",
            "desc"
          ],
          "type": "string",
          "description": "Maps to sort_order."
        },
        "builtAfter": {
          "type": "integer",
          "description": "Maps to built_after."
        },
        "propertyId": {
          "type": "string",
          "description": "Maps to property_id."
        },
        "soldBefore": {
          "type": "string",
          "description": "Maps to sold_before, mm/dd/yyyy."
        },
        "sqftLarger": {
          "type": "number",
          "description": "Maps to sqft_larger."
        },
        "builtBefore": {
          "type": "integer",
          "description": "Maps to built_before."
        },
        "extraParams": {
          "type": "object",
          "additionalProperties": {}
        },
        "sqftSmaller": {
          "type": "number",
          "description": "Maps to sqft_smaller."
        },
        "marketLarger": {
          "type": "number",
          "description": "Maps to market_larger."
        },
        "marketSmaller": {
          "type": "number",
          "description": "Maps to market_smaller."
        },
        "parentStateId": {
          "type": "string",
          "description": "Maps to parent_state_id."
        },
        "altAccountNumber": {
          "type": "string",
          "description": "Maps to alt_account_number."
        },
        "legalDescription": {
          "type": "string",
          "description": "Maps to legal_description."
        }
      },
      "additionalProperties": false
    }
    arguments 134 lines
  • get_permit_data reads auth-required 19h ago

    1:1 wrapper for /api/permit/. Search building/trade/enforcement permit records. ANSWER GUIDANCE: when this data answers a resident's zoning, permit, property, or city-code question, write for a Portland resident or small-business owner with no code, zoning, or permitting background. Lead with a 3–5 sentence plain-English summary (never open with a data table). Then cite EVERY rule, fee, number, timeline, or contact INLINE in the same sentence with both its exact code section AND a full https:// portland.gov URL (e.g. PCC 33.110.255.C, https://www.portland.gov/code/33/110/255) — never cite vaguely ("Title 33", "the BDS website") and never drop the URL. Define every acronym, add a numbered "what to do next" list, and if a number can't be cited to a specific section + URL, say so rather than stating it bare.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "page": {
          "type": "integer",
          "exclusiveMinimum": 0
        },
        "cache": {
          "anyOf": [
            {
              "type": "boolean"
            },
            {
              "type": "number",
              "const": 0
            },
            {
              "type": "number",
              "const": 1
            }
          ]
        },
        "count": {
          "type": "integer",
          "maximum": 1000,
          "exclusiveMinimum": 0
        },
        "county": {
          "type": "string"
        },
        "dateTo": {
          "type": "string",
          "description": "Maps to date_to, mm/dd/yyyy."
        },
        "address": {
          "type": "string"
        },
        "stateId": {
          "type": "string",
          "description": "Maps to state_id."
        },
        "dateFrom": {
          "type": "string",
          "description": "Maps to date_from, mm/dd/yyyy."
        },
        "dateType": {
          "enum": [
            "issued",
            "review",
            "final"
          ],
          "type": "string",
          "description": "Maps to date_type."
        },
        "download": {
          "$ref": "#/properties/cache"
        },
        "ccbNumber": {
          "type": "string",
          "description": "Maps to ccb_number."
        },
        "ivrNumber": {
          "type": "integer",
          "description": "Maps to ivr_number."
        },
        "sortField": {
          "type": "string",
          "description": "Maps to sort_field."
        },
        "sortOrder": {
          "enum": [
            "asc",
            "desc"
          ],
          "type": "string",
          "description": "Maps to sort_order."
        },
        "propertyId": {
          "type": "string",
          "description": "Maps to property_id."
        },
        "extraParams": {
          "type": "object",
          "additionalProperties": {}
        },
        "neighborhood": {
          "type": "string"
        },
        "searchTypeId": {
          "type": "integer",
          "description": "Maps to search_type_id."
        },
        "applicationNumber": {
          "type": "string",
          "description": "Maps to application_number."
        },
        "businessAssociation": {
          "type": "string",
          "description": "Maps to business_association."
        },
        "neighborhoodDistrict": {
          "type": "string",
          "description": "Maps to neighborhood_district."
        }
      },
      "additionalProperties": false
    }
    arguments 108 lines
  • search_landuse_cases reads auth-required 15h ago

    1:1 wrapper for /api/landuse/. Search land use review cases, including Historic Resource Review and Tree Review. ANSWER GUIDANCE: when this data answers a resident's zoning, permit, property, or city-code question, write for a Portland resident or small-business owner with no code, zoning, or permitting background. Lead with a 3–5 sentence plain-English summary (never open with a data table). Then cite EVERY rule, fee, number, timeline, or contact INLINE in the same sentence with both its exact code section AND a full https:// portland.gov URL (e.g. PCC 33.110.255.C, https://www.portland.gov/code/33/110/255) — never cite vaguely ("Title 33", "the BDS website") and never drop the URL. Define every acronym, add a numbered "what to do next" list, and if a number can't be cited to a specific section + URL, say so rather than stating it bare.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "page": {
          "type": "integer",
          "default": 1,
          "exclusiveMinimum": 0
        },
        "cache": {
          "anyOf": [
            {
              "type": "boolean"
            },
            {
              "type": "number",
              "const": 0
            },
            {
              "type": "number",
              "const": 1
            }
          ]
        },
        "count": {
          "type": "integer",
          "default": 100,
          "maximum": 1000,
          "exclusiveMinimum": 0
        },
        "dateTo": {
          "type": "string",
          "description": "Maps to date_to, mm/dd/yyyy."
        },
        "dateFrom": {
          "type": "string",
          "description": "Maps to date_from, mm/dd/yyyy."
        },
        "download": {
          "$ref": "#/properties/cache"
        },
        "ivrNumber": {
          "type": "integer",
          "description": "Maps to ivr_number."
        },
        "sortField": {
          "type": "string",
          "description": "Maps to sort_field."
        },
        "sortOrder": {
          "enum": [
            "asc",
            "desc"
          ],
          "type": "string",
          "description": "Maps to sort_order."
        },
        "extraParams": {
          "type": "object",
          "additionalProperties": {}
        },
        "neighborhood": {
          "type": "string"
        },
        "planDistrict": {
          "type": "string",
          "description": "Maps to plan_district."
        },
        "searchTypeId": {
          "type": "integer",
          "description": "Maps to search_type_id."
        },
        "milestoneStatus": {
          "enum": [
            "Review Complete",
            "Under Review"
          ],
          "type": "string",
          "description": "Maps to milestone_status."
        },
        "historicDistrict": {
          "type": "string",
          "description": "Maps to historic_district."
        },
        "applicationNumber": {
          "type": "string",
          "description": "Maps to application_number."
        },
        "businessAssociation": {
          "type": "string",
          "description": "Maps to business_association."
        },
        "conservationDistrict": {
          "type": "string",
          "description": "Maps to conservation_district."
        },
        "neighborhoodDistrict": {
          "type": "string",
          "description": "Maps to neighborhood_district."
        }
      },
      "additionalProperties": false
    }
    arguments 103 lines
  • query_intersects reads unknown 2h ago

    1:1 wrapper for /api/intersects/. Spatial intersection against named city layers such as row, taxlot, describe, street, and waterbody.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "geometry"
      ],
      "properties": {
        "buffer": {
          "type": "number",
          "default": 10
        },
        "detail": {
          "type": "boolean",
          "default": false
        },
        "include": {
          "type": "array",
          "items": {
            "enum": [
              "all",
              "city",
              "county",
              "describe",
              "park",
              "row",
              "stream",
              "street",
              "taxlot",
              "trail",
              "waterbody",
              "zipcode"
            ],
            "type": "string"
          },
          "default": [
            "describe"
          ]
        },
        "geometry": {
          "type": "object",
          "description": "ESRI JSON geometry in wkid 2913, 3857, or 4326.",
          "additionalProperties": {}
        }
      },
      "additionalProperties": false
    }
    arguments 46 lines
  • convert_geometry reads unknown 9h ago

    1:1 wrapper for /api/geometry/. Convert geometry between ESRI, WKT, GeoJSON, GPolyline, and EncodedGPolyline.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "from",
        "to",
        "geometry"
      ],
      "properties": {
        "to": {
          "enum": [
            "ESRI",
            "WKT",
            "GeoJSON",
            "GPolyline",
            "EncodedGPolyline"
          ],
          "type": "string"
        },
        "from": {
          "enum": [
            "ESRI",
            "WKT",
            "GeoJSON",
            "GPolyline",
            "EncodedGPolyline"
          ],
          "type": "string"
        },
        "srid": {
          "enum": [
            "2913",
            "3857",
            "4326"
          ],
          "type": "string"
        },
        "geometry": {
          "type": "string",
          "description": "Source geometry as a string. JSON inputs should be JSON.stringify'd."
        }
      },
      "additionalProperties": false
    }
    arguments 44 lines
  • get_portlandmaps_detail reads unknown 9h ago

    1:1 wrapper for /api/detail/. Fetch a detail record by detail_type, detail_id, and sections. ANSWER GUIDANCE: when this data answers a resident's zoning, permit, property, or city-code question, write for a Portland resident or small-business owner with no code, zoning, or permitting background. Lead with a 3–5 sentence plain-English summary (never open with a data table). Then cite EVERY rule, fee, number, timeline, or contact INLINE in the same sentence with both its exact code section AND a full https:// portland.gov URL (e.g. PCC 33.110.255.C, https://www.portland.gov/code/33/110/255) — never cite vaguely ("Title 33", "the BDS website") and never drop the URL. Define every acronym, add a numbered "what to do next" list, and if a number can't be cited to a specific section + URL, say so rather than stating it bare.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "detailType",
        "detailId"
      ],
      "properties": {
        "fileId": {
          "type": "string",
          "description": "Maps to file_id."
        },
        "detailId": {
          "type": "string",
          "minLength": 1,
          "description": "Maps to detail_id."
        },
        "fileType": {
          "type": "string",
          "description": "Maps to file_type."
        },
        "geometry": {
          "anyOf": [
            {
              "type": "object",
              "additionalProperties": {}
            },
            {
              "type": "string"
            }
          ]
        },
        "sections": {
          "type": "string",
          "default": "*",
          "description": "Use 'list' for available sections, or '*' for all sections."
        },
        "cacheClear": {
          "anyOf": [
            {
              "type": "boolean"
            },
            {
              "type": "number",
              "const": 0
            },
            {
              "type": "number",
              "const": 1
            }
          ],
          "description": "Maps to cache_clear."
        },
        "detailType": {
          "type": "string",
          "minLength": 1,
          "description": "Maps to detail_type."
        },
        "propertyId": {
          "type": "string",
          "description": "Maps to property_id."
        },
        "extraParams": {
          "type": "object",
          "additionalProperties": {}
        }
      },
      "additionalProperties": false
    }
    arguments 69 lines
  • render_parcel_shape reads unknown 15h ago

    Render a property's lot as an interactive UI component (inline SVG): a City of Portland aerial photo underlay (showing the true roofline) with the parcel outline, the building footprint(s) on the lot, approximate setback dimensions, a north arrow, and faint neighbouring parcels overlaid on top. Provide a detailType+detailId to fetch geometry, or pass rings directly. Aerial, footprints, and neighbours come from Portland's public ArcGIS layers; set basemap="none" to drop the photo and includeContext=false for just the bare outline. Renders in MCP Apps hosts (Claude) and legacy mcp-ui hosts.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "rings": {
          "type": "array",
          "items": {
            "type": "array",
            "items": {
              "type": "array",
              "items": {
                "type": "number"
              }
            }
          },
          "description": "Web Mercator (EPSG:3857) parcel rings, e.g. geometry.rings. Bypasses fetching."
        },
        "title": {
          "type": "string",
          "description": "Caption shown on the component."
        },
        "basemap": {
          "enum": [
            "aerial",
            "none"
          ],
          "type": "string",
          "default": "aerial",
          "description": "Aerial photo underlay (true rooflines). 'aerial' fetches a City of Portland image; 'none' renders dark vectors only."
        },
        "detailId": {
          "type": "string",
          "description": "detail_id used to fetch geometry when rings are not supplied."
        },
        "detailType": {
          "type": "string",
          "default": "zoning",
          "description": "detail_type used to fetch geometry when rings are not supplied."
        },
        "includeContext": {
          "type": "boolean",
          "default": true,
          "description": "Overlay building footprints, setbacks, and neighbouring parcels. Set false for just the lot outline."
        }
      },
      "additionalProperties": false
    }
    arguments 47 lines
  • search_sewer_records reads unknown 15h ago

    1:1 wrapper for /api/sewer/. Search sewer assets, as-builts, and easements.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "type"
      ],
      "properties": {
        "book": {
          "type": "string"
        },
        "date": {
          "type": "string"
        },
        "page": {
          "type": "string",
          "description": "Sewer easement page field."
        },
        "type": {
          "enum": [
            "Asset",
            "AsBuilt",
            "Easement"
          ],
          "type": "string"
        },
        "count": {
          "type": "integer",
          "default": 100,
          "maximum": 1000,
          "exclusiveMinimum": 0
        },
        "unitId": {
          "type": "string",
          "description": "Maps to unit_id."
        },
        "compkey": {
          "type": "string"
        },
        "jobName": {
          "type": "string",
          "description": "Maps to job_name."
        },
        "pageNum": {
          "type": "integer",
          "default": 1,
          "description": "Pagination page; maps to page.",
          "exclusiveMinimum": 0
        },
        "comments": {
          "type": "string"
        },
        "download": {
          "anyOf": [
            {
              "type": "boolean"
            },
            {
              "type": "number",
              "const": 0
            },
            {
              "type": "number",
              "const": 1
            }
          ]
        },
        "location": {
          "type": "string"
        },
        "jobNumber": {
          "type": "string",
          "description": "Maps to job_number."
        },
        "quitClaim": {
          "enum": [
            "Yes",
            "No"
          ],
          "type": "string",
          "description": "Maps to quit_claim."
        },
        "sortField": {
          "type": "string",
          "description": "Maps to sort_field."
        },
        "sortOrder": {
          "enum": [
            "asc",
            "desc"
          ],
          "type": "string",
          "description": "Maps to sort_order."
        },
        "rightOfWay": {
          "type": "string",
          "description": "Maps to right_of_way."
        },
        "extraParams": {
          "type": "object",
          "additionalProperties": {}
        },
        "quarterSection": {
          "type": "string",
          "description": "Maps to quarter_section."
        },
        "trackingNumber": {
          "type": "string",
          "description": "Maps to tracking_number."
        },
        "ordinanceNumber": {
          "type": "string",
          "description": "Maps to ordinance_number."
        },
        "workOrderNumber": {
          "type": "string",
          "description": "Maps to work_order_number."
        },
        "tvInspectionNumber": {
          "type": "string",
          "description": "Maps to tv_inspection_number."
        },
        "serviceRequestNumber": {
          "type": "string",
          "description": "Maps to service_request_number."
        }
      },
      "additionalProperties": false
    }
    arguments 128 lines
  • suggest_portlandmaps_address reads unknown never probed

    1:1 wrapper for /api/suggest/. Search PortlandMaps autocomplete for addresses, intersections, landmarks, or IDs. ANSWER GUIDANCE: when this data answers a resident's zoning, permit, property, or city-code question, write for a Portland resident or small-business owner with no code, zoning, or permitting background. Lead with a 3–5 sentence plain-English summary (never open with a data table). Then cite EVERY rule, fee, number, timeline, or contact INLINE in the same sentence with both its exact code section AND a full https:// portland.gov URL (e.g. PCC 33.110.255.C, https://www.portland.gov/code/33/110/255) — never cite vaguely ("Title 33", "the BDS website") and never drop the URL. Define every acronym, add a numbered "what to do next" list, and if a number can't be cited to a specific section + URL, say so rather than stating it bare.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "ags": {
          "$ref": "#/properties/units"
        },
        "city": {
          "type": "string"
        },
        "page": {
          "type": "integer",
          "exclusiveMinimum": 0
        },
        "unit": {
          "type": "string"
        },
        "cache": {
          "$ref": "#/properties/units"
        },
        "count": {
          "type": "integer",
          "maximum": 1000,
          "exclusiveMinimum": 0
        },
        "exact": {
          "$ref": "#/properties/units"
        },
        "query": {
          "type": "string",
          "minLength": 1,
          "description": "Search term. Can be an address, intersection, landmark name, or ID."
        },
        "units": {
          "anyOf": [
            {
              "type": "boolean"
            },
            {
              "type": "number",
              "const": 0
            },
            {
              "type": "number",
              "const": 1
            }
          ]
        },
        "altIds": {
          "$ref": "#/properties/units",
          "description": "Maps to alt_ids."
        },
        "county": {
          "type": "string"
        },
        "status": {
          "enum": [
            "active",
            "pending",
            "all"
          ],
          "type": "string"
        },
        "elements": {
          "$ref": "#/properties/units"
        },
        "geometry": {
          "anyOf": [
            {
              "type": "object",
              "additionalProperties": {}
            },
            {
              "type": "string"
            }
          ]
        },
        "altCoords": {
          "$ref": "#/properties/units",
          "description": "Maps to alt_coords."
        },
        "idMatches": {
          "$ref": "#/properties/units",
          "description": "Maps to id_matches."
        },
        "landmarks": {
          "$ref": "#/properties/units"
        },
        "centerline": {
          "$ref": "#/properties/units"
        },
        "extraParams": {
          "type": "object",
          "additionalProperties": {}
        },
        "jurisdiction": {
          "type": "string"
        },
        "intersections": {
          "$ref": "#/properties/units"
        }
      },
      "additionalProperties": false
    }
    arguments 107 lines
  • lookup_agol reads unknown 9h ago

    1:1 wrapper for /api/agol/. Retrieve City of Portland ArcGIS Online metadata, webmaps, locators, and portal info.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "type"
      ],
      "properties": {
        "id": {
          "type": "string"
        },
        "type": {
          "enum": [
            "Locators",
            "Portal",
            "PortalGroup",
            "PortalGroupItems",
            "PortalThemes",
            "Webmap",
            "WebmapData",
            "WebmapItem",
            "WebmapExtra"
          ],
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 27 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 ef3754936e18a558.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ef3754936e18a558/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/ef3754936e18a558/badge.svg)](https://brick.blue/agent/ef3754936e18a558?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
100%

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.