mcp server
mcp
AI scenic routing engine: byways, lookouts, itineraries, real drive planning. Zero hallucinations.
Description as published by the maintainer. Source
- version 1.0.0
- active
active — Registry entry last updated 2026-07-27.
What this server can do
9 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
get_byway(slug)- Full detail for one scenic byway or regional route: designation, states or country, length, scenic lookouts on the route, and itineraries that ride it. Required: slug.
get_itinerary(slug)- A classic road-trip itinerary: waypoints, states, and the scenic byways along the route. Required: slug.
get_place(url, kind, slug)- 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, and the nearest verified lookouts. Takes the byway.world URL search_places returned, or the place's kind and slug.
places_along_route(kind, limit, bandMi, origin, destination)- 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. Required: origin, destination.
places_on_byway(kind, byway, limit, bandMi)- 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. Required: byway.
plan_drive(pace, save, origin, interests, destination)- 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. Requires a connected Byway account (OAuth sign-in). Set save=true to save the trip to your account. Required: origin, destination.
search_byways(limit, query, state, country)- 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.
search_lookouts(byway, limit, state)- Scenic lookouts (viewpoints) along a specific byway, or across a US state. Every lookout is a real, verified place — coverage is growing.
search_places(lat, lon, kind, name, limit, state, radiusMi)- Search the Byway atlas of typed places — waterfalls, hot springs, lighthouses, covered bridges, historic sites, beaches, peaks, rest areas and ghost towns. 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.
Last successful function declaration observed on . Source: https://www.byway.world/api/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://www.byway.world/api/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-27 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-27 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 9 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | www.byway.world | |
| mcp endpoint status | ok | The server listed 9 functions when asked. | as of probe | www.byway.world |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json