Adds Storybook component and story documentation tools to an MCP server you run yourself.
Agent Inspect MCP Server
agent-inspect · MCP server
Agent Inspect MCP Server is a read-only server for the local coding-agent debug loop. It works on run traces recorded locally by AgentInspect. Your agent can list recent runs and failures, summarise a run, inspect its execution tree, fetch trace facts, see which contract checks failed and compare two runs. It reports the first causal failure without inferring causes from timing alone. It is not meant for uploading traces to a remote host or for editing application code. Its support level is preview.
Written by ooruby from the README of @agent-inspect/mcp-server 6.31.17.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Your agent can debug a failed run from its recorded trace, using the same trace facts as the command line checks.
What you could do with it
- List the most recent failed runs and ask which failure came first in the causal chain.
- Compare two runs to see a structural diff of what changed between them.
- Check which contract checks a run failed and fetch the trace facts behind them.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Read-only MCP server for local AgentInspect TraceFacts, causal failure, and Evidence tools
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 6.31.17, the file with digest sha512-WoT6AN+sodbI/SasuKAQgXnAKSc+VC75lB2BV+nYF9/j/53YLQngB3xfiWb1W0/+Ksn4UDzi3sg5DgCsKv6uoA==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Paste this into your client's MCP configuration.
{
"mcpServers": {
"agent-inspect-mcp-server": {
"command": "npx",
"args": [
"-y",
"@agent-inspect/mcp-server@6.31.17"
]
}
}
}Or run it directly.
npx -y @agent-inspect/mcp-server@6.31.17Pinned to 6.31.17, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- @agent-inspect/mcp-server
- Version read
- 6.31.17
- Resolved
- 2026-10-10
Built from source, attested
npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.
- Repository
- github.com/rajudandigam/agent-inspect
- Commit
- 071de49d66ae
- Built by
- github.com/actions/runner/github-hosted
- Registry publish attestation
- signed by npm · 2026-10-10
- Checked
- 2026-10-10
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/agent-inspect-mcp-server)About this listing
- Kind
- MCP server
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-07
Similar MCP servers
All MCP serversLets your agent control and inspect a live Chrome browser using Chrome DevTools.
Pulls version-specific library docs and code examples straight into your agent's context.
Verification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.