verify_document

4 registry entries were observed exposing a tool named verify_document — 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 8,470 of 26,658 scannable entries (32%) — 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. @signdocs-brasil/mcp-server
   trust 60/100 · BMCP serverobserved 2026-08-09 · static extraction
   Model Context Protocol (MCP) server for the SignDocs Brasil e-signature API — lets AI agents create signing sessions, manage envelopes, veri
2. io.github.intenttext/intenttext-mcp
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   Parse, validate, query, and render IntentText (.it) documents for AI agents
3. io.github.Syronius/cryptair-mcp-server
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   Tamper-evident attestation tools for AI agents — on-chain receipts on Hedera Hashgraph mainnet.
4. omitly-mcp
   trust 60/100 · BMCP serverobserved 2026-08-19 · static extraction
   Omitly's local, verifiable PDF redaction for AI agents — your documents never leave your device.

All indexed toolsSearch the registry for verify_document