Skip to content
DataNexus MCP logo

DataNexus MCP

Lets Claude query 55 tools over public records covering nonprofits, DNS, CVEs, patents, federal contracts and regulations.

At a glanceswept 2026-10-13

1.5k installs/mo

Emerging

For
people using Claude or other AI agents to look up public records on companies, vulnerabilities, patents or rules
Price
Price not read
Activity
Actively maintainedrelease 3 months ago
Company
Domain since 2026domain registered
Runs as
API
What people do with it
  • check a nonprofit's filings and financial health before a grant
  • screen vendors against federal exclusion lists
  • scan a software bill of materials for known vulnerabilities
The companyeach fact with its source · read 2026-10-13
  • Domain since2026domain registered
How a program reaches itfound, not claimed · read 2026-10-13
  • MCP servercom.datanexusmcp/mcp-serververified in the MCP registry
  • Stateanswers, 55 toolschecked 2026-10-13
  • Address to connectdatanexusmcp.com/mcp
  • MCP docsdatanexusmcp.comthe vendor's page ↗

MCP server details →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Agentsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

All Agents tools →

Questions this page answers
  • What is DataNexus MCP?

    Lets Claude query 55 tools over public records covering nonprofits, DNS, CVEs, patents, federal contracts and regulations. It is listed in the Atlas under Agents.

  • Who is DataNexus MCP for?

    people using Claude or other AI agents to look up public records on companies, vulnerabilities, patents or rules

  • Do people use DataNexus MCP?

    Emerging: 1.5k installs/mo (npm).

  • Is DataNexus MCP still maintained?

    Actively maintained: release 3 months ago.

  • What are alternatives to DataNexus MCP?

    In Agents, by use: Aqta, Tandem, Paylyte, Cloudflare, Claude, PolyAI.

Not quite it? Describe the job

beta

Five tools from the Atlas that fit it, each judged against what you wrote.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.