Other · Remote MCP server
Verity
Cited product-compliance ground truth for AI agents. Never generates; always cites.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.veritylabsai/verity- Version
- 0.2.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-21
- Updated
- 2026-09-21
- Publisher
- veritylabsai (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/veritylabsai) · how
- Website
- github.com/veritylabsai/verity
- Repository
- github.com/veritylabsai/verity
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://verity-mcp-243195959173.us-central1.run.app/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- rattlewatch 0.2.1 · protocol 2025-06-18
- Tools discovered
- 4:
search_recalls,get_requirement,list_changes,verify - Checked on
- 2026-10-05
How to connect Verity
Verity is a remote MCP server: there is nothing to install. Its endpoint is https://verity-mcp-243195959173.us-central1.run.app/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from veritylabsai (GitHub)
| Server | Runs |
|---|---|
| RattlewatchCited US recall lookup for AI agents: CPSC and FDA data, nothing invented. | Remote · HTTPLive check: ✓ handshake |
More other servers
| Server | Runs |
|---|---|
| VerikoValida y consulta transferencias SPEI mediante la API oficial de Veriko. | Local · stdio |
| VeritapCheck whether a real-world fact can be verified before an agent acts on it. Free, no auth. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Veritasacta VerifyOffline receipt verifier. Ed25519 signature verification without contacting any server. | Local · stdio |
| VerityReal-time fact-checking MCP. Verifies claims against live sources with structured verdicts. | Local · stdio |
| Verity MCPFail-closed verify-before-you-act gate for AI agents. Signed receipts. Pay-per-call via x402. | Local · stdio |
| VerixID VerifierVerify VerixID proof-of-existence records and optionally prove ownership. | Remote · HTTPLive check: ✓ handshake |
| VermarcoMarketplace and payment rail for AI agents: list, buy and settle with signed receipts. | Remote · HTTPLive check: ✓ handshake |
| Version PillProduct management, public changelog, and feature requests - 60 lean MCP tools. | Remote · HTTP, SSELive check: sign-in required |