mcp-server-reviewer

mcp-server-reviewer is an agent for Claude Code from avelikiy/great_cto. It costs 39 tokens per session (2,799 once invoked), scanned A, original, MIT.

A pre-implementation reviewer for MCP servers, which let AI agents call tools and receive data from external systems. It checks tool descriptions, result handling, permissions, network exposure, and API boundaries.

In plain words
What is it for?
Use it before building or publishing an MCP server, or when changing its tools, descriptions, permissions, transport, or scope.
Why use it?
MCP tools run inside an agent's context and may use the user's credentials, so poorly defined tools can cause instruction confusion or unintended access.

Agent for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: model in frontmatter; mentions subagents.

Part of the great-cto plugin — 40 skills, 44 commands, 70 agents shipped together

Good fit Use it before building or publishing an MCP server, or when changing its tools, descriptions, permissions, transport, or scope.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/avelikiy/great_cto/mcp-server-reviewer
Install

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.

Clone the repo
git clone --depth 1 https://github.com/avelikiy/great_cto

Made for: Claude Code.

Or install great-cto, the plugin that ships this one along with the rest of its 40 skills, 44 commands, 70 agents.

Wrote 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.

agentmods badge for mcp-server-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/agents/avelikiy/great_cto/mcp-server-reviewer/github.svg)](https://agentmods.dev/agents/avelikiy/great_cto/mcp-server-reviewer)
Your own site
<a href="https://agentmods.dev/agents/avelikiy/great_cto/mcp-server-reviewer"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/mcp-server-reviewer/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.

agentmods 80×15 button for mcp-server-reviewer

Your own site · 80×15
<a href="https://agentmods.dev/agents/avelikiy/great_cto/mcp-server-reviewer"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/mcp-server-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,799 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00039 $0.02799
Opus 5 $0.00019 $0.01399
Sonnet 5 $0.00008 $0.00560
Haiku 4.5 $0.00004 $0.00280

Measured 5d ago against content hash 60170d88d8da, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

mcp-server-reviewer 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.

agents/mcp-server-reviewer.md · 258 lines

How it starts

The opening of the file, as written. The whole thing — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the MCP Server Reviewer — a specialist subagent for projects whose deliverable is an MCP server.

Every other reviewer here checks an artifact a human or a program will use. An MCP server is the one artifact whose output lands inside another agent's context, where the boundary between data and instruction is a convention rather than a type. api-platform-reviewer covers the HTTP contract, cli-reviewer covers the shell surface, security-officer covers auth. Nobody covers the part where a tool description the server author wrote is read by a model that then acts on it, with the user's credentials, in the user's repo.

Verify the spec, do not recall it. The protocol moves. Before any finding that hinges on a spec requirement, WebFetch https://modelcontextprotocol.io/specification and cite the revision date in the threat model — a finding quoting a superseded rule burns credibility for the next one.

When you're invoked

  • senior-dev pre-impl mode on a project whose deliverable is an MCP server
  • Any change to a tool definition, its description, or its declared scope
  • Before publishing a server (registry listing, npm package, plugin manifest)
  • Adding a tool to an already-approved server — the approval covered the surface as it stood

Not invoked for using an MCP server: consuming one is a trust decision the operator makes, building one is a contract you owe every operator downstream.

What you produce

docs/sec-threats/TM-{slug}.md, MCP-adapted — one section per workflow step below, all of them completed. A step you skipped is a section that says so.

Workflow

Step 1: Read inputs

mkdir -p docs/sec-threats docs/architecture
ARCH=$(ls -t docs/architecture/ARCH-*.md 2>/dev/null | head -1)
[ -z "$ARCH" ] && { echo "BLOCKED: no ARCH file. Architect must run first." >&2; exit 1; }
TM="docs/sec-threats/TM-$(basename "$ARCH" .md | sed 's/^ARCH-//').md"
# the tool definitions — without them there is nothing to review
grep -rlE "setRequestHandler|ListToolsRequestSchema|@mcp\.tool|FastMCP|registerTool" \
  --include="*.ts" --include="*.js" --include="*.mjs" --include="*.py" . | head -20

Read the full file on GitHub · 258 lines

Changes

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.

  1. 5d ago Changed 60170d88d8da
  2. 7d ago Changed · -95 tokens per session 68ad327ecf29
  3. 11d ago First seen · 258 lines · 134 tokens per session scan A 36ef041291e4

Subscribe to this mod's changes

mcp-server-reviewer is an agent published in the GitHub repository avelikiy/great_cto (92 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 2,799 once invoked, about $0.0002 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-30.

Related

Other agents, from other repositories

parallel-reviewer

Parallel code review using 4 specialist agents (elixir-reviewer, security-analyzer, testing-reviewer, verification-runner). Use for thorough review of significant changes.

oliver-kriska/claude-elixir-phoenix · 38 tokens

craft-code-reviewer-deep

Deep code review on Opus 4.8 for high-stakes PRs — release branches, security-sensitive code, large architectural changes, migrations, multi-service flows. Use when extra scrutiny is worth the token cost; use craft-code-reviewer for daily review.

michtio/craftcms-claude-skills · 62 tokens

fec-code-reviewer

Senior review focusing on front-end code (React/Vue/Next/Nuxt, TypeScript, styles, client-side security). Delegate after writing or modifying the front-end; by default, only the review report will be output and placed, and the business code will not be modified directly. Press CRITICAL→LOW to check, control noise and…

bovinphang/frontend-craft · 95 tokens

fec-performance-optimizer

Front-end performance analysis and optimization specialization: Core Web Vitals, packaging volume, runtime and rendering, network and cache, memory leak troubleshooting; can cooperate with Lighthouse, Bundle analysis and Profiler. Use it when users mention page slowness, lag, first screen, package size, poor…

bovinphang/frontend-craft · 0 tokens

fec-figma-implementer

Focus on implementing the proxy of UI components accurately according to the design draft, and save the implementation report as a Markdown file. Supports six design tools: Figma, Sketch, MasterGo, Pixso, Ink Knife, and Mockup. Provide design draft links, selection screenshots or annotation data, automatically obtain…

bovinphang/frontend-craft · 0 tokens

claude-deep-review

Internal Claude subagent for deep code review — security vulnerabilities, bug detection, and performance analysis. Has native codebase access (Read, Grep, Glob, Bash) to trace input paths, follow call chains, profile hot paths, and verify assumptions. Launched automatically by council review workflows — not invoked…

rube-de/cc-skills · 71 tokens