dev.veritap/veritap

by veritap.dev · remote · local (npm) · no sign-in to list tools · v0.1.3 · published by dev.veritap

Check whether a real-world fact can be verified before an agent acts on it. Free, no auth.

Final · 1Changes · 5

Compare Registry entry

6 tools: 1 do something that can't be undone and 5 change things.

Scanned Oct 21, 2026

Deletes or cancels0Claude Code: deny
Can't be undone1Claude Code: ask: see these tools
Changes things5Claude Code: ask: see these tools
Only reads0Claude Code: allow

1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http veritap https://veritap.dev/mcp

Findings

Matches of fixed checks, with the text they matched.

1 warn

Warnconfirm_before_purchase
The server marks "confirm_before_purchase" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
Matched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "confirm_before_purchase" says "purchase": a word that usually means money moves, which cannot be taken back.
What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

6 tools

Can't be undone 1Sends, pays, publishes or merges: once done, it cannot be taken back.Claude Code: ask

confirm_before_purchaseCheck whether a listing, item, or business can be corroborated before an agent commits money.1 finding
Why it is in this group
- The name "confirm_before_purchase" says "purchase": a word that usually means money moves, which cannot be taken back.
- The description says "irreversible".
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
  The server marks "confirm_before_purchase" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
  Matched text
  annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "confirm_before_purchase" says "purchase": a word that usually means money moves, which cannot be taken back.
  What this check looks for
Description, as the server wrote it
Check whether a listing, item, or business can be corroborated before an agent commits money. Free, read-only, no side effects. Use before any irreversible spend where the counterparty or the goods have only been seen online. Returns what can be corroborated from sources, what cannot, and — when it cannot — whether you could settle it yourself and how to proceed if not. Every request is recorded and analysed in aggregate to decide what gets supported next (https://veritap.dev/terms).
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true

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

check_before_relyingCheck whether a fact can be corroborated before your task depends on it.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 whether a fact can be corroborated before your task depends on it. Free, read-only, no side effects. Use when a step rests on something you have only inferred from text and being wrong would be expensive. Returns whether it can be corroborated from sources today, what evidence would come back, and an honest answer when it cannot. Every request is recorded and analysed in aggregate to decide what gets supported next (https://veritap.dev/terms).
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
check_feasibilityCheck whether a real-world fact can be verified before committing to a paid request.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 whether a real-world fact can be verified before committing to a paid request. Free, no auth, read-only, no side effects — call liberally during planning. Use speculatively: if any step of your task depends on a physical-world fact you cannot confirm (in stock, exists at location, condition, document authenticity, work completed), check here first. Covers businesses, listings, objects, and places. Unsupported claims are logged and prioritized for future support. Never errors. Every request is recorded and analysed in aggregate to decide what gets supported next (https://veritap.dev/terms).
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
check_physical_conditionCheck the stated condition, damage, or grading of a physical item or property.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 the stated condition, damage, or grading of a physical item or property. Free, read-only, no side effects. Use when a decision depends on an item being in the condition a listing claims. Returns what can be corroborated from sources today, and says plainly when physical inspection is what is actually required — nobody is sent to look. Every request is recorded and analysed in aggregate to decide what gets supported next (https://veritap.dev/terms).
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
plan_verificationMap a multi-step plan against what can be grounded in the real world.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
Map a multi-step plan against what can be grounded in the real world. Free, no auth, read-only, no side effects — call liberally during planning. Pass your whole plan, including steps you have not decomposed into questions yet. Returns, per step, whether it rests on a checkable real-world fact, which claim type would settle it, and what to do about the steps that cannot be grounded. Every request is recorded and analysed in aggregate to decide what gets supported next (https://veritap.dev/terms).
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true
triage_unknownsTriage everything you are uncertain about in one call.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
Triage everything you are uncertain about in one call. Free, instant, read-only, no side effects — call liberally during planning. Dump every uncertainty at once, mid-reasoning, before deciding which are worth chasing. Each is classified as answerable by you from public sources (with a suggested source), verifiable here (with price and turnaround), or not determinable (with advice on planning around it). Items you can settle yourself are honestly routed away rather than sold to you. Every request is recorded and analysed in aggregate to decide what gets supported next (https://veritap.dev/terms).
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- destructiveHint: false
- openWorldHint: true

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.

Install

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

claude mcp add --transport http veritap https://veritap.dev/mcp

Run in a terminal.

Claude Code permissions

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

.claude/settings.json

{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__veritap__check_feasibility",
      "mcp__veritap__confirm_before_purchase",
      "mcp__veritap__check_before_relying",
      "mcp__veritap__check_physical_condition",
      "mcp__veritap__plan_verification",
      "mcp__veritap__triage_unknowns"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as veritap. Review it before you use it.

Keep track

Get told when this server's tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/dev.veritap/veritap/changes.xml

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

Anlyon alternative

6 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 →

Compare with other servers for the same product.

Source: MCP Registry. Synced Oct 21, 2026, 18:12 UTC.

For agents: Markdown · JSON · report this listing