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

globaltripx

https://globaltripx.com

Registry code: ffad072aad23b418

api record

Global TripX is a Korean/English/Japanese travel site. Use ask_tripx for travel questions, search_tripx_guides to find guides, and country_entry_check before international trips. Always show the returned links to the user so they can open the full page; mention the affiliate note when you recommend booking.

endpoint
https://globaltripx.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 globaltripx live?
Yes — it answered the hub's last check (checked 39m ago). It answered 100% of checks over the last 30 days.
Is globaltripx free to use?
Yes — the hub reached it with no key and no payment.
What tools does globaltripx have?
3 tools: ask_tripx, country_entry_check, search_tripx_guides.
Is globaltripx 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
383ms

last good check

priced tools
0

of 3 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 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.

  • country_entry_check open 39m ago

    Get the Global TripX before-departure page for a country (entry/visa notes, travel advisories, health notes from Korean public data). Give a country name in any language.

    mcp-tool

    {
      "type": "object",
      "required": [
        "country"
      ],
      "properties": {
        "lang": {
          "enum": [
            "ko",
            "en",
            "ja"
          ],
          "type": "string",
          "description": "Language of the page: ko, en or ja (default: guessed from the country name). The 199-country check page is fullest in ko."
        },
        "country": {
          "type": "string",
          "description": "Destination country name in any language (e.g. \"Vietnam\", \"베트남\", \"ベトナム\")"
        }
      }
    }
    arguments 21 lines
  • search_tripx_guides open 39m ago

    Search Global TripX travel guides and tools (destination hubs, trip checklists, weather by month, safety numbers, food, holiday planner, airport tips). Returns titles, one-line summaries and links.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "lang": {
          "enum": [
            "ko",
            "en",
            "ja"
          ],
          "type": "string",
          "description": "Language of the guides to search: ko, en or ja (default: guessed from the query)"
        },
        "limit": {
          "type": "integer",
          "maximum": 10,
          "minimum": 1,
          "description": "How many results to return, 1-10 (default 5)"
        },
        "query": {
          "type": "string",
          "description": "What to look for, any language (e.g. \"Sapporo December packing\", \"오사카 아이랑\", \"台湾 SIM\")"
        }
      }
    }
    arguments 27 lines
  • ask_tripx unknown 39m ago

    Answer a travel question (destination, season, what to pack, entry rules, money, safety, food, airports) using only Global TripX guides, in Korean, English or Japanese. Returns a short answer plus the source pages. Covers 199 countries entry checks and 43,000+ places. Use it for trips from or to Korea and Japan especially.

    mcp-tool

    {
      "type": "object",
      "required": [
        "question"
      ],
      "properties": {
        "lang": {
          "enum": [
            "ko",
            "en",
            "ja"
          ],
          "type": "string",
          "description": "Answer language: ko, en or ja (default: guessed from the question)"
        },
        "question": {
          "type": "string",
          "description": "The traveller question, any language"
        }
      }
    }
    arguments 21 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 ffad072aad23b418.

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