Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Gives AI agents a public IPv6 identity, hostname, port forwarding, web fetch, team mesh. Free tier.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
Authorization标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"netid": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/route6me/netid:1.2.5"
]
}
}
}在终端中运行这条命令
claude mcp add --transport http netid https://gw.route6.me/mcp --header 'Authorization: your-value'claude mcp add netid -- docker run -i --rm docker.io/route6me/netid:1.2.5运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"netid": {
"url": "https://gw.route6.me/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"netid": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/route6me/netid:1.2.5"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"netid": {
"type": "http",
"url": "https://gw.route6.me/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"netid": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/route6me/netid:1.2.5"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
Authorization 机密 必填 HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 route6.me 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
在 1519 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:Authorization
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(1.3.4)于3天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, First Sale Scout
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Playbooks and a 14-day checklist for founders winning their first paying customers.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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
1. Get an API key — free account at route6.me (no card).
2. Connect your MCP client to the remote server:
{
"mcpServers": { "route6": { "url": "https://gw.route6.me/mcp", "headers": { "Authorization": "Bearer YOUR_ROUTE6_API_KEY" } } } }
Transport is streamable HTTP; auth is the Authorization: Bearer header. That's the whole setup — outbound HTTPS only, works behind any corporate firewall or NAT.
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
One click, then replace YOUR_ROUTE6_API_KEY with your key. Or add the JSON block above to ~/.cursor/mcp.json.
Use the JSON block above (remote streamable-HTTP server + Bearer header). Detailed per-client guides: docs.route6.me.
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.
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.
| Tier | Tools |
|---|---|
| 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:
my-agent.on.route6.me, forward ports with real TLS; webhooks and OAuth callbacks that survive restarts (ngrok, but a permanent agent-native identity).web_fetch/web_search/scrape from the agent's own IP; DNS64/NAT64 handles IPv4 sites transparently.team_loop — a continuous receive loop so other agents (or humans in the dashboard) can push work to a connected agent in ~1s.*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*