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.
git clone --depth 1 https://github.com/Markgatcha/universal-mcp-toolkitWrote 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/commands/markgatcha/universal-mcp-toolkit/umt-doctor)<a href="https://agentmods.dev/commands/markgatcha/universal-mcp-toolkit/umt-doctor"><img src="https://agentmods.dev/badge/commands/markgatcha/universal-mcp-toolkit/umt-doctor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/markgatcha/universal-mcp-toolkit/umt-doctor"><img src="https://agentmods.dev/badge/commands/markgatcha/universal-mcp-toolkit/umt-doctor.svg" alt="Reviewed on agentmods" width="80" 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.00016 | $0.00201 |
| Opus 5 | $0.00008 | $0.00101 |
| Sonnet 5 | $0.00003 | $0.00040 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
umt-doctor 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 3d 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
Diagnose the user's Universal MCP Toolkit (UMT) setup.
- Run
npx universal-mcp-toolkit doctorfor a full pass over the server registry: missing build outputs, missing environment variables, and config health. - If the user names a specific server, scope it:
npx universal-mcp-toolkit doctor <server-id>. - For each issue reported:
- Missing env var → tell the user exactly which variable and where to set it (shell profile or harness config). Offer to add a placeholder via
umt config -s <id> -t <harness> --write. - Missing build output (workspace mode) → offer
npx universal-mcp-toolkit doctor --fix, which auto-builds the local package.
- Missing env var → tell the user exactly which variable and where to set it (shell profile or harness config). Offer to add a placeholder via
- Finish with a one-line verdict: healthy, or the single next action that fixes the most issues.
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.
- 3d ago First seen · 13 lines · 16 tokens per session scan A 3bb200f25fc4
umt-doctor is a command published in the GitHub repository Markgatcha/universal-mcp-toolkit (13 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 201 once invoked, about $0.0001 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-09-17.
Other commands, from other repositories
preflight
Diagnostique l'environnement Cortex et guide la réparation (DB, extensions, modèles).
latent-fix
Quick fix cho file đang mở hoặc file được chỉ định. Tối đa 1-2 patches.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.