Remote MCP · Endpoint

Altss Public Profiles MCP server

No. Altss Public Profiles answered an MCP handshake 33 minutes ago.

UpLast checked 33 minutes ago

Server URL

https://altss.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.altss-data/public-profiles
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
137 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Search and read bounded published Altss profile summaries with canonical citations. No private data.
Listing
From the official MCP registry (active).
Recent checks of Altss Public Profiles
CheckedResultHandshake
33 minutes agoHandshake completed137 ms
3 days agoHandshake completed204 ms
13 days agoHandshake completed148 ms
13 days agoHandshake completed359 ms
15 days agoHandshake completed158 ms
16 days agoHandshake completed321 ms
17 days agoHandshake completed154 ms
18 days agoHandshake completed375 ms
18 days agoHandshake completed133 ms
20 days agoHandshake completed147 ms
22 days agoHandshake completed132 ms
25 days agoHandshake completed334 ms
27 days agoHandshake completed157 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 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 Altss Public Profiles and makes no claim about it beyond what these checks measured.