# carrierone/verilexdata-mcp [Health: Active]

**Category:** 📊 Data Platforms  
**Repository:** https://github.com/carrierone/verilexdata-mcp  
**GitHub Stars:** 1  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/carrierone-verilexdata-mcp

## Description
20 structured datasets (NPI healthcare, SEC filings, OFAC sanctions, crypto whales, Polymarket signals, patents, economic indicators) via x402 pay-per-query with USDC. Free stats/sample endpoints, MCP + HTTP transport.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "verilexdata-mcp": {
    "command": "npx",
    "args": ["-y","github:carrierone/verilexdata-mcp"],
    "env": {
      "VERILEX_API_URL": "",
      "VERILEX_PAYMENT_TOKEN": ""
    }
  }
}
```

**Requires environment variables:** `VERILEX_API_URL`, `VERILEX_PAYMENT_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What carrierone/verilexdata-mcp MCP server does

The carrierone/verilexdata-mcp MCP server connects AI agents to Verilex Data’s collection of structured datasets. The repository describes 20 datasets spanning government and business information, crypto intelligence, and prediction markets. Available data areas include NPI healthcare providers, SEC filings, NOAA weather observations, federal court metadata, patents, government contracts, economic indicators, OFAC sanctions, wallet activity, token holders, DEX trades, and Polymarket signals.

The dataset catalog also includes cross-dataset company intelligence, OTC company analytics, liquidation signals, wallet labels, and several prediction-market views. Trademarks are listed as coming soon, so they should not be treated as an available dataset based on the repository description alone.

## How it works

An MCP-compatible client runs the server with Node’s package runner and communicates with it through the Model Context Protocol. The project also describes HTTP transport, allowing the service to work with Verilex Data’s API-oriented access model. The README specifically provides a local stdio configuration for MCP clients.

Free statistics and sample endpoints can be called without payment. Paid endpoints respond with HTTP 402 payment requirements and use the x402 protocol for USDC payments on Base. The payment token is supplied through an environment variable rather than being embedded in the client configuration.

High-frequency datasets support queries with a `since` ISO 8601 timestamp. These change-feed requests return records updated after the supplied time, which can reduce repeated retrieval when an agent polls for updates. Paid responses include headers indicating whether data is stale, when it was last updated, and the data age in seconds.

## Setup and configuration

Add the server to an MCP client configuration using the repository command shown in the README:

```json
{
  "mcpServers": {
    "verilex": {
      "command": "npx",
      "args": ["-y", "github:carrierone/verilexdata-mcp"]
    }
  }
}
```

The documented clients include Claude Desktop, VS Code, and Cursor. The API base URL defaults to `https://api.verilexdata.com`; set `VERILEX_API_URL` only when a different API base is needed. Set `VERILEX_PAYMENT_TOKEN` to provide the x402 payment token for paid endpoints. Free statistics and sample requests do not require payment.

## Tools and capabilities

The carrierone/verilexdata-mcp MCP server supports these data-access capabilities:

- Query structured government and business datasets, including NPI, SEC, PACER, patents, contracts, and economic indicators.
- Retrieve crypto intelligence covering sanctions, wallet balances, address attribution, token holders, liquidations, and decentralized-exchange trades.
- Query prediction-market signals, arbitrage data, resolution sources, and market microstructure.
- Poll supported high-frequency datasets using timestamp-based change feeds.
- Inspect freshness information from response headers on paid requests.
- Use free statistics and sample endpoints before configuring paid access.

## Limitations and notes

Access to paid data is usage-based and requires x402 payment in USDC on Base. The repository does not provide a general list of per-query prices, so cost should be checked in Verilex Data’s documentation before production use. Free endpoints are limited to statistics and samples as described in the README.

Data freshness is exposed through response headers rather than presented as a universal fixed update interval. The listed SEC filing dataset is updated every 15 minutes, while other datasets may have different freshness characteristics. The repository also identifies Trademarks as coming soon, so availability may change independently of the MCP wrapper.

The project is released under the MIT license. Its documented configuration uses a GitHub repository reference with `npx`, so the client must be able to run that command and access the package source.

_Full upstream README: https://allmcps.com/mcp/carrierone-verilexdata-mcp/readme_