# Vextorium (remote · api.vextorium.com)

200+ pay-per-call APIs for AI agents via x402: on-chain data, DeFi, markets and compliance.

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

## Components

- remote · `api.vextorium.com`: 87/100 (this document), [markdown](https://verifymcp.io/servers/com-vextorium-api-vextorium/api.md), [page](https://verifymcp.io/servers/com-vextorium-api-vextorium/api)

## Channel facts

- Endpoint: `https://api.vextorium.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.7`

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

- **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**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 378 tokens (~94/item across 4 items; 4 tools + 0 resources), lean.
  - 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Vextorium MCP server?

Vextorium is a hosted endpoint at https://api.vextorium.com/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 com-vextorium-api-vextorium 'https://api.vextorium.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-vextorium-api-vextorium": {
      "url": "https://api.vextorium.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-vextorium-api-vextorium": {
      "type": "http",
      "url": "https://api.vextorium.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-vextorium-api-vextorium]
url = "https://api.vextorium.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-vextorium-api-vextorium --url 'https://api.vextorium.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-vextorium-api-vextorium:
    url: "https://api.vextorium.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-vextorium-api-vextorium": {
      "Transport": "http",
      "Url": "https://api.vextorium.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-vextorium-api-vextorium -t streamable-http -u 'https://api.vextorium.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-vextorium-api-vextorium": {
      "type": "http",
      "url": "https://api.vextorium.com/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-06 (score 87, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-04 (score 87, +1)

- [functional improvement] Tool coverage: 80% → 100%
- [cosmetic] “search_services” reworded the description of “limit”

### 2026-11-03 (score 86, +14)

- [security improvement] Stability: fail → pass

### 2026-10-28 (score 72, +49)

- [security regression] Stability: unverified → fail
- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] HSTS header: fail → pass
- [security improvement] Transport: fail → pass
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass

### 2026-10-27 (score 23, −49)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: fail → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [security regression] HSTS header: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-21 (score 72, −1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “search_services” rewrote its description, which is the text the model reads
- [cosmetic] “call_service” reworded the description of “service”
- [cosmetic] “service_details” reworded the description of “service”

### 2026-10-17 (score 73, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “search_services” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 98 → 109
- [functional] Schema quality: excellent → good

### 2026-10-16 (score 73, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “search_services” rewrote its description, which is the text the model reads

## MCP tools (4)

### `current_date` (~28 tokens)

Get the current date and local time in Europe/Madrid. Free; evaluated live for every call.

### `search_services` (~81 tokens)

Search the Vextorium catalog of 242 paid data services by keywords (e.g. 'crypto price', 'sanctions', 'ECB rates', 'earthquakes'). Free. Returns service ids, descriptions and prices.

Input parameters:

- `limit` (integer): Maximum matches to return (1-30; defaults to 10).
- `query` (string, required): Keywords

### `service_details` (~59 tokens)

Details of one Vextorium service: what it does, its price in USDC, the JSON input it accepts (schema) and an example. Free.

Input parameters:

- `service` (string, required): Service id from search_services, e.g. 'crypto-price'

### `call_service` (~83 tokens)

Run any Vextorium service with its parameters and get the JSON result. Paid per call in USDC via x402 (price shown by service_details); invalid input or a failed upstream source is not charged.

Input parameters:

- `params` (object): JSON input of the service (see service_details)
- `service` (string, required): Service id, e.g. 'iban-validate'

## Diagnostics

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

## Score history

- 2026-11-07: 87
- 2026-11-06: 87
- 2026-11-05: 87
- 2026-11-04: 87
- 2026-11-03: 86
- 2026-11-02: 72
- 2026-11-01: 72
- 2026-10-31: 72
- 2026-10-30: 72
- 2026-10-29: 72
- 2026-10-28: 72
- 2026-10-27: 23
- 2026-10-26: 72
- 2026-10-25: 72
- 2026-10-24: 72
- 2026-10-23: 72
- 2026-10-22: 72
- 2026-10-21: 72
- 2026-10-20: 73
- 2026-10-19: 73
- 2026-10-18: 73
- 2026-10-17: 73
- 2026-10-16: 73
- 2026-10-15: 73
- 2026-10-14: 73
- 2026-10-13: 73
- 2026-10-12: 73
- 2026-10-10: 73
- 2026-10-08: 67
- 2026-10-04: 67

## Common questions

### What is the Vextorium MCP server?

Vextorium is an MCP server listed in the public MCP registry as com.vextorium.api/vextorium. 200+ pay-per-call APIs for AI agents via x402: on-chain data, DeFi, markets and compliance. This page covers its hosted endpoint (https://api.vextorium.com/mcp).

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

Vextorium scores 87 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 Vextorium MCP server expose?

Vextorium exposes 4 tools: current_date, search_services, service_details, call_service. Their descriptions and schemas cost roughly 251 tokens of context every time the server is loaded.

### Does the Vextorium MCP server require authentication?

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

### Is the Vextorium MCP server still maintained?

Vextorium is still listed as active in the MCP registry. We last reached this channel on 7 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 Vextorium MCP server?

VerifyMCP ran 13 checks on Vextorium, 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://api.vextorium.com/mcp
- Repository: https://github.com/bru1noia/vextorium-mcp
- Website: https://vextorium.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-vextorium-api-vextorium/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-vextorium-api-vextorium/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-vextorium-api-vextorium/api.json
- HTML version of this page: https://verifymcp.io/servers/com-vextorium-api-vextorium/api