Should my agent depend on the MCP server com.datanexusmcp/mcp-server?

Verdict: allow — rich-slow-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

DataNexus MCP

com.datanexusmcp/mcp-server

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

— the operator's own registry description reported

Publisher com.datanexusmcp · first seen 2026-08-12 · endpoint https://datanexusmcp.com/mcp

allow

verdict

rich-slow-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-slow-solo — safe to depend on

Cluster rich-slow-solo · distinctiveness 0.855 (unusual). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency455 ms

vs populationslow

protocolcurrent

authopen

Use — can it use it?

tools55

vs populationhigh

capabilities6

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_5b393607af9732978af568c0 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

apikeys_generate_api_key apikeys_revoke_api_key apikeys_rotate_api_key compliance_check_sam_exclusion compliance_fetch_finra_broker compliance_fetch_npi_provider compliance_search_npi_by_name domain_check_email_security domain_fetch_dns_records domain_fetch_domain_history domain_fetch_domain_rdap domain_fetch_reverse_ip domain_fetch_ssl_certificate_chain domain_fetch_subdomains frontend_security_audit_ci_pipeline frontend_security_audit_manifest frontend_security_detect_typosquatting frontend_security_fetch_package_risk_brief govcon_fetch_open_solicitations govcon_fetch_vendor_contract_history govcon_search_contract_awards legal_fetch_inventor_portfolio legal_fetch_patent_by_number legal_fetch_patent_citations legal_search_patents_by_keyword nonprofit_fetch_charity_uk nonprofit_fetch_nonprofit_by_ein nonprofit_fetch_nonprofit_financial_trends nonprofit_fetch_nonprofit_full_profile nonprofit_search_nonprofits_by_category nonprofit_search_nonprofits_by_name regulatory_fetch_docket_details regulatory_fetch_federal_register_notices regulatory_search_open_rulemakings report_feedback report_mcpize_link search_datanexus_tools security_audit_licence_compatibility security_audit_sbom_continuous security_audit_sbom_license_policy security_audit_sbom_vulnerabilities security_detect_typosquatting security_fetch_cisa_kev security_fetch_cve_detail security_fetch_cve_epss security_fetch_cve_risk_summary security_fetch_cve_watch security_fetch_cve_watch_status security_fetch_dependency_graph security_fetch_licence_analysis security_fetch_package_licence security_fetch_package_maintainer_history security_fetch_package_risk_brief security_fetch_package_vulnerabilities validate_tool_output

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	55/55	✓
has a description	55/55	✓
description is substantive	55/55	✓
parameters are typed	55/55	✓
parameters are described	55/55	✓

55 of 55 tools graded · 55 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

3.4.5

server version DataNexus MCP

Capabilities: experimental extensions logging prompts resources tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:58:02Z	ok_tools	200	455	2025-06-18
2026-08-12T05:33:18Z	ok_tools	200	465	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/com.datanexusmcp/mcp-server.svg)](https://robinsaige.com/s/com.datanexusmcp/mcp-server)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview