Verity

io.github.veritylabsai/verityveritylabsaistreamable-httpv0.2.0Scanned 23 hours ago

Cited product-compliance ground truth for AI agents. Never generates; always cites.

4 tools: 1 change things and 3 only read.

Reads private data · 0
Reads text others write · 0
Can send data out · 0
No findings

Tools listed without sign-in. Remote posture

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 1Creates or changes something that can be changed back.Claude Code: ask

verifyCheck a claim or product query against the store.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- readOnlyHint: true
- title: Verify a claim

Only reads 3Looks things up and changes nothing.Show 3 read-only tools

get_requirementGet cited market-entry requirements for a product subject in a given market (e.g.No findings
Why it is in this group
- The name "get_requirement" says "get": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- readOnlyHint: true
- title: Get requirement
list_changesList recall and requirement changes since an ISO-8601 timestamp (e.g.No findings
Why it is in this group
- The name "list_changes" says "list": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- readOnlyHint: true
- title: List changes
search_recallsSearch official US recall records by product name, brand, model, or UPC.No findings
Why it is in this group
- The name "search_recalls" says "search": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- readOnlyHint: true
- title: Search recalls

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0: Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0: Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0: Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Oct 22, 2026, 15:25 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable: yes
HTTP status of an anonymous initialize: 200
tools/list served without credentials: yes
Tools that change things, listed without credentials: 1
Protocol version: 2025-06-18
WWW-Authenticate on 401: not observed
resource_metadata in WWW-Authenticate: not observed
RFC 9728 protected resource metadata: not observed
Authorization servers: not observed
Legacy HTTP+SSE transport: no
Dynamic client registration: not observed
Client ID metadata documents: not observed

WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
Matched text
https://verity-mcp-243195959173.us-central1.run.app/mcp: tools/list returned 4 tools to an anonymous client, including verify (write)
What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

All changes to this server

Install

Pinned to version 0.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http verity https://verity-mcp-243195959173.us-central1.run.app/mcp

claude mcp add --transport http verity https://verity-mcp-243195959173.us-central1.run.app/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__verity__search_recalls",
      "mcp__verity__get_requirement",
      "mcp__verity__list_changes"
    ],
    "ask": [
      "mcp__verity__verify"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as verity. Review it before you use it.

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/io.github.veritylabsai/verity/verify?hash=3982b6400f3237e2f434a20df36a6ecb61aedfb8a7573ce6f95a817bd786f6fb" | jq -e '.changed == false'

Pinned hash 3982b6400f32, from Oct 21, 2026, 19:34 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.github.veritylabsai/verity/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

[![anlyon.dev](https://anlyon.dev/badge/io.github.veritylabsai/verity.svg)](https://anlyon.dev/servers/io.github.veritylabsai/verity)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:51 UTC.