Add mcp-scope to Resources (passive capture + schema diff tool)

[SSanju]

This is not a server submission. I have read the "no longer accepting PRs to add servers" notice and that does not apply here — this PR adds a one-line entry to the
Resources section of the README, alongside existing community tooling such as mcp-cli, mcp-guardian, and MCPWatch. No server is being added; the MCP Server Registry is not
the right venue for a debugging tool.

Description

Adds mcp-scope to the Resources section. mcp-scope is a passive proxy that sits transparently between any MCP client (Claude Desktop, Cursor, custom scripts) and any MCP server,
captures every JSON-RPC frame to a file, and lets you inspect, summarise, and diff the capture offline. Unlike interactive debuggers, it captures real traffic from real clients
without driving the calls.

Motivation and Context

The Resources section already lists tools that help MCP server developers debug, validate, and manage their servers (mcp-cli, mcp-guardian, MCPWatch, MCP Servers Search,
etc.). mcp-scope fills a specific gap none of them cover: a passive on-the-wire capture/diff tool useful for:

• Reproducing MCP bugs that only surface inside Claude Desktop / Cursor / CI
• Gating MCP server releases in CI — mcp-scope diff baseline.jsonl candidate.jsonl exits non-zero on any breaking schema change in tools/resources/prompts
• Latency profiling per method (p50/p95/p99) via mcp-scope stats
• Sharing captures safely via --redact for secret scrubbing

Project details

• Repo: https://github.com/SSanju/mcp-scope
• License: MIT
• Distribution: Homebrew tap, pre-built binaries (macOS / Linux / Windows), or go install
• Status: v0.1.1 released, single static Go binary, no Node/Python/browser dependency

Types of changes

• Documentation update (one-line addition to Resources section in README)

Checklist

• I have read the MCP Protocol Documentation
• My changes follow the existing format of the Resources section
• Entry is placed alphabetically between MCP Router and MCP Servers Hub

(Other checklist items — LLM client testing, env vars, tests, security best practices — do not apply: this PR adds a single line to the README.)

Additional context

Happy to adjust wording, section placement, or remove the entry if a different fit is preferred. If a separate "Tools" or "Debugging Utilities" subsection would be more appropriate
than the general Resources list, I'm glad to make that structural change as well.

[SSanju]

/i-promise-this-is-not-a-new-server

To clarify: this PR does not add a server. It adds a single line to the Resources section of the README, alongside existing community tooling such as mcp-cli, mcp-guardian,
MCPWatch, and MCP Servers Search. mcp-scope is a passive JSON-RPC capture / schema-diff tool for MCP server developers, distributed as a single static Go binary. The MCP Server
Registry is not the right venue for a debugging tool.

Happy to adjust placement if a different section (e.g. a dedicated "Tools" subsection) is preferred.

[localden]

Thanks for the submission. We no longer accept server, resource, or tooling submissions to this repository; it is dedicated to the small set of reference servers maintained by the MCP steering group. To make your project discoverable, please publish it to the MCP Registry: https://registry.modelcontextprotocol.io/