Remote MCP · Endpoint

Ortexo MCP server

No. Ortexo answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://mcp.ortexo.com/mcp

The last check completed an MCP handshake.

Registry name
com.ortexo/mcp
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
154 ms
Tools exposed
41 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Romanian and EU legislation and case law, with exact article citations and point-in-time text.
Listing
From the official MCP registry (active).
Recent checks of Ortexo
CheckedResultHandshake
7 hours agoHandshake completed154 ms
4 days agoHandshake completed149 ms
14 days agoHandshake completed134 ms
15 days agoHandshake completed191 ms
15 days agoHandshake completed161 ms
17 days agoHandshake completed137 ms
18 days agoHandshake completed159 ms
19 days agoHandshake completed158 ms
20 days agoHandshake completed159 ms
21 days agoHandshake completed165 ms
23 days agoHandshake completed156 ms
26 days agoCredentials required—
28 days agoCredentials required—

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

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