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

canienter

https://api.canienter.com

Registry code: d60d87f6504ae416

api record

Stateless visa/entry-requirements lookups. check_entry_requirements is rate limited on the free tier; for unlimited access pay per request via x402 on the HTTP API (see the llms.txt of this host). Advisory information for trip planning — not a boarding, immigration, or legal decision. Rules change frequently; verify with the destination country's official sources before travel.

endpoint
https://api.canienter.com/mcp
door code
afa64fe4c66aa64d
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 canienter live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is canienter free to use?
Yes — the hub reached it with no key and no payment.
What tools does canienter have?
3 tools: check_entry_requirements, get_dataset_info, evaluate_trip.
Is canienter 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
99.5%

90 days 98.8%· all time 98.7%

latency
364ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 847 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
maps travel & places travel & transport
used for
  • check visa requirements for a passport and destination
  • evaluate entry rules for a multi-leg trip
takes → gives
text → data
tools
3 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

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

  • check_entry_requirements reads unknown 13h ago

    Whether a passport holder can enter a destination country: visa-free, visa on arrival, e-visa, eTA, or visa required — with allowed stay, official application portal, extended rules (passport validity, onward ticket, yellow fever, transit-without-visa) and source citations. Free tier: rate limited per caller (see /auth.md to register for a larger quota, or use the x402-paid HTTP API for unlimited access).

    mcp-tool

    {
  "type": "object",
  "required": [
    "passport",
    "destination"
  ],
  "properties": {
    "purpose": {
      "type": "string",
      "description": "Travel purpose (default: tourism)"
    },
    "transit": {
      "type": "string",
      "description": "Optional transit country, ISO 3166-1 alpha-3"
    },
    "passport": {
      "type": "string",
      "description": "Passport country, ISO 3166-1 alpha-3 (e.g. NLD)"
    },
    "visas_of": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Issuers of visas held (ISO3 or SCHENGEN/EU/GCC)"
    },
    "destination": {
      "type": "string",
      "description": "Destination country, ISO 3166-1 alpha-3 (e.g. JPN)"
    },
    "residence_permits_of": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Issuers of residence permits held (ISO3 or SCHENGEN/EU/GCC)"
    }
  }
}
    arguments 39 lines
  • get_dataset_info reads unknown never probed

    Coverage and freshness of the underlying visa-requirements dataset, plus endpoints and x402 pricing for the unlimited paid tier.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • evaluate_trip reads unknown 13h ago

    Premium evaluation of a whole trip in one call: multiple passports (best passport per leg), documents held, multi-leg itineraries with transit legs, dates and purpose — with structured why[] explanations, conditions[], and verification states per decision. PAID endpoint: the call returns HTTP 402 x402 payment instructions unless the request carries an x402 payment header; any x402-capable client settles in USDC on Base and retries.

    mcp-tool

    {
  "type": "object",
  "required": [
    "traveler",
    "trip"
  ],
  "properties": {
    "trip": {
      "type": "object",
      "required": [
        "legs"
      ],
      "properties": {
        "legs": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "country"
            ],
            "properties": {
              "role": {
                "enum": [
                  "entry",
                  "transit"
                ],
                "type": "string",
                "description": "entry = enter the country; transit = pass through in transit"
              },
              "country": {
                "type": "string",
                "description": "Leg country, ISO 3166-1 alpha-3"
              },
              "purpose": {
                "type": "string",
                "description": "Overrides the trip purpose for this leg"
              },
              "arrival_date": {
                "type": "string",
                "description": "YYYY-MM-DD; enables stay-duration and validity-window checks"
              },
              "departure_date": {
                "type": "string",
                "description": "YYYY-MM-DD; enables stay-duration and validity-window checks"
              }
            }
          },
          "description": "Trip legs in order, up to 10"
        },
        "purpose": {
          "type": "string",
          "description": "Trip-wide travel purpose (default: tourism); per-leg purpose overrides"
        }
      },
      "description": "The itinerary to evaluate, in travel order"
    },
    "traveler": {
      "type": "object",
      "required": [
        "passports"
      ],
      "properties": {
        "visas_of": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Issuers of valid visas held (ISO3 or SCHENGEN/EU/GCC)"
        },
        "passports": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "ISO3, 1-4 passports"
        },
        "residence_permits_of": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Issuers of residence permits held (ISO3 or SCHENGEN/EU/GCC)"
        }
      },
      "description": "The traveler's documents"
    }
  }
}
    arguments 88 lines
_ try it over mcp 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 d60d87f6504ae416.

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