MCP Server

What datanexusmcp/mcp-server MCP server does

The datanexusmcp/mcp-server MCP server gives an MCP client access to DataNexus tools for verified public-data research. Its advertised scope covers 55 tools across vulnerability intelligence, software bills of materials, package licences, domain intelligence, nonprofit filings, healthcare provider records, financial registrations, patents, and government contract data.

Security-focused tools can inspect package vulnerabilities, dependency graphs, CVE records, CISA KEV status, EPSS probability, SBOMs, and SPDX licences. Other tools query IRS nonprofit data, UK Charity Commission records, NPPES provider registrations, FINRA BrokerCheck, SAM.gov exclusions, domain registration and DNS data, certificate transparency records, patents, and contract awards.

How it works

The server can be reached at https://datanexusmcp.com/mcp using an HTTP MCP configuration, or launched locally through the npm package with npx. A discovery tool, search_datanexus_tools, helps an agent identify the appropriate DataNexus tool before making a lookup. Many read-only tools are idempotent and identify their public source and cache period in the tool description.

Results include structured fields suited to agent workflows. For example, package vulnerability checks return CVE identifiers, severity, CVSS scores, affected ranges, and fixed versions, while domain tools return registration, certificate, DNS, or subdomain information. validate_tool_output can review a response for data-quality issues, and report_feedback can file an issue or describe a missing agent capability.

Setup and configuration

For an HTTP-capable MCP client, configure the hosted endpoint as follows:

{
  "mcpServers": {
    "datanexus": {
      "type": "http",
      "url": "https://datanexusmcp.com/mcp"
    }
  }
}

For a local stdio setup, run npx -y @datanexusmcp/mcp-server. Claude Desktop is explicitly documented as a stdio client option. Anonymous access allows 100 calls per month. A free DataNexus key raises the stated limit to 500 calls per month; the key is sent as the X-DataNexus-Key HTTP header. The material does not identify a required environment variable.

Tools and capabilities

The datanexusmcp/mcp-server MCP server supports workflows such as:

• Finding CVEs for one package, a batch of packages, or an SBOM.
• Checking licence identifiers and dependency relationships across common ecosystems.
• Combining CVSS, KEV, and EPSS information when triaging a CVE.
• Looking up domains through RDAP, DNS, SSL certificate history, subdomains, and email-security records.
• Searching or fetching nonprofit, NPI, FINRA, SAM exclusion, patent, and contract information.
• Reporting tool-quality problems and validating returned data without blocking the original result.

Limitations and notes

Coverage and parameters vary by tool. Several lookups are limited to the US or UK, patent searches support specified jurisdictions, and some tools require exact identifiers such as an EIN, NPI, CRD number, CVE ID, package version, or patent number. Domain certificate tools do not support every input type; for example, the certificate-chain lookup excludes IP addresses and wildcard domains, while reverse-IP lookup does not support IPv6-only domains.

Caching and quotas also differ. Examples include one-hour caches for several vulnerability queries, 24-hour caches for many registry and domain results, and a stated free-tier quota for reverse-IP lookups. Large dependency trees and SBOMs may return partial results or take longer. The hosted service reports usage and may provide upgrade hints when a limit is near.