Skip to content

byway.world MCP server

world.byway/mcpbyway.worldstreamable-httpv1.8.0Scanned

Byway MCP: call Byway Engine and Byway Atlas, the discovery engine for the real world.

10 tools: 3 change things and 7 only read.

Tools: 0 delete, 0 irreversible, 3 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the byway.world MCP server can do

The byway.world MCP server is published by byway.world, a domain the MCP Registry verified. It has 10 tools. It can create or change data (3 tools: places_on_byway, plan_drive and places_along_route), but cannot delete data. 7 tools only read.

1 tool brings in text other people can write (get_place); 1 tool can send data out of your system (get_place).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 19, 2026, version 1.8.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

10 tools

Changes things 3Claude Code: ask
  • places_along_routeAtlas inventory along a routed drive: every place of a kind within a band of the corridor between two points.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
  • places_on_bywayAtlas 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 deto…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • plan_drivePlan a scenic drive with the Byway engine: real verified stops, honest timing, official scenic byways.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • openWorldHint: false
    • destructiveHint: false
Only reads 7Show 7 read-only tools
  • get_bywayFull detail for one scenic byway or regional route: designation, states or country, length, scenic lookouts on the route, and itineraries that ride it.No findings

    Why it is in this group

    • The name "get_byway" says "get": a word for reading.
    Description, as the server wrote it
    Full detail for one scenic byway or regional route: designation, states or country, length, scenic lookouts on the route, and itineraries that ride it.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_itineraryA classic road-trip itinerary: waypoints, states, and the scenic byways along the route.No findings

    Why it is in this group

    • The name "get_itinerary" says "get": a word for reading.
    Description, as the server wrote it
    A classic road-trip itinerary: waypoints, states, and the scenic byways along the route.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_placeEverything the Byway atlas holds on one place: its own description, the records it traces to (OpenStreetMap, Wikipedia, Wikidata), reconciled public records (GNIS, National Registe…Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "get_place" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • search_bywaysSearch scenic byways and signed routes — the US federal roster plus regional routes (Québec, France, Northern Ireland, Ireland, Iceland, Norway, New Zealand today; growing).No findings

    Why it is in this group

    • The name "search_byways" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • search_destinationsFind 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…No findings

    Why it is in this group

    • The name "search_destinations" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • search_lookoutsScenic lookouts (viewpoints) along a specific byway, or across a US state.No findings

    Why it is in this group

    • The name "search_lookouts" says "search": a word for reading.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • search_placesSearch the Byway atlas of typed places — waterfalls, hot springs, lighthouses, covered bridges, historic sites, beaches, peaks, rest areas, ghost towns, museums and attractions.No findings

    Why it is in this group

    • The name "search_places" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:21 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://www.byway.world/.well-known/oauth-protected-resource/api/mcp
Authorization servers
https://clerk.byway.world
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.byway.world/api/mcp: tools/list returned 10 tools to an anonymous client, including places_on_byway (write), plan_drive (write), places_along_route (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.8.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http byway https://www.byway.world/api/mcp
claude mcp add --transport http byway https://www.byway.world/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__byway__search_byways",
      "mcp__byway__get_byway",
      "mcp__byway__search_lookouts",
      "mcp__byway__get_itinerary",
      "mcp__byway__search_places",
      "mcp__byway__search_destinations"
    ],
    "ask": [
      "mcp__byway__get_place",
      "mcp__byway__places_on_byway",
      "mcp__byway__plan_drive",
      "mcp__byway__places_along_route"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as byway. Review it before you use it.

Capability tags behind 1 rule
  • mcp__byway__get_place untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/world.byway/mcp/verify?hash=d0e047a4c5819ab585e40e19c4b518410ce782cea6f6bceb5681e5d67ad133ec" | jq -e '.changed == false'

Pinned hash d0e047a4c581, from Nov 19, 2026, 12:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/world.byway/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for world.byway/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/world.byway/mcp.svg)](https://radar.anlyon.com/servers/world.byway/mcp)

Source: MCP Registry. Synced Oct 21, 2026, 18:55 UTC.

byway.world MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the byway.world MCP server safe?

No scan can promise that. What its definitions show: 10 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the byway.world MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the byway.world MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the byway.world MCP server have?

10 tools: 3 write, 7 read. places_on_byway, plan_drive, places_along_route, search_byways, get_byway, search_lookouts, get_itinerary, search_places and 2 more.

Does the byway.world MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the byway.world MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): get_place.

Has the byway.world MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.