# VERIDEX (remote · mcp.veridexia.es)

Verify Spanish companies by CIF: registry data, status and BORME filings, paid per call over x402.

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.veridexia.es`: 83/100 (this document), [markdown](https://verifymcp.io/servers/es-veridexia-veridex-mcp/mcp.md), [page](https://verifymcp.io/servers/es-veridexia-veridex-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.veridexia.es/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

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

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 639 tokens (~213/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the VERIDEX MCP server?

VERIDEX is a hosted endpoint at https://mcp.veridexia.es/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 es-veridexia-veridex-mcp 'https://mcp.veridexia.es/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "es-veridexia-veridex-mcp": {
      "url": "https://mcp.veridexia.es/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "es-veridexia-veridex-mcp": {
      "type": "http",
      "url": "https://mcp.veridexia.es/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.es-veridexia-veridex-mcp]
url = "https://mcp.veridexia.es/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add es-veridexia-veridex-mcp --url 'https://mcp.veridexia.es/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  es-veridexia-veridex-mcp:
    url: "https://mcp.veridexia.es/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "es-veridexia-veridex-mcp": {
      "Transport": "http",
      "Url": "https://mcp.veridexia.es/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add es-veridexia-veridex-mcp -t streamable-http -u 'https://mcp.veridexia.es/mcp'
```

### Other

```json
{
  "mcpServers": {
    "es-veridexia-veridex-mcp": {
      "type": "http",
      "url": "https://mcp.veridexia.es/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-11-05 (score 83, +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-11-03 (score 82, +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-10-31 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 78, +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-10-23 (score 77, +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.

### 2026-10-21 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `verify_company_by_cif` (~211 tokens)

Verify a Spanish company by CIF

Verify a Spanish company by its CIF and get its registry data, status in the BORME, recent published acts and an explainable 0-100 risk score.

This is an x402-paid endpoint. The first call returns ok=false with error.code='payment_required' and a complete `payment` challenge (price, network, asset, receiving address). Settle that challenge with a wallet you control and call again with the resulting base64 payload in `x_payment`; the same call then returns the company.

Errors are typed: 'not_found' (valid CIF, no record — you are not charged), 'source_unavailable' (upstream registry down — not charged, safe to retry), 'invalid_request' (malformed CIF), 'rate_limited' (quota), 'transport_error' (the API was unreachable). Do not retry a 402 without changing the payment.

Input parameters:

- `cif` (string, required)
- `idempotency_key`
- `x_payment`

Output parameters:

- `cif` (string): The CIF as requested.
- `company`
- `error`
- `guidance` (string): What to do next, in one sentence, for the calling agent.
- `mock` (boolean): True when the facts are synthetic, never true for a real source.
- `ok` (boolean)
- `payment`
- `provenance`
- `recent_acts` (array)
- `risk`

### `get_veridex_info` (~77 tokens)

VERIDEX service information and pricing

Describe the VERIDEX service: what it does, its price, the settlement network and asset, the receiving address and the available endpoints.

Reads the public discovery manifest at /.well-known/x402. Needs no credentials and costs nothing. Call this before verifying if you need to know what a verification costs or where the payment goes.

Output parameters:

- `asset` (string)
- `asset_decimals`
- `asset_symbol` (string)
- `description` (string)
- `endpoints` (array)
- `error`
- `how_to_pay` (string)
- `manifest_version` (string)
- `name` (string)
- `network` (string)
- `ok` (boolean)
- `pay_to` (string)
- `price` (string)
- `raw_manifest` (object)

### `health_check` (~82 tokens)

VERIDEX API health and today's traffic

Check whether the VERIDEX API is up, and see today's demand: uptime, the number of verification calls served today and the distinct callers.

Free and unauthenticated. The request count excludes the service's own healthchecks and local tests, so it answers 'is anyone using this?' rather than 'is the process alive?'. Useful before starting a paid flow.

Output parameters:

- `api_url` (string)
- `checked_at` (string)
- `error`
- `latency_ms`
- `ok` (boolean)
- `reachable` (boolean)
- `requests_today`
- `status` (string): 'ok' when the API is serving.
- `unique_agents_today`
- `uptime_seconds`

## Diagnostics

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

## Score history

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

## Common questions

### What is the VERIDEX MCP server?

VERIDEX is an MCP server listed in the public MCP registry as es.veridexia/veridex-mcp. Verify Spanish companies by CIF: registry data, status and BORME filings, paid per call over x402. This page covers its hosted endpoint (https://mcp.veridexia.es/mcp).

### Is the VERIDEX MCP server safe to use?

VERIDEX scores 83 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 VERIDEX MCP server expose?

VERIDEX exposes 3 tools: verify_company_by_cif, get_veridex_info, health_check. Their descriptions and schemas cost roughly 370 tokens of context every time the server is loaded.

### Does the VERIDEX MCP server require authentication?

No. We connected to VERIDEX without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the VERIDEX MCP server still maintained?

VERIDEX is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the VERIDEX MCP server?

VerifyMCP ran 13 checks on VERIDEX, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.veridexia.es/mcp
- Repository: https://github.com/Habib4862/veridex-mcp
- Website: https://veridexia.es/
- Changelog RSS feed: https://verifymcp.io/servers/es-veridexia-veridex-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/es-veridexia-veridex-mcp/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/es-veridexia-veridex-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/es-veridexia-veridex-mcp/mcp