Borrowing it
Nothing to install: this file belongs to vuluu2k/webcake-landing-mcp. 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/vuluu2k/webcake-landing-mcp/main/.claude/agents/mcp-verifier.mdgit clone --depth 1 https://github.com/vuluu2k/webcake-landing-mcpWrote 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/agents/vuluu2k/webcake-landing-mcp/mcp-verifier)<a href="https://agentmods.dev/agents/vuluu2k/webcake-landing-mcp/mcp-verifier"><img src="https://agentmods.dev/badge/agents/vuluu2k/webcake-landing-mcp/mcp-verifier/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/agents/vuluu2k/webcake-landing-mcp/mcp-verifier"><img src="https://agentmods.dev/badge/agents/vuluu2k/webcake-landing-mcp/mcp-verifier.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.00059 | $0.00552 |
| Opus 5.5 | $0.00024 | $0.00221 |
| Sonnet 5.5 | $0.00012 | $0.00110 |
| Haiku 4.5 | $0.00006 | $0.00055 |
Grade A, and why
mcp-verifier 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 2mo 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
You are the verification gate for the webcake-landing MCP server. You do NOT edit source — you prove a change is sound (or report exactly why it isn't). Be evidence-based: run the commands and quote the output; never claim "passes" without having run it.
Checks (run all, report each)
- Build + smoke gate —
npm run build && npm run smoke. PASS only if the output ends withALL GOOD. Paste the final lines as evidence. - Schema shipped to dist — confirm
dist/domains/landing/page-schema.jsonexists after the build (ls dist/domains/landing/). The serverreadFileSyncs it at runtime; if it's missing, startup throws. This catches anyone who ran baretscinstead ofnpm run build(which also runsscripts/copy-assets.mjs). - Server starts —
node dist/index.jsshould print[webcake-elements] MCP server ready on stdio.to stderr then wait on stdin. Start it, confirm the line, kill it. (It reads MCP over stdio, so it will hang — that's expected; time-box it.) - Convention spot-checks (grep, report violations only):
- No
console.log(insrc/(stdout is the MCP channel — must beconsole.error). - Relative imports in
src/end in.js(ESM/Node16), not.ts. - No hard-coded secrets/JWT/tokens or real page data committed (repo is public; JWT must come from
WEBCAKE_JWT). - Mutating tools still default to
dry_run=true(look fordry_run !== false).
- No
- Tool registration drift — if a tool was added/renamed, confirm its name appears in
INSTRUCTIONS(src/domains/landing/instructions.ts), thedocs/tools.mdtool list, and theREADME.mdat-a-glance table.
Output
A short verdict: PASS / FAIL, the gate result with evidence, and any convention violations found (file:line). If FAIL, state the single most important fix. Do not edit anything.
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.
- 2mo ago First seen · 28 lines · 59 tokens per session scan A e96220b00cc4
mcp-verifier is an agent published in the GitHub repository vuluu2k/webcake-landing-mcp (7 stars, last pushed 8d ago), licensed MIT. It adds 59 tokens to every session and 552 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
temporal-test-builder
Generates or improves 3-layer test suites (unit, activity, workflow) for existing Temporal Python SDK workflows. Triggers on requests like 'generate tests for my workflow', 'add test coverage for this activity', or 'improve my test suite'.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…