NextTrace MCP
During a network incident, an agent retrieves the route to a service while the administrator controls diagnostic access.
- 8,272 ★ on the repository
- Last commit
- GPL-3.0
Extended access
Why this level
- The server sends diagnostic probes and exposes routes to the agent; listening on an external address makes these operations remotely accessible.
Install
- Works in
Manual install
curl -sL https://nxtrace.org/nt | bashFirst automated full-build installer in the README.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The server sends diagnostic probes and exposes routes to the agent; listening on an external address makes these operations remotely accessible.
This is third-party code. Review the repository files before installing.
What it does
NextTrace MCP returns traceroute results to an agent: which hops responded on the path to a target and what IP information is available. An agent can compare routes from different runs when investigating a connection failure. MCP is included in the full NextTrace build. Start `nexttrace --deploy --mcp` and add `http://127.0.0.1:1080/mcp` to the client as Streamable HTTP. The service runs as a separate process; saving client configuration does not start it.
Who it is for. Network administrators exposing route diagnostics to an agent through their own NextTrace server.
Good fit when
- An agent investigates an approved server connection through tracing.
- A user wants diagnostics in a persistent local process.
- An administrator compares hop responses before and after a network change.
- A remote client needs separately protected diagnostic access.
Not a fit when
- You expect this MCP to run over stdio without a service.
- A reduced build lacks deployment support.
- Probes would target a network without authorization.
Example request
Discover local NextTrace MCP capabilities and run one trace to the approved server, retaining the result for comparison.MCP
- Transport
- http
- Authentication
- key is optional
Environment variables
NEXTTRACE_DEPLOY_TOKENsecret- Optional user-supplied deployment-server token
Limitations
MCP requires the full build with `--deploy`; Tiny and NTR do not include it. Local addresses `127.0.0.1`, `::1` and `localhost` are tokenless by default. External addresses require a token. If none is configured, NextTrace generates one and prints it to stdout, which must remain private. IP location information depends on the data provider and its quotas; an empty location field does not mean the hop failed to respond.
How to disable. Stop the NextTrace deployment process and remove the client connection. Rotate or revoke the token when remote access ends.
FAQ
Which address should a local client use?
The documented example is `http://127.0.0.1:1080/mcp`.
Does adding it to OpenClaw start NextTrace?
No. Start the service separately before connecting.
Where does the access token go?
Use `Authorization: Bearer <token>` or `X-NextTrace-Token`. Set the server token with `--deploy-token` or `NEXTTRACE_DEPLOY_TOKEN`; it is separate from GeoIP API credentials.
Which tools should the agent call first?
Call `nexttrace_capabilities` to inspect available operations, then `nexttrace_traceroute` to trace the selected target.
Does missing geography mean a hop is unavailable?
No. IP enrichment and network responses come from different sources.
Discussion
No questions or reviews yet.
Related
MCP serversMCP server for Cisco Packet Tracer: an agent plans a network, builds it on the canvas and proves connectivity with ping.
A proxy between MCP transports: connects stdio clients to remote SSE and HTTP servers and exposes local servers over the network
Datadog's official managed MCP server: logs, metrics, traces and incidents right in your agent
A self-hosted gateway that merges several MCP servers into one endpoint with auth and tool selection
Tmux MCP Server: agent access to tmux sessions
Tmux MCP Server
An MCP server that lets an agent read tmux panes, run commands in them and create sessions while you watch the output
An MCP server built into the Netdata agent: metrics, logs, alerts and live process, service and container data for an AI assistant
README in short
The README distinguishes full, Tiny and NTR builds. MCP shares the NextTrace network server with WebUI and API.