DataNexus MCP

warnings

datanexusmcp.com

Public data intelligence for AI agents — CVE, compliance, patents, contracts, domains.

https://datanexusmcp.com/mcpNo authMCP 2025-11-25v3.4.5last checked 24 Aug 2026spoke MCP on 2 of 2 checks (30 days)initialize in 195 ms

How to authenticate

Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	No auth
Protected-resource metadata	✕Not found Without it a client has to guess where the authorization server lives.
Anonymous access	Handshake succeeds; 55 tools listable
Credentials demanded in prose	✕report_mcpize_link, compliance_fetch_npi_provider, security_fetch_package_maintainer_history, apikeys_rotate_api_key, apikeys_revoke_api_key These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error.

What the probe found

warningTools needing credentials are listed without a challenge

5 of the 55 tools listed anonymously say in their own descriptions that they need an account or a key (report_mcpize_link, compliance_fetch_npi_provider, security_fetch_package_maintainer_history, apikeys_rotate_api_key, apikeys_revoke_api_key), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

Tools

apikeys_generate_api_keyapikeys_revoke_api_keyapikeys_rotate_api_keycompliance_check_sam_exclusioncompliance_fetch_finra_brokercompliance_fetch_npi_providercompliance_search_npi_by_namedomain_check_email_securitydomain_fetch_dns_recordsdomain_fetch_domain_historydomain_fetch_domain_rdapdomain_fetch_reverse_ipdomain_fetch_ssl_certificate_chaindomain_fetch_subdomainsfrontend_security_audit_ci_pipelinefrontend_security_audit_manifestfrontend_security_detect_typosquattingfrontend_security_fetch_package_risk_briefgovcon_fetch_open_solicitationsgovcon_fetch_vendor_contract_historygovcon_search_contract_awardslegal_fetch_inventor_portfoliolegal_fetch_patent_by_numberlegal_fetch_patent_citationslegal_search_patents_by_keywordnonprofit_fetch_charity_uknonprofit_fetch_nonprofit_by_einnonprofit_fetch_nonprofit_financial_trendsnonprofit_fetch_nonprofit_full_profilenonprofit_search_nonprofits_by_categorynonprofit_search_nonprofits_by_nameregulatory_fetch_docket_detailsregulatory_fetch_federal_register_noticesregulatory_search_open_rulemakingsreport_feedbackreport_mcpize_linksearch_datanexus_toolssecurity_audit_licence_compatibilitysecurity_audit_sbom_continuoussecurity_audit_sbom_license_policysecurity_audit_sbom_vulnerabilitiessecurity_detect_typosquattingsecurity_fetch_cisa_kevsecurity_fetch_cve_detailsecurity_fetch_cve_epsssecurity_fetch_cve_risk_summarysecurity_fetch_cve_watchsecurity_fetch_cve_watch_statussecurity_fetch_dependency_graphsecurity_fetch_licence_analysissecurity_fetch_package_licencesecurity_fetch_package_maintainer_historysecurity_fetch_package_risk_briefsecurity_fetch_package_vulnerabilitiesvalidate_tool_output

Contract history

24 Aug 2026v3.4.5first recorded contract

Get alerted when this contract changes

Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.

Prefer a feed reader? This page's contract changes are also an Atom feed.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/datanexus-mcp/badge.svg)](https://mcpi.app/servers/datanexus-mcp)