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.

US BIKE TRAVEL

REMOTE · MCP.US-BIKE-TRAVEL.COM · SCANNED SEP 28

MCP-Server: US BIKE TRAVEL Motorradreisen – Suche, Details, Termine, Preise, Vergleich, Anfrage

+2 this week 71 Trust /100
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 Security46
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 430 tokens (~86/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage74
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 22% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the US BIKE TRAVEL MCP server?

US BIKE TRAVEL is a hosted endpoint at https://mcp.us-bike-travel.com/mcp-public.php, 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 · mcp.us-bike-travel.com

# add to Claude Code
claude mcp add --transport http com-us-bike-travel-touren 'https://mcp.us-bike-travel.com/mcp-public.php'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-us-bike-travel-touren": {
      "url": "https://mcp.us-bike-travel.com/mcp-public.php"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-us-bike-travel-touren": {
      "type": "http",
      "url": "https://mcp.us-bike-travel.com/mcp-public.php"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-us-bike-travel-touren]
url = "https://mcp.us-bike-travel.com/mcp-public.php"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-us-bike-travel-touren": {
      "type": "remote",
      "url": "https://mcp.us-bike-travel.com/mcp-public.php",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-us-bike-travel-touren --url 'https://mcp.us-bike-travel.com/mcp-public.php' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-us-bike-travel-touren:
    url: "https://mcp.us-bike-travel.com/mcp-public.php"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-us-bike-travel-touren": {
      "Transport": "http",
      "Url": "https://mcp.us-bike-travel.com/mcp-public.php"
    }
  }
}
# add to Vellum
assistant mcp add com-us-bike-travel-touren -t streamable-http -u 'https://mcp.us-bike-travel.com/mcp-public.php'
// mcp.json
{
  "mcpServers": {
    "com-us-bike-travel-touren": {
      "type": "http",
      "url": "https://mcp.us-bike-travel.com/mcp-public.php"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 26 0
    • Stability: 0.97 → pass security
  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +1

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

  • 21 Sept 26 +1

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

  • 18 Sept 26 +1

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

  • 16 Sept 26 +1

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

  • 14 Sept 26 +1

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

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 28 Sept 2026 · Probed https://mcp.us-bike-travel.com/mcp-public.php

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.us-bike-travel.com CN=YR1,O=Let's Encrypt,C=US 26 Aug 2026 24 Nov 2026 RSA 2048 SHA256-RSA 6ea92973478170af6b8cdfc34d793095f4f
SANs: mcp.us-bike-travel.com, www.mcp.us-bike-travel.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.us-bike-travel.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
us-bike-travel.com. absent 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.us-bike-travel.com/mcp-public.php Verified 200
http (plaintext) http://mcp.us-bike-travel.com/mcp-public.php Served over HTTP 200
MCP tools · 5 exposed · ~430 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
compare_touren ~68

Vergleicht 2 bis 4 Touren fair anhand des vollstaendigen Leistungspakets (Leistungen, Add-ons, Gruppengroesse, Selbstbeteiligung, Schwierigkeitsgrad) -- niemals nur anhand des Preises.

NameTypeReqDescription
idsarrayyes–

No output schema declared.

No examples provided.

get_next_step ~48

Liefert die korrekte Tourseiten-URL und einen allgemeinen Kontaktweg fuer die naechsten Schritte (Anfrage) zu einer konkreten Tour.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_termine_preise ~57

Liefert alle aktuellen Termine, deren Status und Preise einer Tour, inklusive Hinweisen wie "in Planung", "auf Anfrage" oder "derzeit kein Termin ausgeschrieben", falls zutreffend.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_tour_details ~89

Liefert das vollstaendige Leistungspaket einer Tour: Highlights, USPs, enthaltene und nicht enthaltene Leistungen, Add-ons, Gruppengroesse, Schwierigkeitsgrad und die Selbstbeteiligungs-/Versicherungsinformation. Kein reiner Preis-/Dauer-Feed.

NameTypeReqDescription
idstringyesTechnische Tour-ID, z.B. aus search_touren

No output schema declared.

No examples provided.

search_touren ~168

Findet passende US BIKE TRAVEL Motorradtouren anhand von Kundenwuenschen (Region/Erlebnis, Reiseart, Reisemonat, maximale Dauer, maximaler Schwierigkeitsgrad). Liefert eine kompakte Uebersicht inkl. Highlights-Stichworte, Preis (falls verfuegbar) und Selbstbeteiligungs-Kurzinfo -- fuer vollstaendige Details bitte get_tour_details nutzen.

NameTypeReqDescription
maxDauerTageinteger––
maxSchwierigkeitsgradinteger––
monatinteger––
region_oder_tagstring–Suchbegriff, z.B. 'route66', 'suedafrika', 'kanada', 'lasvegas'
typstring––

No output schema declared.

No examples provided.

Common questions

What is the US BIKE TRAVEL MCP server?

US BIKE TRAVEL is an MCP server listed in the public MCP registry as com.us-bike-travel/touren. MCP-Server: US BIKE TRAVEL Motorradreisen – Suche, Details, Termine, Preise, Vergleich, Anfrage. This page covers its hosted endpoint (https://mcp.us-bike-travel.com/mcp-public.php).

Is the US BIKE TRAVEL MCP server safe to use?

US BIKE TRAVEL scores 71 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 US BIKE TRAVEL MCP server expose?

US BIKE TRAVEL exposes 5 tools: search_touren, get_tour_details, get_termine_preise, compare_touren, get_next_step. Their descriptions and schemas cost roughly 430 tokens of context every time the server is loaded.

Does the US BIKE TRAVEL MCP server require authentication?

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

Is the US BIKE TRAVEL MCP server still maintained?

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