Verificate MCP
ai-verificate-mcp declares 5 capabilities across 5 tools, with 1 critical issue. One of them, no-revocation, is recorded for every server in the index because MCP has no field in which to declare a way to switch a tool off; a missing declaration is not evidence that the control is missing.
Issues
5 of 5 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
5 of 5 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
5 of 5 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
5 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
validate_artifact | read |
declared |
validate_ai_output | read |
declared |
validate_plan | read |
declared |
analyze_code | read |
declared |
generate_code | read |
declared |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-09-14 | 9 | tools/list on https://mcp.verificate.ai/mcp, published in the official MCP registry as ai.verificate/mcp 1.8.7 |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.