Guard Core
io-github-guard-core-guard-core-mcp declares 9 capabilities across 9 tools, with 1 critical issue.
Issues
9 of 9 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.
9 of 9 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.
9 of 9 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.
9 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
versions | read |
declared |
validate_config | read |
declared |
config_fields | read |
declared |
search_docs | read |
declared |
get_doc | read |
declared |
check_payload | read |
declared |
ecosystem | read |
declared |
adapter_setup | read |
declared |
wire_agent | read |
declared |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-12 | 16 | tools/list answered by the PyPI package guard-core-mcp==1.4.5 (published to PyPI as guard-core-mcp, listed in the official MCP registry as io.github.Guard-Core/guard-core-mcp 1.5.0), run in an isolated container with no network access and no credentials |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.