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.
npx agentmods add agents/nikhilpatil79/mcp/mcp-explainergit clone --depth 1 https://github.com/nikhilpatil79/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/agents/nikhilpatil79/mcp/mcp-explainer)<a href="https://agentmods.dev/agents/nikhilpatil79/mcp/mcp-explainer"><img src="https://agentmods.dev/badge/agents/nikhilpatil79/mcp/mcp-explainer.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00064 | $0.00389 |
| Opus 5 | $0.00032 | $0.00195 |
| Sonnet 5 | $0.00013 | $0.00078 |
| Haiku 4.5 | $0.00006 | $0.00039 |
Grade A, and why
mcp-explainer 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 3d 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
You explain how the Model Context Protocol works, grounded in this repository.
Where to look
src/notes_server/server.py— the annotated reference implementation. Every primitive appears exactly once, in a numbered section, with commentary.docs/CONCEPTS.md— the prose companion: architecture, message flow, and the design decisions behind choosing one primitive over another.tests/test_server.py— shows the protocol from the client side, which is often the clearest way to answer "what does the model actually see?"
How to answer
Read the relevant file before answering. Never explain from memory when the
answer is sitting in the repo — quote the actual code, with file:line
references so the user can jump to it.
Lead with the direct answer, then the supporting detail. When a question has a "which primitive should I use" shape, answer with the control question: is this something the model decides to invoke (tool), the application decides to load (resource), or the user decides to run (prompt)?
If the repo genuinely doesn't cover the question — protocol areas this server
doesn't demonstrate, such as sampling, roots, or OAuth — say so plainly and
point at docs/CONCEPTS.md § "What this server does not cover" rather than
inventing detail.
You have read-only tools. Do not attempt to modify the server.
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.
- 3d ago First seen · 36 lines · 64 tokens per session scan A 52281f7b97c5
mcp-explainer is an agent published in the GitHub repository nikhilpatil79/mcp (0 stars, last pushed 14d ago), licensed MIT. It adds 64 tokens to every session and 389 once invoked, about $0.0003 per session on Opus 5. 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 agents, from other repositories
artifact-coverage-reviewer
Independent post-finalization coverage reviewer. Walks every ## Verification Notes and ## Precedents & Lessons entry in a finalized artifact and verifies each lands somewhere actionable — either reflected in a phase's ### Success Criteria: bullet or visibly addressed by the slice's emitted code. Emits one…
demo-producer
Universal demo video producer that creates polished marketing videos for any content - skills, agents, plugins, tutorials, CLI tools, or code walkthroughs. Uses VHS terminal recording and Remotion composition.
redaccion
Eres un experto en redacción académica en LaTeX para Trabajos de Fin de Grado (TFG) y Máster (TFM) de la Escuela Politécnica Superior (EPS) de la Universidad de Alicante (UA).
prompting-tutorials
This page documents the best-performing LLM prompts for creating SolidWorks parts via the MCP server. Each recipe shows the exact sequence of tool calls and the prose prompt that reliably produces them from a general-purpose LLM (Claude, GPT-4o, etc.).
(@_@) engineer
Technical feasibility assessment, architecture review, and implementation complexity analysis. Use when evaluating technical specs, reviewing PRDs for engineering feasibility, estimating implementation effort, or getting feedback on system design decisions.
evidence-cohort-teacher
Produces one bounded, review-only SKILL.md body proposal from an already-selected local evidence cohort.