Alimenter votre agent
La commande propre à l'éditeur. Ce n'est pas un endpoint PlugMCP.
Host a copy with our keys and logs.
npx -y @agent-inspect/[email protected]Claude Code n'a pas de lien d'installation pour une commande locale. Copiez la commande ci-dessous et exécutez-la dans un terminal.
claude mcp add agent-inspect-mcp-server -- npx -y @agent-inspect/mcp-server@6.31.35À exécuter dans un terminal.
{ "mcpServers": { "agent-inspect-mcp-server": { "command": "npx", "args": [ "-y", "@agent-inspect/[email protected]" ] } }}claude_desktop_config.json
URL distante ou commande sur votre machine ? Ce qui distingue les deux installations
Exécuter sur PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LancerDe l'éditeur
npm install agent-inspect
Agent code rarely fails as one function call. It plans, retrieves, calls tools, invokes a model, retries, and produces side effects. Flat logs show fragments. AgentInspect keeps the run as local JSONL and gives you one evidence loop from the same trace.
Read-only MCP server for local AgentInspect TraceFacts, causal failure, and Evidence tools
See nested steps, tool calls, LLM calls, model and token metadata, durations, errors, and the first causal failure without sending the trace to an AgentInspect service.
npx agent-inspect view <run-id> --dir .agent-inspect --summary
npx agent-inspect report <run-id> --dir .agent-inspect
npx agent-inspect explain <run-id> --dir .agent-inspect
Use manual instrumentation, official adapters, supported standards files, or structured logs you already emit.
Checks are deterministic and provider-free: the same trace and rules produce the same result. Start with a preset, then extend it with the expectations that matter to the workflow.
npx agent-inspect check <run-id> --dir .agent-inspect \
--preset trajectory \
--required-tool retrieve_policy
Use --fail-on-observation failed only when the run records explicit OUTCOME events (for example the broken-agent-debugging starter). Trajectory checks do not invent outcomes from tool/LLM/run success.
A passing check exits 0; a rule failure exits 1. Invalid configuration and unreadable/unsupported inputs use separate documented exit codes. Use TraceContract, suites, cohorts, Vitest/Jest reporters, or --evidence-on fail when the workflow needs more than one CLI check.
npx agent-inspect verify-safe <run-id> --dir .agent-inspect
npx agent-inspect bundle <run-id> --dir .agent-inspect --profile share --out ./evidence
npx agent-inspect bundle verify ./evidence
verify-safe is a best-effort local assessment and can report SAFE, SAFE WITH WARNINGS, UNSAFE, or UNKNOWN. bundle writes a redacted artifact and manifest; bundle verify rechecks the listed file hashes offline. “Share-checked” is not compliance certification—review the artifact before attaching it to a PR, incident, or support handoff.
The generated demo is synthetic, keyless, and local. npm install agent-inspect does not copy repository examples; init writes them into the project.
npm install agent-inspect
npx agent-inspect init --yes
node examples/agent-inspect-demo.mjs
npx agent-inspect list --dir .agent-inspect
Copy the printed run ID, then inspect it:
npx agent-inspect view <run-id> --dir .agent-inspect --summary
npx agent-inspect check <run-id> --dir .agent-inspect --preset trajectory
npx agent-inspect verify-safe <run-id> --dir .agent-inspect
For a fixed good/regression/PII walkthrough with stable run ids (demo-good, demo-regression, demo-pii), use the canonical keyless showcase. The richer blessed starters cover framework-specific paths.
See support levels for Stable, Supported, Beta, Preview, and Experimental surfaces.
import { openTraceFile } from "agent-inspect/readers";
import {
defineTraceContract,
evaluateTraceContractRead,
} from "agent-inspect/checks";
const read = await openTraceFile("./trace.jsonl");
const contract = defineTraceContract({
run: { requireCompleted: true },
tools: { required: ["retrieve_policy"] },
});
const result = evaluateTraceContractRead(read, contract);
if (result.status !== "pass") process.exitCode = 1;
The full API also exposes TraceFacts for bounded, logical analysis of supported traces. See programmatic trace analysis.
AgentInspect owns the laptop-to-PR evidence loop. It complements hosted observability, production trace retention, and broad eval platforms rather than replacing them.
See the factual comparison guide.
.agent-inspect/ or AGENT_INSPECT_TRACE_DIR.redact command creates a separate redacted copy and does not mutate its source.verify-safe are best-effort controls, not privacy, security, or compliance certification.Read network behavior, no-egress policy, and safe trace sharing.
@agent-inspect/mcp-server exposes configured local evidence to an MCP client through bounded, read-only tools. It is optional and currently Preview; the core debug/check/evidence loop does not require it.
npx agent-inspect mcp configure --client cursor
Review the generated dry-run configuration and the coding-agent loop guide before enabling it.
The root package is enough for custom capture, the CLI, checks, and Evidence workflows. Install optional packages only for the integration or surface you use. agent-inspect-vscode is currently in the repository and is not presented as a published Marketplace extension.
Current published baseline: 6.31.27 · persisted schema 1.0 · Node.js >=20 · MIT.
Legacy v0.1 and v0.2 traces remain readable. Check the npm badge and changelog for the current published version.
See CONTRIBUTING.md, good first issues, and GitHub Discussions.
Redact and review traces before posting them in issues or pull requests.
Read-only MCP server for local AgentInspect TraceFacts, causal failure, and Evidence tools
{ "mcpServers": { "agent-inspect-mcp-server": { "command": "npx", "args": [ "-y", "@agent-inspect/[email protected]" ] } }}Outils
Pas encore de liste d'outils. Les serveurs distants en obtiennent une après le premier contrôle d'état.
FAQ
Copiez sur cette page la configuration stdio pour Cursor, Claude Desktop, Claude Code ou VS Code. Elle utilise l'installation de l'éditeur, pas un proxy PlugMCP.
Aucune variable d'environnement requise n'est indiquée sur cette fiche.
@agent Inspect/ s'exécute en local via stdio.
Dernière vérification : 2026-11-15. Read-only MCP server for local AgentInspect TraceFacts, causal failure, and Evidence tools