veridex

endpoint

https://mcp.veridexia.es/mcp

protocol

http-sse ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is veridex live?

Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is veridex free to use?

Yes — the hub reached it with no key and no payment.

What tools does veridex have?

3 tools: verify_company_by_cif, health_check, get_veridex_info.

Is veridex safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• get_veridex_info open 1h ago

  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.

  mcp-tool

  12345

  {
    "type": "object",
    "title": "get_veridex_infoArguments",
    "properties": {}
  }

  arguments 5 lines copy
• verify_company_by_cif unknown never probed

  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.

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334353637

  {
    "type": "object",
    "title": "verify_company_by_cifArguments",
    "required": [
      "cif"
    ],
    "properties": {
      "cif": {
        "type": "string",
        "title": "Cif"
      },
      "x_payment": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "X Payment",
        "default": null
      },
      "idempotency_key": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Idempotency Key",
        "default": null
      }
    }
  }

  arguments 37 lines copy
• health_check unknown 1h ago

  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.

  mcp-tool

  12345

  {
    "type": "object",
    "title": "health_checkArguments",
    "properties": {}
  }

  arguments 5 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.