Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.BenAHammond/code-auditor-mcp

REMOTE · WWW.CODEAUDITORMCP.COM · 2 COMPONENTS

Enforces architectural invariants and code quality rules inside your AI agent's edit loop.

68 Trust /100

Last scanned (23 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 16 Oct 2026.

Category Developer Tools

Recent critical change

Authorization (12 Oct 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 371 tokens (~92/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage80
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 30% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 −9
    • Authorization: partial → fail ▼ critical
    • New tool “request_rule”, which the server declares destructive security
    • Tool coverage: 100% → 30% ▼ functional
    • Schema quality: 83 → 92 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
  • 11 Oct 26 75

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 16 Oct 2026 · Probed https://www.codeauditormcp.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.codeauditormcp.com CN=YR1,O=Let's Encrypt,C=US 1 Sept 2026 30 Nov 2026 RSA 2048 SHA256-RSA 5f19f57d664ed498db7362a0836ae4a3caa
SANs: *.codeauditormcp.com, codeauditormcp.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.codeauditormcp.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
codeauditormcp.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.codeauditormcp.com/api/mcp Verified 200
http (plaintext) http://www.codeauditormcp.com/api/mcp HTTPS enforced 308 https://www.codeauditormcp.com/api/mcp
MCP tools · 4 exposed · ~371 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
explain_symptom ~75

Map a natural-language symptom (e.g. 'my app is slow', 'hardcoded password', 'infinite react loop') to the relevant Code Auditor rule(s) and their fixes. Call this when a user describes a problem rather than naming a rule.

NameTypeReqDescription
symptomstringyesA plain-language description of the problem.
NameTypeReqDescription
hintstring––
matchesarrayyes–

No examples provided.

get_install_commands ~90

Return the exact install commands for Code Auditor for a given AI agent. Call this when a user asks how to install Code Auditor, or asks for the command for a specific agent (claude, cursor, codex, gemini, agents, zcode, or all).

NameTypeReqDescription
agentstringyesThe AI agent to install for (e.g. claude, cursor, codex, all).
NameTypeReqDescription
agentstringyes–
commandsarrayyes–
displayNamestringyes–
notestring––

No examples provided.

lookup_rule ~84

Return the rule kind, description, default severity, detection method, and threshold for a given Code Auditor rule or analyzer. Call this when a user asks what a specific rule does (e.g. import-ban, sql-injection, n+1).

NameTypeReqDescription
rule_idstringyesRule or analyzer id, e.g. import-ban, sql-injection, n+1.

Structured output declared, but exposes no named fields.

No examples provided.

request_rule ~122

Request a new Code Auditor rule. Call lookup_rule or explain_symptom first to confirm no existing rule covers it. Provide a minimal example that should be flagged and a corrected example that should not. Reduce both to the smallest code that shows the difference, and remove secrets and proprietary identifiers. Returns a receipt id.

NameTypeReqDescription
cleanExamplearrayyes–
firingExamplearrayyes–
languagesarrayyes–
signalstringyes–
symptomstringyes–
titlestringyes–
toolVersionstring––
NameTypeReqDescription
duplicateSubmissionbooleanyes–
existingRuleMatchesarrayyes–
idstringyes–

No examples provided.

Install

How do I install the io.github.BenAHammond/code-auditor-mcp server?

io.github.BenAHammond/code-auditor-mcp is a hosted endpoint at https://www.codeauditormcp.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · www.codeauditormcp.com

# add to Claude Code
claude mcp add --transport http benahammond-code-auditor-mcp 'https://www.codeauditormcp.com/api/mcp'
Common questions

What is the io.github.BenAHammond/code-auditor-mcp server?

io.github.BenAHammond/code-auditor-mcp is listed in the public MCP registry as io.github.BenAHammond/code-auditor-mcp. Enforces architectural invariants and code quality rules inside your AI agent's edit loop. This page covers its hosted endpoint (https://www.codeauditormcp.com/api/mcp).

Is the io.github.BenAHammond/code-auditor-mcp server safe to use?

io.github.BenAHammond/code-auditor-mcp scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.BenAHammond/code-auditor-mcp server expose?

io.github.BenAHammond/code-auditor-mcp exposes 4 tools: get_install_commands, lookup_rule, explain_symptom, request_rule. Their descriptions and schemas cost roughly 371 tokens of context every time the server is loaded.

Does the io.github.BenAHammond/code-auditor-mcp server require authentication?

No. We connected to io.github.BenAHammond/code-auditor-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.BenAHammond/code-auditor-mcp server still maintained?

io.github.BenAHammond/code-auditor-mcp is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.