Check whether a real-world fact can be verified before an agent acts on it. **What it does:** business-exists claims are answered on the spot with a dated evidence bundle from public registries (GLEIF LEI records, SEC EDGAR filings, Wikidata, website liveness). Results report observed evidence with sources and an honest confidence — never a bare verdict. - **Free, no auth, no account.** All tools are read-only with no side effects — safe to call speculatively during planning. - `triage_unknowns`: batch every uncertainty in a task; each is classified as answerable-yourself (with a suggested source), verifiable here, or not determinable (with planning advice). - `plan_verification`: map a multi-step plan against which steps rest on checkable real-world facts. - `check_feasibility` / `confirm_before_purchase` / `check_before_relying` / `check_physical_condition`: check a fact before your task depends on it. **Scope limit, stated up front:** claims about individual people (identity, employment, tenancy, background, whereabouts) are refused as a matter of policy, not queued. Also available in the official MCP registry as `dev.veritap/veritap`, or via `npx -y veritap-mcp` for stdio clients. Terms: https://veritap.dev/terms
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 24/25 | Endpoint answers the MCP initialize handshake (3662 ms); slow response -1. |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 6 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 88% of peers
- This listing 87 · peer median 81
- Latency
- Faster than 13% of peers
- This listing 786 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
- Protocol revision −2
— Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/veritapdev/veritap/mcpcurl -X POST https://server.smithery.ai/veritapdev/veritap/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'