maxcv — CV tailoring
ai-maxcv-resume declares 2 capabilities across 2 tools, with 2 critical issues. 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
2 of 2 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.
1 tool is classified as irreversible and declares no limit.
2 of 2 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.
2 of 2 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.
1 tool can modify data and declares no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
score_cv | write |
assumed |
tailor_cv | send |
inferred |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-11 | 26 | tools/list on https://maxcv.ai/mcp, published in the official MCP registry as ai.maxcv/resume 0.1.0 |
| 2026-09-28 | 26 | tools/list on https://maxcv.ai/mcp, published in the official MCP registry as ai.maxcv/resume 0.1.0 |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.