Verity
REMOTE · VERITY-MCP-243195959173.US-CENTRAL1.RUN.APP · SCANNED SEP 27
Cited product-compliance ground truth for AI agents. Never generates; always cites.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 332 tokens (~83/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Verity MCP server?
Verity is a hosted endpoint at https://verity-mcp-243195959173.us-central1.run.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · verity-mcp-243195959173.us-central1.run.app
claude mcp add --transport http veritylabsai-verity 'https://verity-mcp-243195959173.us-central1.run.app/mcp'
{
"mcpServers": {
"veritylabsai-verity": {
"url": "https://verity-mcp-243195959173.us-central1.run.app/mcp"
}
}
} {
"servers": {
"veritylabsai-verity": {
"type": "http",
"url": "https://verity-mcp-243195959173.us-central1.run.app/mcp"
}
}
} [mcp_servers.veritylabsai-verity] url = "https://verity-mcp-243195959173.us-central1.run.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"veritylabsai-verity": {
"type": "remote",
"url": "https://verity-mcp-243195959173.us-central1.run.app/mcp",
"enabled": true
}
}
} openclaw mcp add veritylabsai-verity --url 'https://verity-mcp-243195959173.us-central1.run.app/mcp' --transport streamable-http
mcp_servers:
veritylabsai-verity:
url: "https://verity-mcp-243195959173.us-central1.run.app/mcp" {
"McpServers": {
"veritylabsai-verity": {
"Transport": "http",
"Url": "https://verity-mcp-243195959173.us-central1.run.app/mcp"
}
}
} assistant mcp add veritylabsai-verity -t streamable-http -u 'https://verity-mcp-243195959173.us-central1.run.app/mcp'
{
"mcpServers": {
"veritylabsai-verity": {
"type": "http",
"url": "https://verity-mcp-243195959173.us-central1.run.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 0
- Tool “get_requirement” rewrote its description, which is the text the model reads security
- Tool “list_changes” rewrote its description, which is the text the model reads security
- Tool “search_recalls” rewrote its description, which is the text the model reads security
- Tool “verify” rewrote its description, which is the text the model reads security
- Schema quality: 69 → 83 ▼ functional
- Server version: 0.2.0 → 0.2.1 functional
- 21 Sept 26 +7
- Authorization: unverified → partial ▲ security
- The server changed its declared name: verity → rattlewatch security
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.1.0 → 0.2.0 functional
- 20 Sept 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://verity-mcp-243195959173.us-central1.run.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.a.run.app | CN=WR2,O=Google Trust Services,C=US | 10 Sept 2026 | 3 Dec 2026 | ECDSA 256 | SHA256-RSA | 4e0c02d814e3ca0112f85e6a49ac82bb |
| SANs: *.a.run.app, run.app, *.africa-south1.run.app, *.asia-east1.run.app, *.asia-east2.run.app, *.asia-northeast1.run.app, *.asia-northeast2.run.app, *.asia-northeast3.run.app, *.asia-south1.run.app, *.asia-south2.run.app, *.asia-southeast1.run.app, *.asia-southeast2.run.app and 93 more | ||||||
| CN=WR2,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a07c4cded100ad9d66a5107b98 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of verity-mcp-243195959173.us-central1.run.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| run.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://verity-mcp-243195959173.us-central1.run.app/mcp | Verified | 200 | |
| http (plaintext) | http://verity-mcp-243195959173.us-central1.run.app/mcp | HTTPS enforced | 302 | https://verity-mcp-243195959173.us-central1.run.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_requirement ~102
Get cited market-entry requirements for a product subject in a given market (e.g. subject='childrens_products', market='US'). This is a small curated set, not a full regulatory database: CPC, CPSC eFiling, EU GPSR, CE marking, REACH SVHC, RoHS and California Prop 65. Returns each fact with its official citation URL and last-verified date.
| Name | Type | Req | Description |
|---|---|---|---|
| market | – | – | – |
| subject | string | yes | – |
No output schema declared.
No examples provided.
list_changes ~70
List recall and requirement changes since an ISO-8601 timestamp (e.g. '2026-09-01T00:00:00+00:00'). Includes newly published recalls and rule changes, each with its source URL.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| since | string | yes | – |
No output schema declared.
No examples provided.
search_recalls ~90
Search official US recall records by product name, brand, model, or UPC. Covers CPSC consumer products and FDA food, drug and device enforcement. Returns only cited records from the store, each with a source URL and a match score. If nothing matches, returns an empty list rather than guessing.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| market | string | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
verify ~70
Check a claim or product query against the store. Returns only cited records (recalls and requirements) that match. Explicitly reports 'no verified record' when nothing matches -- it never synthesizes an answer, so absence means 'not in the store', not a negative claim.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
What is the Verity MCP server?
Verity is an MCP server listed in the public MCP registry as io.github.veritylabsai/verity. Cited product-compliance ground truth for AI agents. Never generates; always cites. This page covers its hosted endpoint (https://verity-mcp-243195959173.us-central1.run.app/mcp).
Is the Verity MCP server safe to use?
Verity scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Verity MCP server expose?
Verity exposes 4 tools: search_recalls, get_requirement, list_changes, verify. Their descriptions and schemas cost roughly 332 tokens of context every time the server is loaded.
Does the Verity MCP server require authentication?
No. We connected to Verity without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Verity MCP server still maintained?
Verity is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.