inspector AGENTS.md

Project instructions for MCP Inspector, a visual testing tool for MCP servers, covering its version, structure, setup, dependencies, and contribution process.

In plain words
What is it for?
Use them when setting up, developing, reviewing, or contributing to MCP Inspector.
Why use it?
They give the coding agent the project rules needed to make compatible changes.

Instructions file for CodexOpenCode

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/modelcontextprotocol/inspector/agents-md
Clone the repo
git clone --depth 1 https://github.com/modelcontextprotocol/inspector

Made for: Codex, OpenCode.

Per session 40,129 This file is loaded in full into every session.
When invoked 40,129 The same file — it is already loaded in full.
Security scan D 2 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.40129 $0.40129
Opus 5 $0.20064 $0.20064
Sonnet 5 $0.08026 $0.08026
Haiku 4.5 $0.04013 $0.04013

Measured yesterday against content hash 419ff8cf9e1e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade D, and why

inspector AGENTS.md scanned grade D with 2 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Reads MCP configurationmediumAgent snooping

mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.

**Every web smoke runs against a throwaway catalog (#1977).** The helper mints a temp dir per run and passes it as `MCP_CATALOG_PATH`; without it the web backend falls back to the developer's real `~/.mcp-inspector/mcp.j

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

│ # same failure class. So `rm -rf test-servers/build`
AGENTS.md · 1,066 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 1,066 lines · 40,129 tokens per session scan D 419ff8cf9e1e

Subscribe to this mod's changes

inspector AGENTS.md is an instructions file published in the GitHub repository modelcontextprotocol/inspector (10,789 stars, last pushed 2d ago), with no licence file. It adds 40,129 tokens to every session, about $0.2006 per session on Opus 5. A static security scan graded it D with 2 findings (reads mcp configuration, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.