check_consent

2 registry entries were observed exposing a tool named check_consent — none of them flagged as a privileged capability.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 13,558 of 45,202 scannable entries (30%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

1. @honkio/mcpMCPcommunitylivetrust 60/100 · B

   v1.13.0

   ↓ 90/wk

   HonkIO MCP server: lets AI agents send SMS and email in Canada, verify phone numbers, and manage CASL consent

   ClaudeCursorCopilotChatGPTGemini

   ca.honkioMIT7d agonpmGitHub+compareobserved 2026-09-08 · static extraction

   mcpmcp-servermodel-context-protocolsmsemailcanada
2. io.github.thegridwork/privacyMCPcommunitytrust 60/100 · B

   v1.0.0

   ★ 1

   Audit websites for GDPR, CCPA, and ePrivacy compliance — trackers, consent, and policies.

   ClaudeCursorCopilotGemini

   io.github.thegridworkUnknown6mo agonpmGitHub+compareobserved 2026-06-13 · static extraction

   mcp

All indexed toolsSearch the registry for check_consent