Muhammad Hamid.

Drafting a conformance ruleset for MCP servers

The MCP ecosystem has directories and debuggers but no neutral verifier. A ruleset has to be mechanical enough to be trustworthy and narrow enough that maintainers can act on it in an afternoon.

Conformance half

Security half

Tool descriptions are prompt surface. Instruction-override phrases, zero-width and bidi characters, unbounded string arguments that accept absolute paths, and list tools with no limit parameter are all visible before execution, which makes them statically checkable.

The rule that decides adoption

A scanner that flags everything is worse than no scanner. Every rule needs a fixture taken from a real server, and the false-positive log has to be published. Trust is the product; the checks are just the mechanism.

← All notes