Remote MCP · Endpoint
DataNexus MCP MCP server
No. DataNexus MCP answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://datanexusmcp.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.datanexusmcp/mcp-server
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 497 ms
- Tools exposed
- 55 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Public data intelligence for AI agents — CVE, compliance, patents, contracts, domains.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 497 ms |
| 1 day ago | Handshake completed | 448 ms |
| 3 days ago | Handshake completed | 157 ms |
| 3 days ago | Handshake completed | 451 ms |
| 4 days ago | Handshake completed | 457 ms |
| 5 days ago | Handshake completed | 564 ms |
| 7 days ago | Handshake completed | 457 ms |
| 10 days ago | Handshake completed | 462 ms |
| 12 days ago | Handshake completed | 467 ms |
| 15 days ago | Handshake completed | 499 ms |
| 17 days ago | Handshake completed | 443 ms |
| 19 days ago | Handshake completed | 372 ms |
| 21 days ago | Handshake completed | 453 ms |
| 23 days ago | Handshake completed | 450 ms |
| 25 days ago | Handshake completed | 447 ms |
| 26 days ago | Handshake completed | 441 ms |
| 28 days ago | Handshake completed | 339 ms |
| 29 days ago | Handshake completed | 470 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with DataNexus MCP and makes no claim about it beyond what these checks measured.