Watchlist tracking
Reviewed for relevance and future tracking value.
MCP100 Assessment
Watchlist / Tracking
Why we’re tracking it
Monitor exact implementation activity, MCP interface, permission and setup changes.
Reviewed · Documentation review; complete setup workflow not independently tested
Best fit
MCP tool-call inspection and proxy tracing
What we know
Wireshark for MCP. A transparent proxy that shows every real tool call between your AI client and your MCP servers, live in your terminal. Public Radar listing describes capability; verify precise runtime setup and privilege boundaries upstream.
Maintenance / activity evidence
- GitHub exact repo pushed_at 2026-10-07T09:32:58Z
Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.
Verification gaps / watch-outs
- Installation and comprehensive security have not been independently audited.
- Transparent MCP proxy can inspect tool inputs, outputs and secrets; do not log credentials in production. Complete write authority is not verified.
- Refer to first-party setup documentation; do not infer authorization from package existence.
- Sensitive access: MCP tool payloads and possibly secrets
- Transparent MCP proxy can inspect tool inputs, outputs and secrets; do not log credentials in production.
- Public tracking suitability is not an installation safety audit.
Full authority, access and evidence limits are available in Review context and Access & risk.
Popularity
361 repository stars
Stars observed Oct 10, 2026.
Repository total for kerlenton/mcpsnoop.
All limitations / Review context
Has mcpsnoop changed its documented MCP interface, authentication or privilege boundaries, and does it merit promotion?
Limited editorial listing; known permission implications disclosed, no independently established publication blocker.
- Transparent MCP proxy can inspect tool inputs, outputs and secrets; do not log credentials in production.
- Public tracking suitability is not an installation safety audit.
- Refer to first-party setup documentation; do not infer authorization from package existence.
- MCP tool payloads and possibly secrets
- Sensitive access: MCP tool payloads and possibly secrets
- Complete write authority is not verified.
- Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
- Upstream credential and permission scopes must be validated before runtime use.
- Precise setup/auth/permissions not verified
- Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
- Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted.
- Exact GitHub pushed_at 2026-10-07T09:32:58Z
Original activity observations
- GitHub exact repo pushed_at 2026-10-07T09:32:58Z
Technical identity
github.com/kerlenton/mcpsnoop- Exact implementation source
- https://github.com/kerlenton/mcpsnoop ↗
- Reviewed resource type
- Testing / Debugging
- Repository identity
- kerlenton/mcpsnoop
Evidence & Sources
- Evidence basis
- Recorded source evidence
- Setup runtime verification
- Not independently runtime-tested by MCP100 for this setup workflow.
Reviewed · Latest source observation
- GitHub repository ↗
kerlenton/mcpsnoop
Recorded repository material and project history.
Setup · Watchlist
Testing / Debugging setup
Publisher instructions.
Source evidence observed .
Additional setup details required — see the specific gaps below.
Install / connect
Publisher instructionsmcpsnoop is a debugging wrapper placed in front of an existing stdio MCP server.
publisher documented example · Publisher instructions · Review before use
brew install mcpsnooppackage install · Publisher instructions
npm i -g mcpsnoopConfigure / authenticate
Publisher instructionsmcpsnoop is an MCP traffic debugging wrapper, not a provider MCP server. Install via brew install mcpsnoop or Go. `wrap` backs up and rewrites Claude Desktop config; require explicit user approval.
Check connection
Suggested checkCheck active wrapper capture in the publisher mcpsnoop terminal UI and confirm frames appear only for the intended MCP server. Do not use a credentialed write tool as a smoke test.
Remove / uninstall / revoke
MCP100 setup guideReplace `my-server` with the wrapped client entry. Optional uninstall: `npm uninstall -g mcpsnoop` OR `brew uninstall mcpsnoop` matching installed method.
Distinguish client registration removal from software uninstall, persistent data deletion and provider OAuth/API-key revocation.
Remove client registration · MCP100 composed guide
mcpsnoop unwrap my-server
What it does
Wireshark for MCP. A transparent proxy that shows every real tool call between your AI client and your MCP servers, live in your terminal. Public Radar listing describes capability; verify precise runtime setup and privilege boundaries upstream.
- Capability
- Developer Tools
- Resource type
- Testing / Debugging
- Best fit
- MCP tool-call inspection and proxy tracing
Representative uses
- MCP tool-call inspection and proxy tracing
Limitations
- Transparent MCP proxy can inspect tool inputs, outputs and secrets; do not log credentials in production.
- Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted.
- Exact GitHub pushed_at 2026-10-07T09:32:58Z
Reviewed access
Access & risk
Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.
- Authentication
- Refer to first-party setup documentation; do not infer authorization from package existence.
- Permissions
- Transparent MCP proxy can inspect tool inputs, outputs and secrets; do not log credentials in production.
- Data handling
- MCP tool payloads and possibly secrets
- Cost
- Provider or usage fees possible; verify current pricing
- Risk and cautions
- Transparent MCP proxy can inspect tool inputs, outputs and secrets; do not log credentials in production.
Access scope and cautions
- Write actions
- Not verified
- Sensitive access
- MCP tool payloads and possibly secrets
- Risk level
- high
- Security notes
- Transparent MCP proxy can inspect tool inputs, outputs and secrets; do not log credentials in production. Public tracking suitability is not an installation safety audit.
The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.
FAQ
Based on reviewed evidence as of 2026-10-10T03:38:00Z. Watchlist tracking is not a recommendation or a security certification.