dev.veritap/veritap
REMOTE · VERITAP.DEV · 2 COMPONENTS · SCANNED SEP 24
Check whether a real-world fact can be verified before an agent acts on it. Free, no auth.
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 Security63
- 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1857 tokens (~309/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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 dev.veritap/veritap MCP server?
dev.veritap/veritap is a hosted endpoint at https://veritap.dev/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 · veritap.dev
claude mcp add --transport http dev-veritap-veritap 'https://veritap.dev/mcp'
{
"mcpServers": {
"dev-veritap-veritap": {
"url": "https://veritap.dev/mcp"
}
}
} {
"servers": {
"dev-veritap-veritap": {
"type": "http",
"url": "https://veritap.dev/mcp"
}
}
} [mcp_servers.dev-veritap-veritap] url = "https://veritap.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-veritap-veritap": {
"type": "remote",
"url": "https://veritap.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-veritap-veritap --url 'https://veritap.dev/mcp' --transport streamable-http
mcp_servers:
dev-veritap-veritap:
url: "https://veritap.dev/mcp" {
"McpServers": {
"dev-veritap-veritap": {
"Transport": "http",
"Url": "https://veritap.dev/mcp"
}
}
} assistant mcp add dev-veritap-veritap -t streamable-http -u 'https://veritap.dev/mcp'
{
"mcpServers": {
"dev-veritap-veritap": {
"type": "http",
"url": "https://veritap.dev/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.
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
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 24 Sept 2026 · Probed https://veritap.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=veritap.dev | CN=WE1,O=Google Trust Services,C=US | 17 Aug 2026 | 15 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 84b5d0f466d0643e0edf236e71cab611 |
| SANs: veritap.dev, verify.veritap.dev, *.verify.veritap.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of veritap.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| veritap.dev. | 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://veritap.dev/mcp | Verified | 200 | |
| http (plaintext) | http://veritap.dev/mcp | Inconclusive | 405 |
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 →
check_before_relying Check a fact before relying on it ~300
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).
| Name | Type | Req | Description |
|---|---|---|---|
| budget_ceiling_usd | number | – | Most you would pay for this answer. Directly drives what gets built next. |
| callback_url | string | – | Optional. If this claim is not supported yet, POST here when it becomes supported. Otherwise you are told on your next call. |
| claim_description | string | yes | Free text. The real-world fact you need settled. Required. |
| claim_type | string | – | Optional. A claim type id from the published catalog, if you know it. |
| cost_if_wrong | – | – | What happens to your task if this fact is wrong: "blocks_task", "degrades_answer", or "cosmetic". |
| deadline | string | – | ISO8601. When the answer stops being useful. |
| downstream_action | string | – | What you will do with the answer once you have it. |
| location | object | – | Where the fact must be checked. |
| task_context | string | – | The wider task this step belongs to. |
No output schema declared.
No examples provided.
check_feasibility Check whether a real-world fact can be verified ~328
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).
| Name | Type | Req | Description |
|---|---|---|---|
| budget_ceiling_usd | number | – | Most you would pay for this answer. Directly drives what gets built next. |
| callback_url | string | – | Optional. If this claim is not supported yet, POST here when it becomes supported. Otherwise you are told on your next call. |
| claim_description | string | yes | Free text. The real-world fact you need settled. Required. |
| claim_type | string | – | Optional. A claim type id from the published catalog, if you know it. |
| cost_if_wrong | – | – | What happens to your task if this fact is wrong: "blocks_task", "degrades_answer", or "cosmetic". |
| deadline | string | – | ISO8601. When the answer stops being useful. |
| downstream_action | string | – | What you will do with the answer once you have it. |
| location | object | – | Where the fact must be checked. |
| task_context | string | – | The wider task this step belongs to. |
No output schema declared.
No examples provided.
check_physical_condition Check the condition or grading of a physical item ~300
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).
| Name | Type | Req | Description |
|---|---|---|---|
| budget_ceiling_usd | number | – | Most you would pay for this answer. Directly drives what gets built next. |
| callback_url | string | – | Optional. If this claim is not supported yet, POST here when it becomes supported. Otherwise you are told on your next call. |
| claim_description | string | yes | Free text. The real-world fact you need settled. Required. |
| claim_type | string | – | Optional. A claim type id from the published catalog, if you know it. |
| cost_if_wrong | – | – | What happens to your task if this fact is wrong: "blocks_task", "degrades_answer", or "cosmetic". |
| deadline | string | – | ISO8601. When the answer stops being useful. |
| downstream_action | string | – | What you will do with the answer once you have it. |
| location | object | – | Where the fact must be checked. |
| task_context | string | – | The wider task this step belongs to. |
No output schema declared.
No examples provided.
confirm_before_purchase Confirm a listing or seller is real before spending money ~307
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).
| Name | Type | Req | Description |
|---|---|---|---|
| budget_ceiling_usd | number | – | Most you would pay for this answer. Directly drives what gets built next. |
| callback_url | string | – | Optional. If this claim is not supported yet, POST here when it becomes supported. Otherwise you are told on your next call. |
| claim_description | string | yes | Free text. The real-world fact you need settled. Required. |
| claim_type | string | – | Optional. A claim type id from the published catalog, if you know it. |
| cost_if_wrong | – | – | What happens to your task if this fact is wrong: "blocks_task", "degrades_answer", or "cosmetic". |
| deadline | string | – | ISO8601. When the answer stops being useful. |
| downstream_action | string | – | What you will do with the answer once you have it. |
| location | object | – | Where the fact must be checked. |
| task_context | string | – | The wider task this step belongs to. |
No output schema declared.
No examples provided.
plan_verification Map which steps of a plan depend on unverified real-world facts ~144
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).
| Name | Type | Req | Description |
|---|---|---|---|
| goal | string | yes | What the overall plan is trying to achieve. |
| steps | array | yes | The plan, in order. |
No output schema declared.
No examples provided.
triage_unknowns Triage a batch of uncertainties into answerable, verifiable, or neither ~201
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).
| Name | Type | Req | Description |
|---|---|---|---|
| downstream_action | string | – | What resolving these would let you do. |
| task_context | string | – | What you are trying to accomplish. |
| unknowns | array | yes | Every uncertainty in the task. Batch them — this is one call. Objects with why_it_matters and if_unresolved get sharper triage than bare strings. |
No output schema declared.
No examples provided.
What is the dev.veritap/veritap MCP server?
dev.veritap/veritap is an MCP server listed in the public MCP registry as dev.veritap/veritap. Check whether a real-world fact can be verified before an agent acts on it. Free, no auth. This page covers its hosted endpoint (https://veritap.dev/mcp).
Is the dev.veritap/veritap MCP server safe to use?
dev.veritap/veritap scores 79 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 dev.veritap/veritap MCP server expose?
dev.veritap/veritap exposes 6 tools: check_feasibility, confirm_before_purchase, check_before_relying, check_physical_condition, plan_verification, triage_unknowns. Their descriptions and schemas cost roughly 1,580 tokens of context every time the server is loaded.
Does the dev.veritap/veritap MCP server require authentication?
No. We connected to dev.veritap/veritap without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the dev.veritap/veritap MCP server still maintained?
dev.veritap/veritap is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.