Groundhog
io-github-dmytrome-groundhog-mcp declares 4 capabilities across 4 tools, with 1 critical issue.
Issues
4 of 4 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.
4 of 4 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.
4 of 4 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.
4 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
read_url | read |
declared |
research | read |
declared |
search | read |
declared |
status | read |
declared |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-21 | 7 | tools/list answered by the PyPI package groundhog-mcp==0.17.2 (published to PyPI as groundhog-mcp, listed in the official MCP registry as io.github.dmytrome/groundhog-mcp 0.17.2), run in an isolated container with no network access and no credentials |
| 2026-10-15 | 7 | tools/list answered by the PyPI package groundhog-mcp==0.17.1 (published to PyPI as groundhog-mcp, listed in the official MCP registry as io.github.dmytrome/groundhog-mcp 0.17.1), 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.