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.
npx agentmods add skills/myeolinmalchi/mcp2cli/mcp-analyzenpx skills add myeolinmalchi/mcp2cli --skill mcp-analyzegit clone --depth 1 https://github.com/myeolinmalchi/mcp2cliWrote 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/skills/myeolinmalchi/mcp2cli/mcp-analyze)<a href="https://agentmods.dev/skills/myeolinmalchi/mcp2cli/mcp-analyze"><img src="https://agentmods.dev/badge/skills/myeolinmalchi/mcp2cli/mcp-analyze.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 | $0.00074 | $0.00343 |
| Opus 5 | $0.00037 | $0.00171 |
| Sonnet 5 | $0.00015 | $0.00069 |
| Haiku 4.5 | $0.00007 | $0.00034 |
Grade A, and why
mcp-analyze 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 5d 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.
What it actually says
MCP Server Analysis
Analyze an MCP server's source code to extract tools, classify its architecture pattern, and assess CLI conversion feasibility.
How to Analyze
Read the MCP server source code and extract:
- Tools: List every
@tool,server.setRequestHandler(CallToolRequestSchema, ...), or@mcp.tool()definition - Parameters: For each tool, document all input parameters (name, type, required/optional, description)
- Output format: What each tool returns (JSON structure, text, binary)
- Dependencies: External APIs, SDKs, auth requirements
- Transport: stdio, SSE, HTTP — and whether the server is a proxy or direct implementation
- Resources/Prompts: Any MCP resources or prompt templates exposed
Output Format
Create a structured analysis table:
| Tool Name | Params | Output | API Endpoint | Auth |
|-----------|--------|--------|--------------|------|
Then classify the server using references/pattern-classification.md and report:
- Pattern type and tier (1-4)
- CLI conversion feasibility (Excellent / Good / Partial / Not recommended)
- Recommended conversion strategy
- Any blockers or concerns
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 35 lines · 74 tokens per session scan A be87123f8197
mcp-analyze is a skill published in the GitHub repository myeolinmalchi/mcp2cli (4 stars, last pushed 6mo ago), licensed MIT. It adds 74 tokens to every session and 343 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…