Remote MCP · Endpoint

CoreNexis API MCP server

No — it is up, but it requires credentials. CoreNexis API answered 1 hour ago with an authentication challenge rather than a session.

Auth requiredLast checked 1 hour ago

Server URL

https://api.corenexis.com/mcp/server

The endpoint is answering and asked us for credentials. That is a working server, not an outage.

Registry name
com.corenexis/api
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
Behind credentials
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
PDF from HTML or Markdown, OCR, email validation, image conversion and hosting, QR and barcodes.
Listing
From the official MCP registry (active).
Recent checks of CoreNexis API
CheckedResultHandshake
1 hour agoCredentials required—
22 hours agoHandshake completed127 ms
2 days agoHandshake completed89 ms
3 days agoHandshake completed55 ms
4 days agoHandshake completed90 ms
5 days agoHandshake completed83 ms
6 days agoHandshake completed379 ms
8 days agoHandshake completed9.88 s
11 days agoHandshake completed78 ms
13 days agoHandshake completed93 ms
15 days agoHandshake completed131 ms
18 days agoHandshake completed92 ms
20 days agoHandshake completed312 ms
22 days agoHandshake completed111 ms
24 days agoHandshake completed80 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

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 CoreNexis API and makes no claim about it beyond what these checks measured.