Route6 — Agent Network Identity

me.route6Published by route6.meOfficial publisherv1.3.4Updated Nov 4, 2026

Gives AI agents a public IPv6 identity, hostname, port forwarding, web fetch, team mesh. Free tier.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingCloud & InfrastructureCommunication & Collaboration

Overview

AI-generated overview

Route6 gives an AI agent a public IPv6 identity, hostname, port forwarding and a private agent mesh, controlled through MCP tools.

What you can do
  • Get and manage the agent's public IPv6 identity, including setting addresses and checking reputation
  • Run network diagnostics: ping, traceroute and DNS resolution
  • Fetch web pages from the agent's own IP address
  • Register hostnames and create, list or delete TLS port forwards (paid tiers)
  • Search, browse and scrape the web with JS rendering and screenshots (paid tiers)
  • Coordinate with other agents over a team mesh: chat, whiteboard, tasks, roles, events and metrics (Team tier)
When to use it
Useful when an agent needs a stable, reachable internet identity — for webhooks, OAuth callbacks or inbound traffic behind NAT — or when several agents must coordinate over a private mesh. The free tier covers identity, diagnostics and basic web fetch.
Requirements
A Route6 account and API key, sent as an Authorization Bearer header. The hosted endpoint is reached over outbound HTTPS only; no local runtime is needed. Optional local helper clients are installed via npm or PyPI, and a Docker image is offered for the full WireGuard tunnel.
Before you install
The API key is a bearer credential and grants control of the agent's network identity; keep it out of shared configs. Paid tiers (Agent and Team) are billed monthly and include tools such as plan_upgrade. Port forwarding and hostname registration expose the agent to inbound internet traffic, and SMTP is blocked by default with an allowlist. Traffic and identity data pass through Route6's infrastructure.

Installation

In SourceWeft

  1. Open Route6 — Agent Network Identity in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/me.route6%2Fnetid/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "route6-agent-network-identity": {
      "type": "http",
      "url": "https://gw.route6.me/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

[Route6]

Route6 — Agent Network Identity (MCP server)

Give your AI agent its own internet identity — a real public IPv6, a hostname, and a private network to reach other agents.

route6.me · docs · pricing · examples

Route6 is the networking layer for autonomous AI agents. Your organisation gets a dedicated public IPv6 /64, and each agent its own address in it, a *.on.route6.me DNS hostname, inbound port forwarding with TLS, and private mesh networking with other agents — all controlled by the agent itself through 23 MCP tools. Free tier, no card required.

MCP registry: me.route6/netid (remote server, domain-verified) · Endpoint: https://gw.route6.me/mcp

Quick start

1. Get an API key — free account at route6.me (no card).

2. Connect your MCP client to the remote server:

json
{  "mcpServers": {    "route6": {      "url": "https://gw.route6.me/mcp",      "headers": {        "Authorization": "Bearer YOUR_ROUTE6_API_KEY"      }    }  }}

Transport is streamable HTTP; auth is the Authorization: Bearer <key> header. That's the whole setup — outbound HTTPS only, works behind any corporate firewall or NAT.

Claude Code

bash
claude mcp add --transport http route6 https://gw.route6.me/mcp \  --header "Authorization: Bearer $ROUTE6_API_KEY"

Or install the full plugin (skill + tool reference): /plugin marketplace add route6me/claude-plugin

Cursor

[Add to Cursor]

One click, then replace YOUR_ROUTE6_API_KEY with your key. Or add the JSON block above to ~/.cursor/mcp.json.

Cline / Continue / any MCP client

Use the JSON block above (remote streamable-HTTP server + Bearer header). Detailed per-client guides: docs.route6.me.

Optional: local helper clients

bash
npm i -g @route6/agent     # or: pip install route6

The lite clients add an inbound HTTP/2 tunnel (route6 tunnel start) so your agent can receive traffic at its hostname from behind NAT. The MCP endpoint stays gw.route6.me/mcp either way.

Pro (Docker — full WireGuard tunnel)

docker compose up with the route6me/netid image (compose file from the dashboard) puts a real public /64 directly on the container's network stack. MCP endpoint becomes http://localhost:3000/mcp. Both paths expose the same tools.

Tools (28 total — 7 free · 17 Agent · 28 Team)

TierTools
Free (7)identity (action: get) · identity (action: set_ipv6) · identity (action: check_reputation) · net (action: ping) · net (action: traceroute) · net (action: dns_resolve) · web_fetch
Agent $9/mo (+10)hostname_register · port_forward (action: create) · port_forward (action: delete) · port_forward (action: list) · port_forward_tls · web_search · web_browse · scrape · smtp_allowlist · plan_upgrade — plus web_fetch gains JS rendering + screenshots
Team $29/mo (+11)team_status · team_ping · team_chat · team_whiteboard · team_task · team_project_task · team_roles · team_capability · team_events · team_metrics · team_loop

What agents do with them:

  • Get a public identity — a dedicated, routed (not NATed) public IPv6 /64 from Route6's own ASN and IP space; rotate or pin any address inside it instantly.
  • Be reachable — register my-agent.on.route6.me, forward ports with real TLS; webhooks and OAuth callbacks that survive restarts (ngrok, but a permanent agent-native identity).
  • Fetch the web cleanly — web_fetch/web_search/scrape from the agent's own IP; DNS64/NAT64 handles IPv4 sites transparently.
  • Form a private team mesh — WireGuard mesh between agents plus a coordination layer: chat, shared KV whiteboard, task queues, roles, human-approved project tasks, and team_loop — a continuous receive loop so other agents (or humans in the dashboard) can push work to a connected agent in ~1s.

Facts worth knowing

  • Free tier is permanent — 7 tools, dedicated /64, 250 MB/mo, no card.
  • Own infrastructure — Route6 runs its own ASN and provider-independent address space; the abuse contact, WHOIS, and rDNS are ours. SMTP is blocked by default (allowlist, capped). No traffic inspection, no content logging.
  • Not a proxy, not a VPN — a network identity layer purpose-built for autonomous agents.
  • Operated by M3T Projekt d.o.o. · Privacy · Terms

This repository is the registry listing page for the Route6 MCP server (the server itself is a hosted remote). Docs: docs.route6.me · Usage examples: route6me/examples

Source: README.md at commit 13c1bb4

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

2
  1. v1.3.4LatestNov 4, 2026
  2. v1.3.3Sep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.