world.byway/mcp
REMOTE · WWW.BYWAY.WORLD
Byway MCP: call Byway Engine and Byway Atlas, the discovery engine for the real world.
Available components
Last scanned (8 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- 50% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1515 tokens (~126/item across 12 items; 10 tools + 2 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 87% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
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.
- 19 Oct 26 0
- Tool “get_place” rewrote its description, which is the text the model reads security
- Tool “search_lookouts” rewrote its description, which is the text the model reads security
- Server version: 1.7.1 → 1.8.0 functional
- 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
- 25 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 Aug 26 0
- First check of Injection markers: pass security
- First check of Judged manipulation: pass security
- Stability: 0.97 → pass security
- First check of Destructive annotations: pass functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- Server version: 1.7.0 → 1.7.1 functional
- 19 Aug 26 0
- Server version: 1.0.0 → 1.7.0 functional
- 18 Aug 26 0
- Tool “search_places” rewrote its description, which is the text the model reads security
- Tool “plan_drive” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- New tool “search_destinations” functional
- “plan_drive” added an optional parameter “budget_min” cosmetic
- “plan_drive” added an optional parameter “depart_at” cosmetic
- 12 Aug 26 0
- Schema quality: 74 → 107 ▼ functional
- Schema quality: 0% → 50% ▲ functional
- New resource “atlas-kinds” functional
- New tool “get_place” functional
- New tool “places_along_route” functional
- New tool “places_on_byway” functional
- New tool “search_places” functional
- 11 Aug 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
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 5 Nov 2026 · Probed https://www.byway.world/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.byway.world | CN=YR1,O=Let's Encrypt,C=US | 18 Sept 2026 | 17 Dec 2026 | RSA 2048 | SHA256-RSA | 520bc4c2f63804cfd3b5ffd06eeb0a37686 |
| SANs: *.byway.world, byway.world | ||||||
| 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 www.byway.world. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| world. | present | 13081 | 8 | Verified |
| byway.world. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.byway.world/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.byway.world/api/mcp | HTTPS enforced | 308 | https://www.byway.world/api/mcp |
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 →
get_byway Get byway details ~56
Full detail for one scenic byway or regional route: designation, states or country, length, scenic lookouts on the route, and itineraries that ride it.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Byway slug from search_byways |
No output schema declared.
No examples provided.
get_itinerary Get road-trip itinerary ~39
A classic road-trip itinerary: waypoints, states, and the scenic byways along the route.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Itinerary slug |
No output schema declared.
No examples provided.
get_place Get place details ~174
Everything the Byway atlas holds on one place: its own description, the records it traces to (OpenStreetMap, Wikipedia, Wikidata), reconciled public records (GNIS, National Register), the scenic byways that pass near it, the nearest verified lookouts, and for a place people walk to from the car (a waterfall, peak, cliff, arch, hot spring, lighthouse or trailhead) the walk in: time, path length one way and climb, with what the numbers come from. Takes the byway.world URL search_places returned, or the place's kind and slug.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Place type |
| slug | string | – | Place slug, ending in the row's 8-hex id |
| url | string | – | The place's byway.world /places URL |
No output schema declared.
No examples provided.
places_along_route Places along a route ~163
Atlas inventory along a routed drive: every place of a kind within a band of the corridor between two points. This returns the raw record, not a plan — to plan a drive with stops chosen for the traveler, use plan_drive. One limit, stated: ghost-town rows live in a separate Wikidata corpus the corridor read cannot see. Asking for one here is refused rather than answered empty; reach them with search_places by state.
| Name | Type | Req | Description |
|---|---|---|---|
| bandMi | number | – | Miles either side of the route (default 30) |
| destination | string | yes | Where it ends (city or place) |
| kind | string | – | Place type to filter on |
| limit | integer | – | – |
| origin | string | yes | Where the drive starts (city or place) |
No output schema declared.
No examples provided.
places_on_byway Places on a byway ~168
Atlas places along one scenic byway: every place of a kind within a band of the drawn route, nearest to the road first, each marked whether it sits on the byway itself or is a detour off it. Only routes with drawn geometry can answer. This is the atlas inventory beside a road, not an itinerary. One limit, stated: ghost-town rows live in a separate Wikidata corpus the corridor read cannot see. Asking for one here is refused rather than answered empty; reach them with search_places by state.
| Name | Type | Req | Description |
|---|---|---|---|
| bandMi | number | – | Miles either side of the route (default 30) |
| byway | string | yes | Byway slug from search_byways |
| kind | string | – | Place type to filter on |
| limit | integer | – | – |
No output schema declared.
No examples provided.
plan_drive Plan a byway ~277
Plan a scenic drive with the Byway engine: real verified stops, honest timing, official scenic byways. Origin and destination are place names — the tool resolves each to the closest matching real place. budget_min is the whole time window (driving plus stops, default 240): a long drive needs a budget comfortably above its direct drive time or there is no slack to spend on stops. Requires a connected Byway account (OAuth sign-in). Set save=true to save the trip to your account.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_min | integer | – | Total minutes for the whole trip, driving plus stops (30-960, default 240). Set well above the direct drive time to make room for stops. |
| depart_at | string | – | Departure time, ISO 8601 with offset (e.g. 2026-08-20T09:00:00-04:00). Defaults to now; must be within 14 days — hours and weather verdicts are real only inside the forecast horizon. |
| destination | string | yes | Where the drive ends (city or place name) |
| interests | array | – | Taste categories to weight stops |
| origin | string | yes | Starting point (city or place name) |
| pace | string | – | leisurely | balanced | efficient |
| save | boolean | – | Save the trip to the account |
No output schema declared.
No examples provided.
search_byways Search scenic byways ~130
Search scenic byways and signed routes — the US federal roster plus regional routes (Québec, France, Northern Ireland, Ireland, Iceland, Norway, New Zealand today; growing). Filter by name, US state, or ISO-2 country. US byways carry byway.world links.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO-2 country (US, CA, FR, GB, IE, IS, NO, NZ); non-US searches regional routes |
| limit | integer | – | – |
| query | string | – | Name text to match |
| state | string | – | Two-letter US state code |
No output schema declared.
No examples provided.
search_destinations Search destinations ~110
Find US destination cities by name or state, with the day trip around each one: the scenic byways, national parks, public land units and campgrounds Byway's registries place within 30 miles. Only cities with a proven weave are listed — every result links to its own byway.world destination page.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rows to return (default 10) |
| q | string | – | City name text to match |
| state | string | – | Two-letter US state code |
No output schema declared.
No examples provided.
search_lookouts Search scenic lookouts ~99
Scenic lookouts (viewpoints) along a specific byway, or across a US state. Every lookout is a real, verified place — coverage is growing. Where known, each carries the walk in from the car: time, path length one way and climb, or roadside (no walk).
| Name | Type | Req | Description |
|---|---|---|---|
| byway | string | – | Byway slug |
| limit | integer | – | – |
| state | string | – | Two-letter US state code |
No output schema declared.
No examples provided.
search_places Search atlas places ~246
Search the Byway atlas of typed places — waterfalls, hot springs, lighthouses, covered bridges, historic sites, beaches, peaks, rest areas, ghost towns, museums and attractions. Locate by US state (which also needs a kind), by a point and radius, or by name; a name given alongside a locator narrows it. Every result links to the byway.world page for that place, and every place traces to its OpenStreetMap or Wikidata record. One limit, stated: ghost-town rows live in a separate Wikidata corpus that the point and name searches cannot read, so they are absent from a kind-less search. Reach them with state + kind, or with get_place. Asking for one any other way is refused, never answered empty.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Place type to filter on |
| lat | number | – | Latitude to search near |
| limit | integer | – | – |
| lon | number | – | Longitude to search near |
| name | string | – | Place name text |
| radiusMi | number | – | Miles around lat/lon (default 30) |
| state | string | – | Two-letter US state code; requires kind |
No output schema declared.
No examples provided.
How do I install the world.byway/mcp server?
world.byway/mcp is a hosted endpoint at https://www.byway.world/api/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 · www.byway.world
claude mcp add --transport http world-byway-mcp 'https://www.byway.world/api/mcp'
What is the world.byway/mcp server?
world.byway/mcp is listed in the public MCP registry as world.byway/mcp. Byway MCP: call Byway Engine and Byway Atlas, the discovery engine for the real world. This page covers its hosted endpoint (https://www.byway.world/api/mcp).
Is the world.byway/mcp server safe to use?
world.byway/mcp scores 85 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 world.byway/mcp server expose?
world.byway/mcp exposes 10 tools: search_byways, get_byway, search_lookouts, get_itinerary, search_places, and 5 more. Their descriptions and schemas cost roughly 1,462 tokens of context every time the server is loaded.
Does the world.byway/mcp server require authentication?
No. We connected to world.byway/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the world.byway/mcp server still maintained?
world.byway/mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.