Skip to content

VERIDEX

by veridexia.es · remote · no sign-in to list tools · v0.1.1 · published by es.veridexia

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

Changes · 2
CompareRegistry entry

3 tools: 2 change things and 1 only read.

Scanned Oct 21, 2026

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

claude mcp add --transport http veridex https://mcp.veridexia.es/mcp

Findings

Matches of fixed checks, with the text they matched.

1 info

Tools

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

3 tools

Changes things 2Claude Code: ask
  • health_checkCheck whether the VERIDEX API is up, and see today's demand: uptime, the number of verification calls served today and the distinct callers.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 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • verify_company_by_cifVerify 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.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.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 1Claude Code: allow
  • get_veridex_infoDescribe the VERIDEX service: what it does, its price, the settlement network and asset, the receiving address and the available endpoints.1 finding

    Why it is in this group

    • The name "get_veridex_info" says "get": a word for reading.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...manifest at /.well-known/x402. Needs no credentials and costs nothing. Call this before ver..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • 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.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http veridex https://mcp.veridexia.es/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": [
      "mcp__veridex__get_veridex_info"
    ],
    "ask": [
      "mcp__veridex__verify_company_by_cif",
      "mcp__veridex__health_check"
    ],
    "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 veridex. Review it before you use it.