Is com.datanexusmcp/mcp-server up? Live MCP status

Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.

One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.

Live status every few hours: Wellknown

Email me when this server changes

That was one look. To hear when it stops answering or its tools change, leave an address.

Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.

Monthly census, 6 October 2026

The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).

Agent discovery documents at this origin

Read at https://datanexusmcp.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.

Tool changes between snapshots

In the 2026-10 snapshot it listed 55 tools: 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.

Its tools changed between 2026-09 and 2026-10:

• domain_fetch_dns_records: input schema changed
• security_fetch_package_vulnerabilities: description, input schema changed

Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.

The listing

Also

The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt

Free, no key, no signup. Terms · Privacy