veritap MCP server
dev.veritap/veritapveritap.devstreamable-httpv0.1.3Scanned
Check whether a real-world fact can be verified before an agent acts on it. Free, no auth.
6 tools: 1 do something that can't be undone and 5 change things.
- Reads private data · 0
- Reads text others write · 6
- Can send data out · 4
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the veritap MCP server can do
The veritap MCP server is published by veritap.dev, a domain the MCP Registry verified. It has 6 tools. It can do things that cannot be undone, such as sending, paying or publishing (confirm_before_purchase) and create or change data (5 tools: check_feasibility, check_before_relying, check_physical_condition, plan_verification and 1 more), but cannot delete data. None of its tools only reads.
6 tools bring in text other people can write (check_feasibility, confirm_before_purchase, check_before_relying and 3 more); 4 tools can send data out of your system (check_feasibility, confirm_before_purchase, check_before_relying and 1 more).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 17, 2026, version 0.1.3.
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.
6 tools
Can't be undone 1Claude Code: ask
confirm_before_purchaseCheck whether a listing, item, or business can be corroborated before an agent commits money.Reads text others writeCan send data out1 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.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.callback_url): a request to a URL can carry data to whoever runs it.
Findings
- Warn
The server marks "confirm_before_purchase" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched 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.
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 5Claude Code: ask
check_before_relyingCheck whether a fact can be corroborated before your task depends on it.Reads text others writeCan send data outNo 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.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.callback_url): a request to a URL can carry data to whoever runs it.
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.Reads text others writeCan send data outNo 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.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.callback_url): a request to a URL can carry data to whoever runs it.
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.Reads text others writeCan send data outNo 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.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.callback_url): a request to a URL can carry data to whoever runs it.
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.Reads text others writeNo 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.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
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.Reads text others writeNo 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.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
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.
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.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write6
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out4
- 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.
Looked at Nov 20, 2026, 19:22 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
- 6
- 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
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (1 irreversible, 5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://veritap.dev/mcp: tools/list returned 6 tools to an anonymous client, including confirm_before_purchase (irreversible), check_feasibility (write), check_before_relying (write), check_physical_condition (write), plan_verification (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
The server marks "confirm_before_purchase" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched 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.
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.
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/mcpclaude mcp add --transport http veritap https://veritap.dev/mcpRun 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.
{
"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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as veritap. Review it before you use it.
Capability tags behind 6 rules
- mcp__veritap__check_feasibility untrusted-input, outbound
- mcp__veritap__confirm_before_purchase untrusted-input, outbound
- mcp__veritap__check_before_relying untrusted-input, outbound
- mcp__veritap__check_physical_condition untrusted-input, outbound
- mcp__veritap__plan_verification untrusted-input
- mcp__veritap__triage_unknowns untrusted-input
Pin
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://radar.anlyon.com/api/v1/servers/dev.veritap/veritap/verify?hash=1587501f0cddf4e40b0b783f70df0abff1cb396e016f7694f789dbfbe006ab00" | jq -e '.changed == false'Pinned hash 1587501f0cdd, from Nov 17, 2026, 04:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.veritap/veritap/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.veritap/veritap)Source: MCP Registry. Synced Oct 21, 2026, 18:12 UTC.
veritap MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the veritap MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 6 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the veritap MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the veritap MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: confirm_before_purchase.
What tools does the veritap MCP server have?
- 6 tools: 1 irreversible, 5 write. confirm_before_purchase, check_feasibility, check_before_relying, check_physical_condition, plan_verification and triage_unknowns.
Does the veritap MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the veritap MCP server send data to outside services?
- 4 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_feasibility, confirm_before_purchase, check_before_relying and check_physical_condition.
Has the veritap MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.