API Tools
vextorium.com
MCP server that lets agents search, inspect, and call Vextorium's catalog of paid data services via API.
ENDPOINT 1
https://api.vextorium.com/mcp
MCP server metadata
- Name
- vextorium
- Version
- 1.0.0
Vextorium: 507 pay-per-call data services for AI agents (on-chain data on 30+ chains, DeFi, markets, official statistics, compliance, web and developer tools). Use search_services to find a service, service_details to see its inputs and price, then call_service to run it (paid per call in USDC via x402; failed calls are not charged).
Known tools 3
search_servicesSearch the Vextorium catalog of 507 paid data services by keywords (e.
Inferred read-onlyservice_detailsDetails of one Vextorium service: what it does, its price in USDC, the JSON input it accepts (schema) and an example.
Inferred read-onlycall_serviceRun any Vextorium service with its parameters and get the JSON result.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.vextorium]
url = "https://api.vextorium.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"vextorium": {
"type": "http",
"url": "https://api.vextorium.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: vextorium
Remote MCP URL: https://api.vextorium.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"vextorium": {
"url": "https://api.vextorium.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"vextorium": {
"type": "http",
"url": "https://api.vextorium.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "vextorium",
"transport": "streamable-http",
"url": "https://api.vextorium.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.