@dataville/dataville-mcp

MCPattestedlive

v0.1.8com.datavilleUnknownUpdated 5d agonpm GitHub

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

Endpoint healthlive

checked 7 days ago · 281ms

100% of the last 1 check reached this endpoint

Works in

ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build

A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.

2GitHub stars

5d agoLast update

Needs 1 credential before it runs

DATAVILLE_API_KEYAPI keyrequired
Dataville API key from https://app.dataville.com/api-keys

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package

Authorcom.dataville

LicenseUnknown

Version0.1.8

Sourcenpm+mcp-registry

npm@dataville/dataville-mcp

GitHubdatavilleorg/dataville-mcp

SBOMCycloneDX 1.6 ↓

Trust Status

A

85/100Trusted

✓Listed in Forge index+10/10

✓Identity verified · attested build+20/20

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

✓npm Trusted Publishing (Sigstore)+5/5

—npm maintainer match+0/5

→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusIdentity verified

PublisherUnverified

SignatureUnsigned

Domain—

Provenance✓ Sigstore-verified · 9d930a7

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface15 tools · none privileged

Security scan✓ Cleanv0.1.8 · todayHow well does this scan work?

EvalsNone

IndexedOct 10, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

15 tools · none privileged

Statically extracted from the published packagev0.1.8 · 14h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

Filter toolsPrivileged only

list_dataville_sourcesList every Dataville data source with a one-line description and the SQL tables (if any) that query_dataville can read for it.

List every Dataville data source with a one-line description and the SQL tables (if any) that query_dataville can read for it.

No input schema was published for this tool.

describe_dataville_sourceShow how to use one data source: what search_dataville expects as keywords (with an example that returns a result),

Show how to use one data source: what search_dataville expects as keywords (with an example that returns a result),

No input schema was published for this tool.

search_datavilleLook up one thing in a Dataville data source by keywords and get back the single best-matching record

Look up one thing in a Dataville data source by keywords and get back the single best-matching record

No input schema was published for this tool.

query_datavilleRun a read-only SQL SELECT (DuckDB dialect) over Dataville's stored tables:

Run a read-only SQL SELECT (DuckDB dialect) over Dataville's stored tables:

No input schema was published for this tool.

wikipediaWikipedia articles

Wikipedia articles

No input schema was published for this tool.

arxivarXiv preprints

arXiv preprints

No input schema was published for this tool.

gutenbergProject Gutenberg public-domain books

Project Gutenberg public-domain books

No input schema was published for this tool.

censusUS Census Bureau data

US Census Bureau data

No input schema was published for this tool.

fooddataUSDA FoodData Central

USDA FoodData Central

No input schema was published for this tool.

paperswithcodePapers with Code — ML papers, code, and benchmarks

Papers with Code — ML papers, code, and benchmarks

No input schema was published for this tool.

edgarSEC EDGAR filings

SEC EDGAR filings

No input schema was published for this tool.

openalexOpenAlex scholarly works

OpenAlex scholarly works

No input schema was published for this tool.

pypiPyPI package metadata

PyPI package metadata

No input schema was published for this tool.

stackexchangeStack Exchange Q&A

Stack Exchange Q&A

No input schema was published for this tool.

newsFront-page news headlines from a historical archive (not live/current news)

Front-page news headlines from a historical archive (not live/current news)

No input schema was published for this tool.

15 of 15 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

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

Keywords

mcp

Alternatives

Comparing tool surfaces…

Tools exposed

15 tools · none privileged · observed 2026-10-17 by static extraction. A tool surface is what one scan read on one day, not a live capability list.

list_dataville_sources
describe_dataville_source
search_dataville
query_dataville
wikipedia
arxiv
gutenberg
census
fooddata
paperswithcode
edgar
openalex
pypi
stackexchange
news

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-17 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

zod4.6.7
@modelcontextprotocol/sdk1.32.117 dependencies
- ajv8.20.04 dependencies
  - fast-deep-equal3.1.3
  - fast-uri3.1.8
  - json-schema-traverse1.0.0
  - require-from-string2.0.2
- zod4.6.7shown above
- cors2.8.62 dependencies
  - object-assign4.1.1
  - vary1.1.2
- hono4.13.13
- jose6.2.12
- express5.3.0+27 not drawn1 dependency
  - vary1.1.2shown above
- raw-body3.0.2+4 not drawn
- ajv-formats3.0.11 dependency
  - ajv8.20.0shown above
- cross-spawn7.0.6+3 not drawn
- eventsource3.0.71 dependency
  - eventsource-parser3.1.1
- content-type1.0.5
- pkce-challenge5.0.1
- @hono/node-server2.1.5
- json-schema-typed8.0.2
- eventsource-parser3.1.1shown above
- express-rate-limit8.7.1+2 not drawn
- zod-to-json-schema3.25.2

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 49
below the depth cap: 5

wrappy 1 — required by once@1.4.0package cap reached
http-errors ^2.0.1 — required by send@1.2.1package cap reached
mime-types ^3.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by send@1.2.1package cap reached
on-finished ^2.4.1 — required by send@1.2.1package cap reached
range-parser ^1.2.1 — required by send@1.2.1package cap reached
statuses ^2.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by debug@4.4.3package cap reached
debug ^4.4.0 — required by router@2.2.0package cap reached
depd ^2.0.0 — required by router@2.2.0package cap reached
is-promise ^4.0.0 — required by router@2.2.0package cap reached
parseurl ^1.3.3 — required by router@2.2.0package cap reached

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.