DataNexus MCP
REMOTE · DATANEXUSMCP.COM · 2 COMPONENTS · SCANNED SEP 24
Public data intelligence for AI agents — CVE, compliance, patents, contracts, domains.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (security_fetch_cve_watch). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 13463 tokens (~244/item across 55 items; 55 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 56 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the DataNexus MCP server?
DataNexus MCP is a hosted endpoint at https://datanexusmcp.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · datanexusmcp.com
claude mcp add --transport http com-datanexusmcp-mcp-server 'https://datanexusmcp.com/mcp'
{
"mcpServers": {
"com-datanexusmcp-mcp-server": {
"url": "https://datanexusmcp.com/mcp"
}
}
} {
"servers": {
"com-datanexusmcp-mcp-server": {
"type": "http",
"url": "https://datanexusmcp.com/mcp"
}
}
} [mcp_servers.com-datanexusmcp-mcp-server] url = "https://datanexusmcp.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-datanexusmcp-mcp-server": {
"type": "remote",
"url": "https://datanexusmcp.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-datanexusmcp-mcp-server --url 'https://datanexusmcp.com/mcp' --transport streamable-http
mcp_servers:
com-datanexusmcp-mcp-server:
url: "https://datanexusmcp.com/mcp" {
"McpServers": {
"com-datanexusmcp-mcp-server": {
"Transport": "http",
"Url": "https://datanexusmcp.com/mcp"
}
}
} assistant mcp add com-datanexusmcp-mcp-server -t streamable-http -u 'https://datanexusmcp.com/mcp'
{
"mcpServers": {
"com-datanexusmcp-mcp-server": {
"type": "http",
"url": "https://datanexusmcp.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 30 Aug 26 0
- Stability: fail → pass ▲ security
- 26 Aug 26 77
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- Server version: 3.4.5 → 2.4.13 functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://datanexusmcp.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=datanexusmcp.com | CN=YE2,O=Let's Encrypt,C=US | 26 Aug 2026 | 24 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 61a7b0d6d73bd26074c9aefb80141c6a5d2 |
| SANs: *.datanexusmcp.com, datanexusmcp.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of datanexusmcp.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| datanexusmcp.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://datanexusmcp.com/mcp | Verified | 200 | |
| http (plaintext) | http://datanexusmcp.com/mcp | HTTPS enforced | 308 | https://datanexusmcp.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
security_fetch_package_licence ~264
Fetch the SPDX licence identifier for an open source package version. Read-only. No side effects. Idempotent. package: Package name e.g. flask. Required. version: Exact version string e.g. 2.3.0. Required. ecosystem: One of PyPI, npm, Maven, Go, Cargo, NuGet, RubyGems. Required. Returns the SPDX licence identifier e.g. MIT, Apache-2.0, GPL-3.0. Use this to verify licence compatibility before including a dependency. Use security_fetch_package_vulnerabilities instead when checking for security issues not licences. Verified source: deps.dev (Google). 1-hour cache. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="security_fetch_package_licence", intended_query="{what the user needed}", gap_description="{what was missing or wrong in the result}".
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | Package ecosystem: npm, pypi, cargo, go, maven, nuget. Required. |
| package | string | yes | Package name e.g. requests. Required. |
| version | string | yes | Package version e.g. 2.28.0. Required. |
Structured output declared, but exposes no named fields.
No examples provided.
security_fetch_package_maintainer_history ~207
Analyse ownership and release history for an npm or PyPI package to detect supply-chain risk. Uses PyPI JSON API and npm registry — data refreshed on each call, 1-hour cache. Returns maintainer_count, recent_changes, ownership_transfers, account_ages, anomaly_score (0.0–1.0), and maintainer_health (healthy | stale | abandoned | suspicious). Rate limit: 60/minute. No auth required. For security engineers auditing open-source dependencies before inclusion in production builds. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="security_fetch_package_maintainer_history", intended_query="{what the user needed}", gap_description="{what was missing or wrong in the result}".
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | Package ecosystem: npm, pypi, cargo, go. Required. |
| package_name | string | yes | Package name e.g. requests. Required. |
Structured output declared, but exposes no named fields.
No examples provided.
security_fetch_package_risk_brief ~241
Single SHIP/CAUTION/BLOCK verdict for any package. Combines CVEs, licence, maintainer health, and transitive count in one call. Uses OSV.dev, deps.dev, PyPI, and npm registry — data refreshed on each call. Returns verdict (SHIP/CAUTION/BLOCK), critical_cve_count, high_cve_count, licence_risk, maintainer_health, transitive_count, resolved_version, upstream_status, and reasoning. Rate limit: 30/minute. No auth required. For security engineers performing pre-inclusion package review. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="security_fetch_package_risk_brief", intended_query="{what the user needed}", gap_description="{what was missing or wrong in the result}".
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | Package ecosystem: npm, pypi, cargo, go, maven. Required. |
| package_name | string | yes | Package name e.g. requests. Required. |
| version | – | – | Package version e.g. 2.28.0. Required. |
Structured output declared, but exposes no named fields.
No examples provided.
security_fetch_package_vulnerabilities ~346
Fetch all known CVEs for an open source package version or a batch of packages. Read-only. No side effects. Idempotent. Single-package mode: package (e.g. requests), version (e.g. 2.28.0), ecosystem (PyPI/npm/Maven/Go/Cargo/NuGet/RubyGems). Batch mode: packages array of {name, version, ecosystem} objects — max 50 per call. If packages array is provided and non-empty, batch mode is used and package/version/ecosystem are ignored. Batch returns {results: [...], partial: bool, failed_count: int}. Each result has vuln_count and vulnerabilities list. Returns CVE ID, severity, CVSS score, affected range, and fixed version. Use security_fetch_cve_detail for full detail by CVE ID. Use security_audit_sbom_vulnerabilities for SBOM files. Verified source: Google OSV.dev. 1-hour cache. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="security_fetch_package_vulnerabilities", intended_query="{what the user needed}", gap_description="{what was missing or wrong in the result}".
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | – | – | Package ecosystem: npm, pypi, cargo, go, maven, nuget. Required. |
| package | – | – | Package name e.g. requests. Required in single-package mode. |
| packages | – | – | Batch list of {name, version, ecosystem} objects. Max 50. |
| version | – | – | Package version e.g. 2.28.0. Required in single-package mode. |
Structured output declared, but exposes no named fields.
No examples provided.
validate_tool_output ~302
Validate a DataNexus tool response for data quality issues using two-layer validation: deterministic rules first, then AI review for ambiguous cases. Read-only. Never blocks. tool_id: DataNexus tool identifier e.g. T04, T10, T22. Required. Find in the tool_id field of any response. query_hash: Hash from the response you are validating. Required. Enables feedback correlation. response_json: Full tool response serialised as a JSON string. Required. Returns pass or issues_found, with issues from each layer and whether feedback was auto-filed. Both layers must agree before feedback is filed. Use validate_tool_output to check data quality. Use report_feedback instead to manually report an issue you have already identified. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="validate_tool_output", intended_query="{what the user needed}", gap_description="{what was missing or wrong in the result}".
| Name | Type | Req | Description |
|---|---|---|---|
| query_hash | string | yes | Hash from the response being validated — found in the query_hash field of any response. Enables feedback correlation. Required. |
| response_json | string | yes | The full tool response, serialised as a JSON string, to validate for data quality issues. Required. |
| tool_id | string | yes | DataNexus tool identifier, e.g. T04, T10, T22 — found in the tool_id field of any response. Required. |
Structured output declared, but exposes no named fields.
No examples provided.
What is the DataNexus MCP server?
DataNexus MCP is listed in the public MCP registry as com.datanexusmcp/mcp-server. Public data intelligence for AI agents, CVE, compliance, patents, contracts, domains. This page covers its hosted endpoint (https://datanexusmcp.com/mcp).
Is the DataNexus MCP server safe to use?
DataNexus MCP scores 77 out of 100 on VerifyMCP. 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 DataNexus MCP server expose?
DataNexus MCP exposes 55 tools: report_feedback, report_mcpize_link, validate_tool_output, search_datanexus_tools, nonprofit_fetch_nonprofit_by_ein, and 50 more. Their descriptions and schemas cost roughly 12,515 tokens of context every time the server is loaded.
Does the DataNexus MCP server require authentication?
No. We connected to DataNexus MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the DataNexus MCP server still maintained?
DataNexus MCP is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.