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.
git clone --depth 1 https://github.com/ejentum/self-inspect-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/ejentum/self-inspect-mcp/self-inspect)<a href="https://agentmods.dev/mcp/ejentum/self-inspect-mcp/self-inspect"><img src="https://agentmods.dev/badge/mcp/ejentum/self-inspect-mcp/self-inspect/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/ejentum/self-inspect-mcp/self-inspect"><img src="https://agentmods.dev/badge/mcp/ejentum/self-inspect-mcp/self-inspect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
self-inspect scanned grade A with 0 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 2mo ago.
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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"self-inspect": {
"command": "npx",
"args": [
"-y",
"self-inspect-mcp"
]
}
}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.
- 2mo ago First seen · 9 lines scan A 1b59ebf723a6
self-inspect is an MCP server published in the GitHub repository ejentum/self-inspect-mcp (7 stars, last pushed 4mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
strands-docs
A Model Context Protocol server that provides knowledge about building AI agents with Strands Agents. Runs locally from the strands-agents-mcp-server Python package.
nightgate-mcp
MCP server exposing NIGHTGATE (Midnight blockchain attestation layer) to AI agents. Runs locally from the @odatano/nightgate-mcp npm package.
agent-magnet
Self-learning memory infrastructure for AI products. Runs locally from the agent-magnet Python package. Needs 6 environment variables to run.
usrcp
Encrypted local ledger of structured user state, shared across every MCP-aware AI tool. Runs locally from the usrcp npm package. Needs 1 environment variable to run.
memharness
Bi-temporal, provenance-carrying long-term memory for AI agents, in one SQLite file. Runs locally from the @memharness/mcp npm package. Needs 1 environment variable to run.
clink-mcp-server
MCP server for Clink - powering agentic coordination. Runs locally from the @voxos-ai/clink-mcp-server npm package.