# dev.veritap/veritap (remote · veritap.dev)

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

- Trust score: 79/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `veritap.dev`: 79/100 (this document), [markdown](https://verifymcp.io/servers/dev-veritap-veritap/veritap.md), [page](https://verifymcp.io/servers/dev-veritap-veritap/veritap)
- npm · `veritap-mcp`: 34/100, [markdown](https://verifymcp.io/servers/dev-veritap-veritap/veritap-mcp.md), [page](https://verifymcp.io/servers/dev-veritap-veritap/veritap-mcp)

## Channel facts

- Endpoint: `https://veritap.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "dev-veritap-veritap": {
      "url": "https://veritap.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-veritap-veritap": {
      "type": "http",
      "url": "https://veritap.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-veritap-veritap]
url = "https://veritap.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-veritap-veritap": {
      "type": "remote",
      "url": "https://veritap.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-veritap-veritap --url 'https://veritap.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-veritap-veritap:
    url: "https://veritap.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-veritap-veritap": {
      "Transport": "http",
      "Url": "https://veritap.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-veritap-veritap -t streamable-http -u 'https://veritap.dev/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-11 (score 79, +1)

- [security] Stability: 0.97 → pass

### 2026-09-09 (score 78, +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.

### 2026-09-07 (score 77, +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.

### 2026-09-05 (score 76, +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.

### 2026-09-03 (score 75, +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.

### 2026-09-01 (score 74, +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.

### 2026-08-29 (score 73, +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.

### 2026-08-27 (score 72, +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.

## MCP tools (6)

### `check_feasibility` (~328 tokens)

Check whether a real-world fact can be verified

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).

Input parameters:

- `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, required): 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.

### `confirm_before_purchase` (~307 tokens)

Confirm a listing or seller is real before spending money

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).

Input parameters:

- `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, required): 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.

### `check_before_relying` (~300 tokens)

Check a fact before relying on 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).

Input parameters:

- `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, required): 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.

### `check_physical_condition` (~300 tokens)

Check the condition or grading of a physical item

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).

Input parameters:

- `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, required): 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.

### `plan_verification` (~144 tokens)

Map which steps of a plan depend on unverified real-world facts

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).

Input parameters:

- `goal` (string, required): What the overall plan is trying to achieve.
- `steps` (array, required): The plan, in order.

### `triage_unknowns` (~201 tokens)

Triage a batch of uncertainties into answerable, verifiable, or neither

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).

Input parameters:

- `downstream_action` (string): What resolving these would let you do.
- `task_context` (string): What you are trying to accomplish.
- `unknowns` (array, required): 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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-veritap-veritap/veritap#diagnostics

## Score history

- 2026-09-24: 79
- 2026-09-23: 79
- 2026-09-22: 79
- 2026-09-21: 79
- 2026-09-20: 79
- 2026-09-19: 79
- 2026-09-18: 79
- 2026-09-17: 79
- 2026-09-16: 79
- 2026-09-15: 79
- 2026-09-14: 79
- 2026-09-13: 79
- 2026-09-12: 79
- 2026-09-11: 79
- 2026-09-10: 78
- 2026-09-09: 78
- 2026-09-08: 77
- 2026-09-07: 77
- 2026-09-06: 76
- 2026-09-05: 76
- 2026-09-04: 75
- 2026-09-03: 75
- 2026-09-02: 74
- 2026-09-01: 74
- 2026-08-31: 73
- 2026-08-30: 73
- 2026-08-29: 73
- 2026-08-28: 72
- 2026-08-27: 72
- 2026-08-26: 71

## Common questions

### 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.

## Links

- Remote endpoint: https://veritap.dev/mcp
- Website: https://veritap.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-veritap-veritap/veritap.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-veritap-veritap/veritap.json
- HTML version of this page: https://verifymcp.io/servers/dev-veritap-veritap/veritap