DESIGN.md@docs/feature/mcp-tools-pageA
DESIGN.md@docs/feature/mcp-tools-page from jayantdevkar/claude-code-karma is a DESIGN.md file: the design rules coding agents follow in that repo.
mdr add jayantdevkar/claude-code-karma/docs/feature/mcp-tools-page/DESIGN.md@git:20260228.a60a310Pins git:20260228.a60a310 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- DESIGN.md file
- Repository
- jayantdevkar/claude-code-karma
- Path
docs/feature/mcp-tools-page/DESIGN.md- Versions recorded
- 2
- Latest version
- git:20260228.a60a310, committed Feb 28, 2026
- First version recorded
- Feb 16, 2026
- Size
- 22,230 bytes
- Repository stars
- 338
- License
- Apache-2.0
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# MCP Tools Page — Design Document > Feature: Global MCP tool usage visibility across all sessions and projects. --- ## Problem Statement Claude Code Karma surfaces **agents** (who performed work) and **skills** (what workflows were invoked), but has no dedicated view for **MCP tools** — the external systems Claude connects to via the Model Context Protocol. MCP tool usage data already exists in SQLite (`session_tools`, `subagent_tools`) and is partially visible inside plugin detail pages, but users have no way to: - See all MCP servers and tools in one place - Understand which external integrations are most used - Compare main session vs subagent tool usage - Track MCP tool usage trends over time - Navigate from a tool to the sessions that used it --- ## Data Landscape ### What We Already Have **SQLite tables** (in `~/.claude_karma/metadata.db`): | Table | Relevant Columns | MCP Data | |-------|-----------------|----------| | `session_tools` | `session_uuid`, `tool_name`, `count` | All tools with `mcp__` prefix | | `subagent_tools` | `invocation_id`, `tool_name`, `count` | MCP tools used by subagents | …
Read the whole file at its exact version.
How to install
mdr add jayantdevkar/claude-code-karma/docs/feature/mcp-tools-page/DESIGN.md@sha256:0753b9b4701fbf65The line at the top of this page pins the label git:20260228.a60a310, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_z4agtg3c4xjxilbn)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Feb 16, 2026 and Feb 28, 2026, about one every 11 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260228.a60a310 latest | 2026-02-28 | a60a310 | 22,230 B | A | view · diff |
| git:20260216.84b0bd9 | 2026-02-16 | 84b0bd9 | 22,225 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (22230 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
jayantdevkar/claude-code-karma · 338 stars · license Apache-2.0 · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_z4agtg3c4xjxilbn GET https://markdownregistry.com/api/v1/resolve?ref=jayantdevkar/claude-code-karma/docs/feature/mcp-tools-page/DESIGN.md GET https://markdownregistry.com/api/v1/blob/0753b9b4701fbf651d3552e193a16fdc75e19b50f054155abd8347db564e7b58
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: what DESIGN.md is and how agents use it · which agent file does what.