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 skills/madappgang/claude-code/mcp-standardsnpx skills add MadAppGang/claude-code --skill mcp-standardsgit clone --depth 1 https://github.com/MadAppGang/claude-codeWrote 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/skills/madappgang/claude-code/mcp-standards)<a href="https://agentmods.dev/skills/madappgang/claude-code/mcp-standards"><img src="https://agentmods.dev/badge/skills/madappgang/claude-code/mcp-standards.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.1 | $0.00069 | $0.06678 |
| Opus 5 | $0.00034 | $0.03339 |
| Sonnet 5 | $0.00014 | $0.01336 |
| Haiku 4.5 | $0.00007 | $0.00668 |
Grade A, and why
mcp-standards scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const result = await externalAPI.fetch(id); How it starts
The opening of the file, as written. The whole thing — 1,122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Standards Skill
1. Overview
What is MCP in Claude Code?
Model Context Protocol (MCP) is the standard way to extend Claude Code with custom tools and integrations. MCP servers provide:
- Tool Integration: Connect to external APIs, databases, and services
- Context Providers: Supply relevant information to Claude during conversations
- Action Handlers: Execute operations in external systems
- Data Sources: Access project-specific or organization-specific data
Why Standardization Matters
Standardized MCP servers ensure:
- Predictable Behavior: Developers know what to expect from MCP tools
- Easier Debugging: Consistent patterns make issues easier to identify
- Better Discoverability: Standard naming helps Claude and users find tools
- Maintainability: Common patterns reduce maintenance burden
- Team Consistency: Multiple developers follow same conventions
MCP in the Plugin Ecosystem
MCP servers are plugin components alongside agents, commands, and skills:
plugin/
├── agents/ # Specialized Claude instances
├── commands/ # CLI commands
├── skills/ # Knowledge documents
└── mcp-servers/ # MCP tool providers ← We're here
Key Difference: While agents use built-in tools, MCP servers provide NEW tools that extend Claude's capabilities.
2. MCP Server Structure
Standard Directory Layout
mcp-servers/
├── server-name/
│ ├── index.ts # Server entry point
│ ├── package.json # Dependencies and metadata
│ ├── tsconfig.json # TypeScript configuration
│ ├── README.md # Server documentation
│ ├── tools/ # Tool implementations
│ │ ├── read-tool.ts
│ │ ├── write-tool.ts
│ │ └── index.ts # Tool exports
│ ├── lib/ # Shared utilities
│ │ ├── client.ts # API client
│ │ ├── validation.ts # Input validation
│ │ └── errors.ts # Error handling
│ └── tests/ # Test files
│ ├── read-tool.test.ts
│ └── write-tool.test.ts
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.
- 2d ago First seen · 1,122 lines · 69 tokens per session scan A 139df149f82a
mcp-standards is a skill published in the GitHub repository MadAppGang/claude-code (279 stars, last pushed 5mo ago), licensed MIT. It adds 69 tokens to every session and 6,678 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
mcp-server-enhancement
Guide for safely adding new MCP tools to the AI Counsel server.
mcp-patterns
MCP server building, advanced patterns, and security hardening. Use when building MCP servers, implementing tool handlers, choosing a transport, adding OAuth authentication, wiring MCP Apps UI with @mcp-ui, hardening MCP security, or debugging MCP integrations.
code-review-standards
Discover and apply organization coding standards from .forge-review/ configuration.
frontmcp-config
Use when configuring a FrontMCP server through frontmcp.config or the @FrontMcp options. Covers auth modes (public, transparent, local, remote), OAuth plus credential vault and secureStore, CORS, HTTP port / entry-path prefix / unix socket, security headers (CSP, HSTS, X-Frame-Options, X-Content-Type-Options), rate…
geoserver-rest-api
Use when automating GeoServer management — programmatic workspace, datastore, and layer creation, style upload, service configuration via REST API. GeoServer REST API: manage GeoServer without GUI using curl, Python, or any HTTP client.
mcp-protocol-suite
Model Context Protocol (MCP) tool integration for connecting external MCP servers, enterprise tools, and APIs.