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

io.github.capitalthought/customs-dog-mcp

listed under this name in a public catalogue; the server gives only its address, customs.dog

https://customs.dog

Registry code: b62880fa42af2ed4

api record

Pet travel documents + border trip-readiness (cleared/caution/blocked) for AI assistants.

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

endpoint
https://customs.dog/mcp
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 io.github.capitalthought/customs-dog-mcp live?
No — it has stopped answering the hub's checks (checked 58m ago). It answered 77% of checks over the last 30 days.
Is io.github.capitalthought/customs-dog-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does io.github.capitalthought/customs-dog-mcp have?
8 tools: customs_list_documents, customs_overview, customs_check_trip_readiness, customs_prep, customs_start_signup, customs_upcoming_trips, customs_check_rules, customs_list_pets.
Is io.github.capitalthought/customs-dog-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
down
uptime, 30 days
77.3%

90 days 85.5%· all time 85.5%

latency
132ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 325 checks · signed record
  • degraded → down· HTTP 500
  • live → degraded· HTTP 500
  • down → live
  • degraded → down· HTTP 500
  • live → degraded· HTTP 500
_ what it is for
used for
  • check pet border entry rules for a country
  • check a pet's trip readiness
  • list a pet's travel documents
  • sign up a new user
takes → gives
text, data → data
tools
7 reads1 sends messages
_ 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 8 tools
2 open 6 never probed 2 of 8 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.

  • customs_check_rules reads open 14d ago

    Per-destination pet border-entry requirements — NO account needed. What documents a dog needs to enter a country and re-enter the US. Use this to answer 'what does my pet need to travel to X?' for anyone. Omit `destination` to list every corridor.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "destination": {
          "enum": [
            "mexico",
            "canada",
            "bvi",
            "us_domestic"
          ],
          "type": "string"
        }
      }
    }
    arguments 15 lines
  • customs_list_pets reads open 14d ago

    List the household's pets (source of pet_id).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • customs_list_documents reads unknown 14d ago

    List documents for a pet.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "pet_id"
      ],
      "properties": {
        "pet_id": {
          "type": "string"
        },
        "status": {
          "enum": [
            "valid",
            "expiring",
            "expired",
            "none"
          ],
          "type": "string"
        },
        "category": {
          "enum": [
            "cdc_import_receipt",
            "health_cert",
            "rabies",
            "microchip",
            "permit",
            "medical",
            "service_esa",
            "airline",
            "photos"
          ],
          "type": "string"
        }
      }
    }
    arguments 35 lines
  • customs_overview reads unknown never probed

    Counts of pets/documents by status, what's expiring soon, recent household activity, and MCP usage stats (per-tool call counts, public-tier reach, verdict distribution).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • customs_check_trip_readiness reads unknown 14d ago

    Cleared / caution / blocked for pet + destination + return_date. NEVER assert clearance without this. (For rules without an account, use customs_check_rules.)

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "pet_id",
        "destination"
      ],
      "properties": {
        "pet_id": {
          "type": "string"
        },
        "destination": {
          "enum": [
            "mexico",
            "canada",
            "bvi",
            "us_domestic"
          ],
          "type": "string"
        },
        "return_date": {
          "type": "string"
        }
      }
    }
    arguments 25 lines
  • customs_prep reads unknown never probed

    Validate the session, confirm the pet roster, report health. Call first.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • customs_start_signup sends messages unknown never probed

    Start a FREE customs.dog account for a NEW user by email and send them a magic sign-in link (no password). Use this to onboard someone who wants to store and track their pet's travel documents after you've shown them their border requirements.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "email"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 80
        },
        "email": {
          "type": "string",
          "format": "email",
          "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
        }
      }
    }
    arguments 18 lines
  • customs_upcoming_trips reads unknown never probed

    Upcoming trips from the household's connected travel calendar (TripIt/Flighty/Google/Apple), each with per-pet readiness (cleared/caution/blocked). Use to proactively flag paperwork needed before travel.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 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 b62880fa42af2ed4.

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