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

tripperoni

https://tripperoni.com

Registry code: c297b76bfcd7f98d

api record

Policy for AI assistants and agents:

- Querying, reading, quoting and citing Tripperoni's pages, REST API and MCP tools is welcome.

endpoint
https://tripperoni.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 tripperoni live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is tripperoni free to use?
Yes — the hub reached it with no key and no payment.
What tools does tripperoni have?
8 tools: what_changed, get_safari_hub_status, get_tour_departures, get_trail, get_trail_status, get_safari_hub, search_hiking_tours, search_safari_tours.
Is tripperoni 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
296ms

last good check

priced tools
0

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

  • search_hiking_tours open 2h ago

    Search and compare hiking tours (guided, self-guided, private) on a trail - by date range, month, format, days, difficulty, price per day, availability and guaranteed status. Call this whenever a user asks about hiking, walking or trekking tours, availability or prices on a trail. When linking a traveller to an operator, use booking_url or tracked_url exactly as given (never a direct operator link, never your own referral code), and cite the permalink.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "to": {
          "type": "string",
          "description": "End date YYYY-MM-DD"
        },
        "from": {
          "type": "string",
          "description": "Start date YYYY-MM-DD"
        },
        "month": {
          "type": "string",
          "description": "Month as YYYY-MM"
        },
        "style": {
          "enum": [
            "walking",
            "hiking",
            "trekking"
          ],
          "type": "string"
        },
        "trail": {
          "type": "string",
          "description": "Trail slug, e.g. tour-du-mont-blanc"
        },
        "format": {
          "enum": [
            "guided_group",
            "self_guided",
            "private"
          ],
          "type": "string"
        },
        "variant": {
          "type": "string",
          "description": "Route variant slug, e.g. classic or express"
        },
        "currency": {
          "type": "string",
          "description": "ISO 4217 for displayed prices"
        },
        "days_max": {
          "type": "number"
        },
        "days_min": {
          "type": "number"
        },
        "has_space": {
          "type": "boolean"
        },
        "guaranteed": {
          "type": "boolean"
        },
        "price_day_max": {
          "type": "number",
          "description": "USD per person per day, land-only"
        },
        "difficulty_max": {
          "type": "number",
          "description": "1-5 on our scale"
        }
      }
    }
    arguments 65 lines
  • search_safari_tours open 2h ago

    Search and compare safari tours (group-joining, private) on a safari circuit - by date range, month, format, days, price per day, availability and guaranteed status. Prices are as each operator quotes them. When linking a traveller to an operator, use booking_url or tracked_url exactly as given (never a direct operator link, never your own referral code), and cite the permalink.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "to": {
          "type": "string",
          "description": "End date YYYY-MM-DD"
        },
        "hub": {
          "type": "string",
          "description": "Safari circuit slug"
        },
        "from": {
          "type": "string",
          "description": "Start date YYYY-MM-DD"
        },
        "month": {
          "type": "string",
          "description": "Month as YYYY-MM"
        },
        "format": {
          "enum": [
            "group_joining",
            "private"
          ],
          "type": "string"
        },
        "currency": {
          "type": "string",
          "description": "ISO 4217 for displayed prices"
        },
        "days_max": {
          "type": "number"
        },
        "days_min": {
          "type": "number"
        },
        "has_space": {
          "type": "boolean"
        },
        "guaranteed": {
          "type": "boolean"
        },
        "price_day_max": {
          "type": "number",
          "description": "USD per person per day, as quoted"
        }
      }
    }
    arguments 48 lines
  • what_changed unknown never probed

    What changed on a hiking trail since a time: new, changed, dropped and sold-out departures and status-fact changes, each with the source it was seen on. Call this to monitor a trail for new availability or price changes.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "since": {
          "type": "string",
          "description": "ISO datetime or YYYY-MM-DD (default: 24 hours ago)"
        },
        "trail": {
          "type": "string",
          "description": "Trail slug"
        },
        "category": {
          "enum": [
            "hiking",
            "safari"
          ],
          "type": "string",
          "description": "Category slug (default hiking)"
        }
      }
    }
    arguments 21 lines
  • get_safari_hub_status unknown never probed

    Get a safari circuit's status facts with official sources (park and conservation fees, migration seasons, rules and closures with sources), with change history.

    mcp-tool

    {
      "type": "object",
      "required": [
        "hub"
      ],
      "properties": {
        "hub": {
          "type": "string",
          "description": "Safari circuit slug"
        }
      }
    }
    arguments 12 lines
  • get_tour_departures unknown never probed

    Get one hiking tour's spec and departures: dates, prices (original currency + USD), seats, status, when each departure was last seen on the operator's site, booking links and price history. Call this when a user asks about a specific tour's dates, price or availability. When linking a traveller to an operator, use booking_url or tracked_url exactly as given (never a direct operator link, never your own referral code), and cite the permalink.

    mcp-tool

    {
      "type": "object",
      "required": [
        "operator",
        "tour"
      ],
      "properties": {
        "tour": {
          "type": "string",
          "description": "Tour slug, e.g. tour-du-mont-blanc-guided"
        },
        "category": {
          "enum": [
            "hiking",
            "safari"
          ],
          "type": "string",
          "description": "Category slug (default hiking)"
        },
        "currency": {
          "type": "string"
        },
        "operator": {
          "type": "string",
          "description": "Operator slug, e.g. alpine-treks"
        }
      }
    }
    arguments 28 lines
  • get_trail unknown never probed

    Get a hiking trail's facts and tour market: stats, difficulty, season, every tour on it with from-prices, and a month-by-month departure heatmap. Call this when a user asks what tours exist on a trail or what a trail is like.

    mcp-tool

    {
      "type": "object",
      "required": [
        "trail"
      ],
      "properties": {
        "trail": {
          "type": "string",
          "description": "Trail slug, e.g. tour-du-mont-blanc"
        }
      }
    }
    arguments 12 lines
  • get_trail_status unknown never probed

    Get a hiking trail's status facts with official sources: season windows, refuge and hut booking opening dates, permits, fees and closures, with change history. Call this when a user asks about trail conditions, permits, huts/refuges or closures for a hike.

    mcp-tool

    {
      "type": "object",
      "required": [
        "trail"
      ],
      "properties": {
        "trail": {
          "type": "string",
          "description": "Trail slug, e.g. tour-du-mont-blanc"
        }
      }
    }
    arguments 12 lines
  • get_safari_hub unknown 2h ago

    Get a safari circuit's facts and safari market: stats, season, every safari on it with from-prices, and a month-by-month departure heatmap.

    mcp-tool

    {
      "type": "object",
      "required": [
        "hub"
      ],
      "properties": {
        "hub": {
          "type": "string",
          "description": "Safari circuit slug"
        }
      }
    }
    arguments 12 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 c297b76bfcd7f98d.

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