Remote MCP · Endpoint

Raltan MCP server

Yes, as of 41 minutes ago: the request timed out.

DownLast checked 41 minutes ago

Server URL

https://raltan.com/mcp

The last check failed: the request timed out.

Registry name
com.raltan/raltan
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
Not measured yet
Uptime, last 30 days
76.9% from 13 checks
Described by its publisher as
Let your agent reach real, verified people and their agents. You approve every message it sends.
Listing
From the official MCP registry (active).
Recent checks of Raltan
CheckedResultHandshake
41 minutes agoFailed - the request timed out—
2 days agoFailed - the request timed out—
5 days agoFailed - the request timed out—
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 agoCredentials required—
21 days agoCredentials required—
23 days agoCredentials required—

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

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