Borrowing it
Nothing to install: this file belongs to kungfusheep/mcpview. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kungfusheep/mcpview/main/CLAUDE.mdgit clone --depth 1 https://github.com/kungfusheep/mcpviewWrote 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/instructions/kungfusheep/mcpview/claude-md)<a href="https://agentmods.dev/instructions/kungfusheep/mcpview/claude-md"><img src="https://agentmods.dev/badge/instructions/kungfusheep/mcpview/claude-md.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.01082 | $0.01082 |
| Opus 5 | $0.00541 | $0.00541 |
| Sonnet 5 | $0.00216 | $0.00216 |
| Haiku 4.5 | $0.00108 | $0.00108 |
Grade A, and why
mcpview CLAUDE.md 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
MCP Explorer (mcpview) is a terminal UI application for developing and debugging MCP (Model Context Protocol) servers. Written in Go following a single-file architecture pattern, it provides both interactive exploration and headless proxy functionality.
Build and Run Commands
# Build the application
go build -o mcpview .
# Run in explorer mode (default)
./mcpview
# Run in debug mode with live message pane
./mcpview --debug
# Run in stdio proxy mode (headless - no TUI)
./mcpview --proxy --target "python server.py"
# Auto-connect to MCP server
./mcpview --server "python my_server.py"
# Debug mode with auto-connect
./mcpview --debug --server "node server.js"
# Show help
./mcpview --help
# Run directly without building
go run .
# Install dependencies
go mod tidy
# Format code
go fmt .
# Vet code for issues
go vet .
Current Features
Core MCP Client
- ✅ JSON-RPC 2.0 communication over stdio transport
- ✅ MCP protocol initialization and tool/resource discovery
- ✅ Dynamic form generation from JSON schemas (string, number, boolean, array, object)
- ✅ Tool execution with parameter validation
- ✅ Message logging with timestamps and direction tracking
Terminal UI (Bubbletea)
- ✅ Connection screen for server command input
- ✅ Tools list browser with navigation
- ✅ Tool detail view with three-pane layout:
- Tool info (dynamic height based on description)
- Parameter form (scrollable, resizable)
- Response viewer (scrollable, with execution history)
- ✅ Resources list browser
- ✅ Message history viewer with pretty-printed JSON
- ✅ Debug mode with split-pane layout (messages top, tools bottom)
Stdio Proxy Mode
- ✅ Headless transparent proxy between MCP client and server
- ✅ Message interception and logging
- ✅ Automatic target server process management
- ✅ Works with any MCP client (Claude Desktop, etc.)
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.
- 7d ago First seen · 155 lines · 1,082 tokens per session scan A 24899ca03749
mcpview CLAUDE.md is an instructions file published in the GitHub repository kungfusheep/mcpview (5 stars, last pushed 1y ago), licensed Apache-2.0. It adds 1,082 tokens to every session, about $0.0054 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.