@nextscope/mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 2 of 4 tools tried
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y @nextscope/mcp@0.3.0
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
4 tools that take no input and look read-only were called once with nothing. 2 returned a result.
nextscope_status | Returned a result under 0.1 s · 134 characters |
nextscope_list_servers | Returned a result 5.1 s · 187 characters |
nextscope_list_traces | No usable answer tool reported an error: No NextScope MCP sidecar found for route /_nextscope |
nextscope_search_spans | No usable answer tool reported an error: No NextScope MCP sidecar found for route /_nextscope |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
nextscope_status format, writeToFile, overwrite, serverId
Return NextScope collector status and retained trace counts.
nextscope_list_servers format, writeToFile, overwrite
List discovered NextScope development servers available to this MCP bridge.
nextscope_list_traces format, writeToFile, overwrite, serverId, limit, cursor, sort
List retained trace request summaries with pagination.
nextscope_get_trace format, writeToFile, overwrite, serverId, traceId
Return a request-oriented trace diagnostic summary.
nextscope_list_spans format, writeToFile, overwrite, serverId, traceId, limit, cursor
List flattened spans for one trace with depth and timing metadata.
4 more tools
nextscope_get_spans format, writeToFile, overwrite, serverId, traceId, spanIds
Return details for up to 25 spans in one trace.
nextscope_search_spans format, writeToFile, overwrite, serverId, query, traceId, limit, cursor
Search spans by id, name, service, status, or span type across one trace or all retained traces.
nextscope_export_trace format, writeToFile, overwrite, serverId, traceId
Export one complete normalized trace. Use writeToFile for large traces.
nextscope_clear_traces format, writeToFile, overwrite, serverId, confirm
Clear all retained NextScope traces from memory and local persistence. Requires confirm: true.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | not stated |
| Source | github.com/vercel-labs/nextscope |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-sew5wEfkHXMKRO7QZjx/6UwmX4NygtkkbUYO+JxzfBzihptomu4t2A5tA1PFRas7tT8nMRGBI1xvcIovX5iG2A== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40nextscope/mcp)
New version out? Ask for a fresh report.