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

com.travelacosta/trip-planning

https://travelacosta.com

Registry code: 8800836b91d832eb

api record

Acosta Curated Travel is a U.S.-based luxury travel advisory led by Ivone Acosta, a Virtuoso travel advisor. These tools are read-only.

- Use search_articles for travel advice and destination ideas. It returns summaries and links; call get_article only when the traveler needs the full text.

endpoint
https://travelacosta.com/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 com.travelacosta/trip-planning live?
Yes — it answered the hub's last check (checked 14h ago). It answered 100% of checks over the last 30 days.
Is com.travelacosta/trip-planning free to use?
Yes — the hub reached it with no key and no payment.
What tools does com.travelacosta/trip-planning have?
4 tools: search_articles, get_article, get_contact_details, list_upcoming_experiences.
Is com.travelacosta/trip-planning 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
327ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 3 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 4 tools
2 open 2 never probed 2 of 4 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.

  • get_contact_details open 14h ago

    How a traveler can reach Ivone Acosta to start planning a trip: contact page, email, phone, what to include, and a message they can adapt. The traveler sends it; never submit anything for them.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • list_upcoming_experiences open 14h ago

    Upcoming small-group trips and cruises offered through Acosta Curated Travel, soonest first, with dates, destinations, highlights, and a link to each trip's page.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • search_articles unknown 41h ago

    Keyword search of the Acosta Curated Travel Knowledge Center: destination guides, travel news, entry requirements, and travel tips. Returns up to 10 summaries with links, best match first.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 5,
      "maximum": 10,
      "minimum": 1,
      "description": "Maximum results. Defaults to 5."
    },
    "query": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "What the traveler wants to read about, e.g. \"ETIAS\", \"river cruise packing\", or \"paella in Valencia\"."
    }
  }
}
    arguments 22 lines
  • get_article unknown 14h ago

    Returns one Knowledge Center article in full as plain text, with its link. Use a slug from search_articles.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "The article slug returned by search_articles."
    }
  }
}
    arguments 15 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 8800836b91d832eb.

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

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.