02-mcp-protocol-standards

02-mcp-protocol-standards is a cursor rule for Cursor from gargoyle92/agentify-mcp. It costs 889 tokens per session, scanned A, original, MIT.

A set of rules for building a Model Context Protocol server with the official SDK. MCP is a standard for exposing tools and resources that AI clients can call.

In plain words
What is it for?
Implementing or reviewing MCP servers, including tool schemas, argument validation, resource URIs, client detection, and server components.
Why use it?
It keeps tool inputs validated, responses structured, resources consistently addressed, and behavior adapted to different AI clients.

Cursor rule for Cursor

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 rules/gargoyle92/agentify-mcp/02-mcp-protocol-standards
Clone the repo
git clone --depth 1 https://github.com/gargoyle92/agentify-mcp

Made for: Cursor.

Wrote 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.

agentmods badge for 02-mcp-protocol-standards

README.md
[![agentmods](https://agentmods.dev/badge/rules/gargoyle92/agentify-mcp/02-mcp-protocol-standards.svg)](https://agentmods.dev/rules/gargoyle92/agentify-mcp/02-mcp-protocol-standards)
Your own site
<a href="https://agentmods.dev/rules/gargoyle92/agentify-mcp/02-mcp-protocol-standards"><img src="https://agentmods.dev/badge/rules/gargoyle92/agentify-mcp/02-mcp-protocol-standards.svg" alt="Measured on agentmods" height="20"></a>
Per session 889 This file is loaded in full into every session.
When invoked 889 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original 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.00889 $0.00889
Opus 5 $0.00445 $0.00445
Sonnet 5 $0.00178 $0.00178
Haiku 4.5 $0.00089 $0.00089

Measured 3d ago against content hash 7eb7355f00b1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

02-mcp-protocol-standards 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.

.cursor/rules/02-mcp-protocol-standards.mdc · 111 lines

How it starts

The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.

02-MCP-Protocol-Standards

MCP Protocol Implementation

This project implements the Model Context Protocol (MCP) using @modelcontextprotocol/sdk.

Core MCP Components

CRITICAL MCP RULES - MUST FOLLOW

✅ ALWAYS DO:

  1. Use proper schemas: All tool definitions MUST use proper inputSchema with type, properties, and required fields
  2. Validate tool arguments: Always validate incoming tool arguments against the schema
  3. Return proper response format: Tools must return objects that match MCP response expectations
  4. Handle client detection: Use AgentClientType to provide client-specific tools and resources
  5. Implement proper URI schemes: Resources must use agentify:// URI scheme consistently

❌ NEVER DO:

  1. Skip input validation: Never execute tools without validating input parameters
  2. Return raw strings for complex data: Use structured objects, not plain strings for tool responses
  3. Hardcode resource URIs: Always use the established agentify:// URI pattern
  4. Ignore client context: Never provide tools/resources without checking client type compatibility
  5. Break MCP schema compliance: All responses must conform to MCP protocol specifications

Tool Implementation Standards

Required Tool Structure:

{
  name: string;                    // kebab-case naming
  description: string;             // Clear, actionable description
  inputSchema: {
    type: 'object';
    properties: Record<string, any>; // Detailed parameter definitions
    required?: string[];             // List required parameters
  };
  clientTypes?: AgentClientType[];   // Specify compatible clients
  handler: (args: any, client: AgentClient) => Promise<any>;
}

Read the full file on GitHub · 111 lines

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. 3d ago First seen · 111 lines · 889 tokens per session scan A 7eb7355f00b1

Subscribe to this mod's changes

02-mcp-protocol-standards is a cursor rule published in the GitHub repository gargoyle92/agentify-mcp (1 stars, last pushed 1y ago), licensed MIT. It adds 889 tokens to every session, about $0.0044 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.