mcp-server@6.31.39
VERIFIEDPublisher claims: "Read-only MCP server for local AgentInspect TraceFacts, causal failure, and Evidence tools" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Server started and answered tools/list.- Tested
- MCP initialize and tools/list · every tool description, for hidden instructions · every file read, file written and host contacted by what ran
- Not tested
- what the tools do when called with real credentials
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- no vendor host named in the code
- What we saw when it ran
- no credential files read · no network
- What we could not test
- what the tools do when called with real credentials
Reasonable to connect. No credential asked for, no third-party host named, Server started and answered tools/list.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
What changed since 6.31.37
vet-skills diff mcp-server 6.31.37 6.31.39In the sandbox, this version reached for nothing 6.31.37 did not. Compared from the two recorded runs, not from source.
6.31.39 was run further than 6.31.37 (full vs startup only); some additions may be first observations rather than changes. Only one of the two runs produced a tool list; tools are not compared.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-21 and scored it 91/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 22 s · 2 scenarios · 0 deviationsStatic findings
// packages/mcp-server/src/assess-trace.tsFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.// packages/mcp-server/src/assess-trace.tsFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.// packages/mcp-server/src/assess-trace.tsFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for @agent-inspect/mcp-server@6.31.39 as of 25 min ago. This is the package itself, not its dependencies.