agentverify-checks
Related Servers
Alternatives to agentverify-checks
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceAppend-only evidence receipts for AI records: seal, verify, cite, chain-check, anchor status. A seal proves a record existed at a time, not that its contents are true. Five tools over stdio with npx -y apex-psi-mcp — no account, no key, verification free forever.5826 npm1MIT

Qinisoofficial
AlicenseAqualityCmaintenanceThe deterministic fact-verification layer for AI agents. Validates the structured facts an agent emits — IBANs, payment cards, VAT and national tax IDs, crypto and bank addresses, domains, emails, phone numbers, securities and academic identifiers, plus dates, currencies and holidays — against checksums and curated authoritative data, not guesses.561Apache 2.0- AlicenseNot gradedqualityDmaintenanceEnables AI agents to verify claims deterministically by computing arithmetic, ratios, and dates and matching statements against provided sources, returning a confidence ladder of certain, source-backed, or unverifiable.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to obtain independent, Ed25519-signed receipts confirming real-world facts: whether a page is online, a domain is legitimate, an email address is deliverable, a heartbeat was declared, or a scheduled task actually ran. Each response includes a verifiable cryptographic receipt, so agents can prove to their users that an asserted outcome was observed by a neutral third party rather than self-attested.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to validate deliverables (JSON, ZIP, PDF, DOCX) against signed contracts, generating verifiable receipts with Ed25519 signatures.-
- AlicenseBqualityBmaintenanceChecks AI agents' claims against primary evidence, with no model; observes only what you grant.8105 PyPIApache 2.0
TDQS
Scored across 5 tools
Each tool targets a distinct operation: single verification, batch verification, verification with signing, receipt signature check, and public key retrieval. The only mild overlap is between verify_calculation and verify_and_sign, but the descriptions make the signing distinction explicit.
All names are snake_case and verb-led (verify_*, check_*, get_*), forming a predictable pattern throughout. verify_and_sign is slightly longer but still follows the convention.
Five tools is well-scoped for a verification-and-signing service, with each tool earning its place. No redundant or filler tools are present.
The surface covers the core lifecycle: verify, batch verify, sign, check receipt, and retrieve public key. Minor gaps exist, such as no batch signing or receipt listing/retrieval, but core workflows are covered.