Remote MCP · Endpoint

Nearius MCP server

Yes, as of 2 days ago: the server returned an HTTP error.

DownLast checked 2 days ago

Server URL

https://mcp.nearius.com/mcp

The last check failed: the server returned an HTTP error.

Registry name
com.nearius/nearius
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
Not measured yet
Uptime, last 30 days
83.3% from 12 checks
Described by its publisher as
Jurisprudencia española verificada para tu IA: sentencias con ECLI, artículos del BOE y doctrina
Listing
From the official MCP registry (active).
Recent checks of Nearius
CheckedResultHandshake
2 days agoFailed - the server returned an HTTP error—
5 days agoCredentials required—
7 days agoCredentials required—
9 days agoCredentials required—
11 days agoCredentials required—
13 days agoCredentials required—
15 days agoCredentials required—
17 days agoCredentials required—
19 days agoCredentials required—
20 days agoFailed - the server returned an HTTP error—
21 days agoCredentials required—
22 days agoCredentials required—

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

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