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

travelmcp-directory

https://omnitravel.ai

Registry code: 85fa74103838c62a

api record

Directory of MCP servers, agent skills and APIs for the travel industry, published by OmniTravel. Use search_travel_tools to find tools by topic (hotel ID mapping, room type mapping, rates, scraping, browser automation), get_tool_details for the full record including setup documentation, and list_categories to see how the directory is organised.

endpoint
https://omnitravel.ai/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 travelmcp-directory live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is travelmcp-directory free to use?
Yes — the hub reached it with no key and no payment.
What tools does travelmcp-directory have?
3 tools: get_tool_details, search_travel_tools, list_categories.
Is travelmcp-directory 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.2%· all time 99.2%

latency
88ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 379 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
developer tools apis & integration
used for
  • find travel industry mcp servers and apis
  • get a tool listing with setup docs
  • list directory categories
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

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

  • search_travel_tools reads open 19h ago

    Search the OmniTravel directory of MCP servers, agent skills and APIs for travel technology. Returns matching tools with their tagline, category, author and URL. Typo-tolerant full-text search.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "type": {
      "enum": [
        "mcp_server",
        "agent_skill",
        "client",
        "api"
      ],
      "type": "string",
      "description": "Restrict to one kind of listing"
    },
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "Maximum results, default 10"
    },
    "query": {
      "type": "string",
      "description": "Search phrase, for example \"hotel id mapping\" or \"browser automation\""
    },
    "category": {
      "type": "string",
      "description": "Category slug filter, for example \"hotel-id-mapping\" or \"web-scraping\""
    }
  }
}
    arguments 30 lines
  • list_categories reads open 19h ago

    List every category in the directory with its slug and how many listings it holds. Travel-specific categories such as hotel ID mapping and room type mapping are marked as pinned.

    mcp-tool

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

    Fetch one directory listing by slug, including its full description, install snippet and setup documentation. Use the slug returned by search_travel_tools.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Listing slug, for example \"room-matching-api\""
    }
  }
}
    arguments 13 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 85fa74103838c62a.

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