Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Tripperoni

REMOTE · TRIPPERONI.COM

Compare multi-day hiking and safari tours by departure: dates, prices, seats and trail status.

Available components

65 Trust /100

Last scanned (16 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1205 tokens (~150/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 67% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 16 Nov 26 62

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://tripperoni.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=tripperoni.com CN=WE1,O=Google Trust Services,C=US 13 Oct 2026 11 Jan 2027 ECDSA 256 ECDSA-SHA256 aab1f1af240145290e273d0c0834a735
SANs: tripperoni.com, *.tripperoni.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of tripperoni.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
tripperoni.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=15552000
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://tripperoni.com/mcp Verified 200
http (plaintext) http://tripperoni.com/mcp HTTPS enforced 301 https://tripperoni.com/mcp
MCP tools · 8 exposed · ~995 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_safari_hub ~53

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.

NameTypeReqDescription
hubstringyesSafari circuit slug

No output schema declared.

No examples provided.

get_safari_hub_status ~51

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

NameTypeReqDescription
hubstringyesSafari circuit slug

No output schema declared.

No examples provided.

get_tour_departures ~160

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.

NameTypeReqDescription
categorystring–Category slug (default hiking)
currencystring––
operatorstringyesOperator slug, e.g. alpine-treks
tourstringyesTour slug, e.g. tour-du-mont-blanc-guided

No output schema declared.

No examples provided.

get_trail ~81

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.

NameTypeReqDescription
trailstringyesTrail slug, e.g. tour-du-mont-blanc

No output schema declared.

No examples provided.

get_trail_status ~82

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.

NameTypeReqDescription
trailstringyesTrail slug, e.g. tour-du-mont-blanc

No output schema declared.

No examples provided.

search_hiking_tours ~268

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.

NameTypeReqDescription
currencystring–ISO 4217 for displayed prices
days_maxnumber––
days_minnumber––
difficulty_maxnumber–1-5 on our scale
formatstring––
fromstring–Start date YYYY-MM-DD
guaranteedboolean––
has_spaceboolean––
monthstring–Month as YYYY-MM
price_day_maxnumber–USD per person per day, land-only
stylestring––
tostring–End date YYYY-MM-DD
trailstring–Trail slug, e.g. tour-du-mont-blanc
variantstring–Route variant slug, e.g. classic or express

No output schema declared.

No examples provided.

search_safari_tours ~204

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.

NameTypeReqDescription
currencystring–ISO 4217 for displayed prices
days_maxnumber––
days_minnumber––
formatstring––
fromstring–Start date YYYY-MM-DD
guaranteedboolean––
has_spaceboolean––
hubstring–Safari circuit slug
monthstring–Month as YYYY-MM
price_day_maxnumber–USD per person per day, as quoted
tostring–End date YYYY-MM-DD

No output schema declared.

No examples provided.

what_changed ~96

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.

NameTypeReqDescription
categorystring–Category slug (default hiking)
sincestring–ISO datetime or YYYY-MM-DD (default: 24 hours ago)
trailstring–Trail slug

No output schema declared.

No examples provided.

Install

How do I install the Tripperoni MCP server?

Tripperoni is a hosted endpoint at https://tripperoni.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · tripperoni.com

# add to Claude Code
claude mcp add --transport http com-tripperoni-tripperoni 'https://tripperoni.com/mcp'
Common questions

What is the Tripperoni MCP server?

Tripperoni is an MCP server listed in the public MCP registry as com.tripperoni/tripperoni. Compare multi-day hiking and safari tours by departure: dates, prices, seats and trail status. This page covers its hosted endpoint (https://tripperoni.com/mcp).

Is the Tripperoni MCP server safe to use?

Tripperoni scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Tripperoni MCP server expose?

Tripperoni exposes 8 tools: search_hiking_tours, get_tour_departures, get_trail, get_trail_status, what_changed, and 3 more. Their descriptions and schemas cost roughly 995 tokens of context every time the server is loaded.

Does the Tripperoni MCP server require authentication?

No. We connected to Tripperoni without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Tripperoni MCP server still maintained?

Tripperoni is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Tripperoni MCP server?

VerifyMCP ran 12 checks on Tripperoni, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Tripperoni: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.