# Dataville (npm · @dataville/dataville-mcp)

SEC filings, Wikipedia, arXiv, US Census and more for AI agents, with every answer source-linked.

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

## Components

- remote · `api.dataville.com`: 80/100, [markdown](https://verifymcp.io/servers/com-dataville-dataville-mcp/api.md), [page](https://verifymcp.io/servers/com-dataville-dataville-mcp/api)
- npm · `@dataville/dataville-mcp`: 91/100 (this document), [markdown](https://verifymcp.io/servers/com-dataville-dataville-mcp/dataville-dataville-mcp.md), [page](https://verifymcp.io/servers/com-dataville-dataville-mcp/dataville-dataville-mcp)

## Channel facts

- Registry: `npm`
- Package: `@dataville/dataville-mcp`
- Version: `0.1.8`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-05.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to datavilleorg/dataville-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 23 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 660 tokens (~165/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 Dataville MCP server?

Dataville runs locally as an npm package, launched with npx -y @dataville/dataville-mcp. 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 com-dataville-dataville-mcp -- npx -y @dataville/dataville-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-dataville-dataville-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@dataville/dataville-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-dataville-dataville-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@dataville/dataville-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-dataville-dataville-mcp -- npx -y @dataville/dataville-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-dataville-dataville-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@dataville/dataville-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-dataville-dataville-mcp --command npx --arg -y --arg @dataville/dataville-mcp
```

### Hermes

```yaml
mcp_servers:
  com-dataville-dataville-mcp:
    command: "npx"
    args: ["-y", "@dataville/dataville-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-dataville-dataville-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@dataville/dataville-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-dataville-dataville-mcp -t stdio -c npx -a -y @dataville/dataville-mcp
```

### Other

```json
{
  "mcpServers": {
    "com-dataville-dataville-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@dataville/dataville-mcp"
      ]
    }
  }
}
```

## 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-05 (score 91, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 90, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 89, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 84, +3)

- [functional improvement] Stability: unverified → 0.27

## MCP tools (4)

### `list_dataville_sources` (~53 tokens)

List Dataville data sources

List every Dataville data source with a one-line description and the SQL tables (if any) that query_dataville can read for it. Call describe_dataville_source for a source's keyword format and table columns.

### `describe_dataville_source` (~79 tokens)

Describe a Dataville data source

Show how to use one data source: what search_dataville expects as keywords (with an example that returns a result), and the SQL tables and columns query_dataville can read for it. Sources with no tables can only be searched.

Input parameters:

- `source` (string, required): Data source name from list_dataville_sources, e.g. 'edgar'

### `search_dataville` (~175 tokens)

Search a Dataville data source

Look up one thing in a Dataville data source by keywords and get back the single best-matching record (full text in `body`, structured fields in `metadata`). Use describe_dataville_source to see what keywords a source expects. To get many records, filter, or page through results, use query_dataville instead.

Input parameters:

- `keywords` (string, required): Search keywords or identifier, e.g. a title, ticker, or package name
- `params` (object): Extra query-string parameters passed through to the API as-is. Most callers need none.
- `source` (string, required): Data source name, e.g. 'wikipedia', 'arxiv', 'edgar' (see list_dataville_sources)
- `summary` (boolean): If true, truncate `body` to its first 100 characters to save tokens

### `query_dataville` (~243 tokens)

Query Dataville with SQL

Run a read-only SQL SELECT (DuckDB dialect) over Dataville's stored tables: wiki, arxiv, gutenberg, fooddata, pwc_methods, pwc_datasets, edgar, openalex, pypi, stackexchange. Use it to list, filter (WHERE … ILIKE '%term%'), sort, count, aggregate, or join across sources, and page through results with LIMIT/OFFSET. Get each table's columns from describe_dataville_source. Only SELECT is allowed; at most 1,000 rows are returned (a missing LIMIT becomes LIMIT 1000); queries time out after 30 s. Billed per row returned, so keep LIMIT as small as the task allows. The tables hold Dataville's stored copy: some sources are loaded in bulk, others only hold records fetched before, so a row missing here may still exist upstream — fall back to search_dataville for a specific item.

Input parameters:

- `sql` (string, required): A single SELECT statement, e.g. "SELECT company_name, form_type, filing_date FROM edgar WHERE company_name ILIKE '%apple%' ORDER BY filing_date DESC LIMIT 10"

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-dataville-dataville-mcp/dataville-dataville-mcp#diagnostics

## Score history

- 2026-11-05: 91
- 2026-11-04: 90
- 2026-11-03: 90
- 2026-11-02: 89
- 2026-11-01: 89
- 2026-10-31: 89
- 2026-10-30: 88
- 2026-10-29: 88
- 2026-10-28: 87
- 2026-10-27: 87
- 2026-10-26: 86
- 2026-10-25: 86
- 2026-10-24: 85
- 2026-10-23: 85
- 2026-10-22: 84
- 2026-10-21: 81
- 2026-10-20: 81
- 2026-10-19: 81
- 2026-10-18: 81
- 2026-10-17: 81
- 2026-10-16: 81
- 2026-10-15: 81
- 2026-10-14: 81
- 2026-10-13: 49
- 2026-10-12: 49
- 2026-10-11: 49

## Common questions

### What is the Dataville MCP server?

Dataville is an MCP server listed in the public MCP registry as com.dataville/dataville-mcp. SEC filings, Wikipedia, arXiv, US Census and more for AI agents, with every answer source-linked. This page covers its npm package (@dataville/dataville-mcp).

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

Dataville scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Dataville MCP server expose?

Dataville exposes 4 tools: list_dataville_sources, describe_dataville_source, search_dataville, query_dataville. Their descriptions and schemas cost roughly 550 tokens of context every time the server is loaded.

### Is the Dataville MCP server still maintained?

Dataville is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Dataville MCP server under?

Dataville declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@dataville/dataville-mcp
- Socket report: https://socket.dev/npm/package/@dataville/dataville-mcp
- Repository: https://github.com/datavilleorg/dataville-mcp
- Website: https://dataville.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-dataville-dataville-mcp/dataville-dataville-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-dataville-dataville-mcp/dataville-dataville-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-dataville-dataville-mcp/dataville-dataville-mcp