_ registry / mcp streamable-http · checked 37m ago

gangway-ais

https://gangwayais.com

Registry code: e09c4c95eec7372e

api record

Gangway AIS answers about vessels and ports from licensed AIS sources: where a vessel is now and where she has been, vessels in an area or near a point, a port's picture (expected, in port, at anchor), arrivals and departures, port calls, waiting times at anchor, congestion, events, sanctions checks, depth and passage routes. Use search_vessels to turn a vessel's name into an MMSI, and give ports by UN/LOCODE or name. Every tool needs a Gangway AIS key: a free account's key answers search_vessels, get_vessel, vessels_in_area, vessels_near, search_ports, resolve_destination, port_now,…

endpoint
https://gangwayais.com/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 gangway-ais live?
Yes — it answered the hub's last check (checked 37m ago). It answered 100% of checks over the last 30 days.
Is gangway-ais free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does gangway-ais have?
21 tools: account_usage, get_vessel, search_vessels, vessels_in_area, vessels_near, vessel_track, data_sources, resolve_destination, ….
Is gangway-ais 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 100%· all time 100%

latency
190ms

last good check

priced tools
0

of 21 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 21 tools
21 auth-required 21 of 21 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.

  • account_usage auth-required 37m ago

    Your key's plan, the credits used and left this month, when they renew, and the plan's rate, largest box, reach back and delay. Free. Free accounts too: their answers are 24 hours behind, with a box of at most 1 square degree and 1,000 credits a month; paid plans are live.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • get_vessel auth-required 37m ago

    One vessel now: her last position, speed, course, heading and navigational status from a source we may pass on, with her particulars (name, IMO, call sign, type, size, flag) and voyage (destination, ETA, draught). Give her MMSI, or her IMO number (then she is found by search first, 1 credit more). Credits: 1. Free accounts too: their answers are 24 hours behind, with a box of at most 1 square degree and 1,000 credits a month; paid plans are live.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "imo": {
      "type": "integer",
      "maximum": 9999999,
      "minimum": 1000000,
      "description": "The vessel's IMO number, seven digits"
    },
    "mmsi": {
      "type": "integer",
      "maximum": 999999999,
      "minimum": 1,
      "description": "The vessel's MMSI, nine digits"
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • search_vessels auth-required never probed

    Find vessels by name, MMSI or IMO number (a prefix of at least 2 characters works), among the vessels our sources have heard. Each comes with her particulars and her last position from a source we may pass on. Use it to turn a name into an MMSI for the other tools. Credits: 1 per vessel returned. Free accounts too: their answers are 24 hours behind, with a box of at most 1 square degree and 1,000 credits a month; paid plans are live.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "At most this many vessels (default 10)"
    },
    "query": {
      "type": "string",
      "maxLength": 60,
      "minLength": 2,
      "description": "Name, MMSI or IMO, or the start of one"
    },
    "near_lat": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Optional: rank vessels near this latitude first"
    },
    "near_lon": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Optional: rank vessels near this longitude first"
    }
  },
  "additionalProperties": false
}
    arguments 33 lines
  • vessels_in_area auth-required never probed

    Vessels inside a latitude/longitude box, newest report first, each at her last position from a source we may pass on. truncated says that more were left out. Largest box: 1 square degree on a free account, 4 on Plus, 25 on Pro, 100 on Scale. Credits: 1 per vessel returned. Free accounts too: their answers are 24 hours behind, with a box of at most 1 square degree and 1,000 credits a month; paid plans are live.

    mcp-tool

    {
  "type": "object",
  "required": [
    "min_lat",
    "min_lon",
    "max_lat",
    "max_lon"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 500,
      "minimum": 1,
      "description": "At most this many vessels (default 50)"
    },
    "max_age": {
      "type": "string",
      "pattern": "^[0-9]{1,4}[mhd]$",
      "description": "Only vessels heard within this time, such as 90m, 24h or 7d (default 24h)"
    },
    "max_lat": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "North edge of the box"
    },
    "max_lon": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "East edge of the box"
    },
    "min_lat": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "South edge of the box"
    },
    "min_lon": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "West edge of the box"
    },
    "ship_type": {
      "type": "integer",
      "maximum": 99,
      "minimum": 0,
      "description": "AIS ship type: a code ending in 0 means its whole group (70 all cargo, 80 all tankers)"
    },
    "min_speed_kn": {
      "type": "number",
      "maximum": 102,
      "minimum": 0,
      "description": "Only vessels at or above this speed over ground, in knots"
    }
  },
  "additionalProperties": false
}
    arguments 59 lines
  • vessels_near auth-required never probed

    Vessels within a radius of a position or of another vessel, nearest first, each with her distance in nautical miles and true bearing from the centre. It asks for the square around the circle, which must fit your plan's largest box (1 square degree on a free account, 4 on Plus, 25 on Pro, 100 on Scale). Credits: 1 for every vessel in that square (at most 200), and 1 more to centre on a vessel. Free accounts too: their answers are 24 hours behind, with a box of at most 1 square degree and 1,000 credits a month; paid plans are live.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "lat": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Latitude in decimal degrees, north positive"
    },
    "lon": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Longitude in decimal degrees, east positive"
    },
    "mmsi": {
      "type": "integer",
      "maximum": 999999999,
      "minimum": 1,
      "description": "Or centre on this vessel's last position"
    },
    "limit": {
      "type": "integer",
      "maximum": 200,
      "minimum": 1,
      "description": "At most this many vessels (default 25)"
    },
    "max_age": {
      "type": "string",
      "pattern": "^[0-9]{1,4}[mhd]$",
      "description": "Only vessels heard within this time, such as 90m or 24h (default 24h)"
    },
    "radius_nm": {
      "type": "number",
      "maximum": 30,
      "minimum": 0.5,
      "description": "Radius in nautical miles (default 10, at most 30)"
    }
  },
  "additionalProperties": false
}
    arguments 42 lines
  • vessel_track auth-required never probed

    One vessel's recorded positions, oldest first, from the sources we may pass on: give hours back from now (default 72) or a from/to window. Long tracks are thinned evenly to max_points for reading; the credits count the whole range. Reach back: 90 days on Plus, 365 on Pro and Scale. Credits: 1 per vessel-day with positions. Needs a paid plan: Data API Plus, Pro or Scale, or a paid Watch plan (https://gangwayais.com/#pricing).

    mcp-tool

    {
  "type": "object",
  "required": [
    "mmsi"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "End, ISO 8601 UTC (default now)"
    },
    "from": {
      "type": "string",
      "description": "Start, ISO 8601 UTC such as 2026-11-01T00:00:00Z"
    },
    "mmsi": {
      "type": "integer",
      "maximum": 999999999,
      "minimum": 1,
      "description": "The vessel's MMSI, nine digits"
    },
    "hours": {
      "type": "integer",
      "maximum": 8760,
      "minimum": 1,
      "description": "Hours back from now"
    },
    "max_points": {
      "type": "integer",
      "maximum": 2000,
      "minimum": 2,
      "description": "Hand back at most this many points (default 300)"
    }
  },
  "additionalProperties": false
}
    arguments 35 lines
  • data_sources auth-required 37m ago

    The sources behind the answers, each with its licence, the credit to show and what it covers, and how far back our recorded history goes. Free. Free accounts too: their answers are 24 hours behind, with a box of at most 1 square degree and 1,000 credits a month; paid plans are live.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • resolve_destination auth-required never probed

    The port an AIS destination text names (such as "NL RTM" or "ROTTERDAM PILOT"), or null. Free. Free accounts too: their answers are 24 hours behind, with a box of at most 1 square degree and 1,000 credits a month; paid plans are live.

    mcp-tool

    {
  "type": "object",
  "required": [
    "destination"
  ],
  "properties": {
    "destination": {
      "type": "string",
      "maxLength": 120,
      "minLength": 1,
      "description": "The destination as the vessel broadcasts it"
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • port_calls_on_date auth-required never probed

    The seagoing vessels alongside in a port on one UTC day (default today), with when each made fast and left. Reach back: 90 days on Plus, 365 on Pro and Scale. Credits: 1 per call. Needs a paid plan: Data API Plus, Pro or Scale, or a paid Watch plan (https://gangwayais.com/#pricing).

    mcp-tool

    {
  "type": "object",
  "required": [
    "port"
  ],
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^[0-9]{4}-[0-9]{2}-[0-9]{2}$",
      "description": "The day, YYYY-MM-DD (UTC)"
    },
    "port": {
      "type": "string",
      "maxLength": 80,
      "minLength": 2,
      "description": "A port by UN/LOCODE (such as NLRTM) or by name (such as Rotterdam)"
    }
  },
  "additionalProperties": false
}
    arguments 20 lines
  • vessel_port_calls auth-required never probed

    Where a vessel called, from when to when, the gaps when no receiver heard her and the events along the way, for the last days asked (default 7), from all the AIS we hear (the ports and times; a position only where we may pass it on). Reach back: 90 days on Plus, 365 on Pro and Scale. Credits: 1 per call. Needs a paid plan: Data API Plus, Pro or Scale, or a paid Watch plan (https://gangwayais.com/#pricing).

    mcp-tool

    {
  "type": "object",
  "required": [
    "mmsi"
  ],
  "properties": {
    "days": {
      "type": "integer",
      "maximum": 365,
      "minimum": 1,
      "description": "Days back from now (default 7)"
    },
    "mmsi": {
      "type": "integer",
      "maximum": 999999999,
      "minimum": 1,
      "description": "The vessel's MMSI, nine digits"
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
  • vessel_activity auth-required never probed

    A summary of how a vessel spent the last days (default 30): hours under way, in port, stopped off a port, stopped elsewhere and not heard, the distance sailed, her speeds, her calls and the ports she called at most. Reach back: 90 days on Plus, 365 on Pro and Scale. Credits: 5. Needs a paid plan: Data API Plus, Pro or Scale, or a paid Watch plan (https://gangwayais.com/#pricing).

    mcp-tool

    {
  "type": "object",
  "required": [
    "mmsi"
  ],
  "properties": {
    "days": {
      "type": "integer",
      "maximum": 365,
      "minimum": 1,
      "description": "Days back from now (default 30)"
    },
    "mmsi": {
      "type": "integer",
      "maximum": 999999999,
      "minimum": 1,
      "description": "The vessel's MMSI, nine digits"
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
  • sanctions_check auth-required never probed

    Whether a vessel's IMO number is on the public sanctions lists we read (the US OFAC SDN list, the UK Sanctions List, the EU vessel lists and Australia's sanctioned vessels), with what each list says of her. Matched by IMO number only: information, not a compliance determination. Credits: 1. Needs a paid plan: Data API Plus, Pro or Scale, or a paid Watch plan (https://gangwayais.com/#pricing).

    mcp-tool

    {
  "type": "object",
  "required": [
    "imo"
  ],
  "properties": {
    "imo": {
      "type": "integer",
      "maximum": 9999999,
      "minimum": 1000000,
      "description": "The vessel's IMO number, seven digits with a valid check digit"
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • search_ports auth-required never probed

    Ports by name, UN/LOCODE or English name, ranked for a seafarer; or the ports nearest a position. Free. Free accounts too: their answers are 24 hours behind, with a box of at most 1 square degree and 1,000 credits a month; paid plans are live.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 12,
      "minimum": 1,
      "description": "At most this many ports (default 8)"
    },
    "query": {
      "type": "string",
      "maxLength": 80,
      "minLength": 2,
      "description": "A port name or UN/LOCODE"
    },
    "near_lat": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Or: the ports nearest this latitude"
    },
    "near_lon": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Or: the ports nearest this longitude"
    }
  },
  "additionalProperties": false
}
    arguments 31 lines
  • port_now auth-required never probed

    A port's picture now: vessels in port and at anchor, vessels expected (arriving) and the latest port events. Give a UN/LOCODE or a name. Credits: 5, nothing when the port is empty. Free accounts too: their answers are 24 hours behind, with a box of at most 1 square degree and 1,000 credits a month; paid plans are live.

    mcp-tool

    {
  "type": "object",
  "required": [
    "port"
  ],
  "properties": {
    "port": {
      "type": "string",
      "maxLength": 80,
      "minLength": 2,
      "description": "A port by UN/LOCODE (such as NLRTM) or by name (such as Rotterdam)"
    },
    "limit": {
      "type": "integer",
      "maximum": 400,
      "minimum": 1,
      "description": "At most this many vessels in each list (default 40)"
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
  • port_vessels auth-required never probed

    A port's list of vessels: expected (bound for it), in port now, arrived or departed over the last 7 days. Filter by kind, flag and length. Credits: 1 per vessel returned. Needs a paid plan: Data API Plus, Pro or Scale, or a paid Watch plan (https://gangwayais.com/#pricing).

    mcp-tool

    {
  "type": "object",
  "required": [
    "port"
  ],
  "properties": {
    "flag": {
      "type": "string",
      "pattern": "^[A-Za-z]{2}$",
      "description": "Only this flag, a two-letter ISO country code"
    },
    "kind": {
      "enum": [
        "passenger",
        "cargo",
        "tanker",
        "hsc",
        "fishing",
        "service",
        "pleasure",
        "other"
      ],
      "type": "string",
      "description": "Only this kind of vessel"
    },
    "list": {
      "enum": [
        "expected",
        "inport",
        "arrived",
        "departed"
      ],
      "type": "string",
      "description": "Which list (default expected)"
    },
    "port": {
      "type": "string",
      "maxLength": 80,
      "minLength": 2,
      "description": "A port by UN/LOCODE (such as NLRTM) or by name (such as Rotterdam)"
    },
    "limit": {
      "type": "integer",
      "maximum": 300,
      "minimum": 1,
      "description": "At most this many vessels (default 50)"
    },
    "max_length_m": {
      "type": "number",
      "maximum": 500,
      "minimum": 0,
      "description": "Only vessels at most this long, in metres"
    },
    "min_length_m": {
      "type": "number",
      "maximum": 500,
      "minimum": 0,
      "description": "Only vessels at least this long, in metres"
    }
  },
  "additionalProperties": false
}
    arguments 62 lines
  • port_waiting_times auth-required never probed

    Waiting times at anchor off a port: the median this week against what is normal there, and optionally the vessels waiting now. Credits: 5, nothing when we hold no figures for it. Needs a paid plan: Data API Plus, Pro or Scale, or a paid Watch plan (https://gangwayais.com/#pricing).

    mcp-tool

    {
  "type": "object",
  "required": [
    "port"
  ],
  "properties": {
    "port": {
      "type": "string",
      "maxLength": 80,
      "minLength": 2,
      "description": "A port by UN/LOCODE (such as NLRTM) or by name (such as Rotterdam)"
    },
    "include_vessels": {
      "type": "boolean",
      "description": "Also list the vessels at anchor now (default false)"
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • port_congestion auth-required never probed

    How busy a port is against its own normal: an index, vessels waiting now, the median wait and the arrivals and departures day by day over the last days (default 30). Credits: 5, nothing when we hold no figures for it. Needs a paid plan: Data API Plus, Pro or Scale, or a paid Watch plan (https://gangwayais.com/#pricing).

    mcp-tool

    {
  "type": "object",
  "required": [
    "port"
  ],
  "properties": {
    "days": {
      "type": "integer",
      "maximum": 90,
      "minimum": 1,
      "description": "Days back from now (default 30)"
    },
    "port": {
      "type": "string",
      "maxLength": 80,
      "minLength": 2,
      "description": "A port by UN/LOCODE (such as NLRTM) or by name (such as Rotterdam)"
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
  • port_events auth-required never probed

    Recent events from AIS: arrivals, departures, anchoring, weighing anchor and approaches by default; also pilot, tug, bunkering, waiting, renamed and more. Optionally inside a box (at most 400 square degrees). Since defaults to the last 24 hours, at most 30 days back. Credits: 1 per event. Needs a paid plan: Data API Plus, Pro or Scale, or a paid Watch plan (https://gangwayais.com/#pricing).

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "kinds": {
      "type": "string",
      "description": "Comma-separated kinds, or \"all\". Kinds: aisoff, anchored, approaching, arrived, bunkering, delayrisk, destination, dragging, draught, drifting, eta, heard, left, pilot, quiet, renamed, slow, strait, sts, tug, underway, waiting, weighed"
    },
    "limit": {
      "type": "integer",
      "maximum": 200,
      "minimum": 1,
      "description": "At most this many events (default 60)"
    },
    "since": {
      "type": "string",
      "description": "ISO 8601 UTC time to start from"
    },
    "max_lat": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "North edge of the box"
    },
    "max_lon": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "East edge of the box"
    },
    "min_lat": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "South edge of the box"
    },
    "min_lon": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "West edge of the box"
    }
  },
  "additionalProperties": false
}
    arguments 45 lines
  • plan_route auth-required never probed

    A sea route between two positions, through the traffic separation schemes, with its distance and legs. Give the vessel's length and draught to keep her in water deep enough. A planning aid from charts and data that can be wrong: never for navigation. At most 6 a minute. Credits: 10. Needs a paid plan: Data API Plus, Pro or Scale, or a paid Watch plan (https://gangwayais.com/#pricing).

    mcp-tool

    {
  "type": "object",
  "required": [
    "from_lat",
    "from_lon",
    "to_lat",
    "to_lon"
  ],
  "properties": {
    "to_lat": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Latitude in decimal degrees, north positive"
    },
    "to_lon": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Longitude in decimal degrees, east positive"
    },
    "from_lat": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Latitude in decimal degrees, north positive"
    },
    "from_lon": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Longitude in decimal degrees, east positive"
    },
    "length_m": {
      "type": "number",
      "maximum": 500,
      "minimum": 1,
      "description": "Her length overall in metres"
    },
    "draught_m": {
      "type": "number",
      "maximum": 30,
      "minimum": 0.1,
      "description": "Her draught in metres"
    }
  },
  "additionalProperties": false
}
    arguments 48 lines
  • check_route auth-required never probed

    Check a planned route leg by leg against land, depth (her draught plus the under-keel clearance), sea room and the traffic separation schemes, with plain-language warnings for what it finds. A planning aid: it finds what our charts and data show, never everything; not for navigation. At most 30 a minute. Credits: 10. Needs a paid plan: Data API Plus, Pro or Scale, or a paid Watch plan (https://gangwayais.com/#pricing).

    mcp-tool

    {
  "type": "object",
  "required": [
    "waypoints"
  ],
  "properties": {
    "ukc_m": {
      "type": "number",
      "maximum": 10,
      "minimum": 0,
      "description": "Under-keel clearance to keep, in metres"
    },
    "beam_m": {
      "type": "number",
      "maximum": 80,
      "minimum": 1,
      "description": "Her beam in metres"
    },
    "length_m": {
      "type": "number",
      "maximum": 500,
      "minimum": 1,
      "description": "Her length overall in metres"
    },
    "draught_m": {
      "type": "number",
      "maximum": 30,
      "minimum": 0.1,
      "description": "Her draught in metres"
    },
    "waypoints": {
      "type": "array",
      "items": {
        "type": "array",
        "items": {
          "type": "number"
        },
        "maxItems": 2,
        "minItems": 2
      },
      "maxItems": 200,
      "minItems": 2,
      "description": "The route's turning points in order, each [lat, lon]"
    },
    "sea_room_nm": {
      "type": "number",
      "maximum": 20,
      "minimum": 0,
      "description": "Sea room to keep off danger, in nautical miles"
    },
    "air_draught_m": {
      "type": "number",
      "maximum": 100,
      "minimum": 1,
      "description": "Her air draught in metres"
    }
  },
  "additionalProperties": false
}
    arguments 59 lines
  • depth_at auth-required never probed

    The charted water depth at a position from EMODnet Bathymetry (European waters), or none where it has no figure. Not for navigation. Credits: 1, nothing where there is no depth. Needs a paid plan: Data API Plus, Pro or Scale, or a paid Watch plan (https://gangwayais.com/#pricing).

    mcp-tool

    {
  "type": "object",
  "required": [
    "lat",
    "lon"
  ],
  "properties": {
    "lat": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Latitude in decimal degrees, north positive"
    },
    "lon": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Longitude in decimal degrees, east positive"
    }
  },
  "additionalProperties": false
}
    arguments 22 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 e09c4c95eec7372e.

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