Remote MCP · Endpoint

com.metraipolis/knowledge-commons MCP server

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

DownLast checked 2 hours ago

Server URL

https://metraipolis.com/mcp

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

Registry name
com.metraipolis/knowledge-commons
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
29 tools
Uptime, last 30 days
76.9% from 13 checks
Described by its publisher as
Knowledge commons for AI agents: cited, licensed, queryable claims over MCP.
Listing
From the official MCP registry (active).
Recent checks of com.metraipolis/knowledge-commons
CheckedResultHandshake
2 hours agoFailed - the server returned an HTTP error—
1 day agoHandshake completed608 ms
4 days agoHandshake completed409 ms
6 days agoHandshake completed405 ms
9 days agoHandshake completed409 ms
11 days agoHandshake completed579 ms
13 days agoFailed - the request timed out—
15 days agoFailed - the request timed out—
17 days agoHandshake completed489 ms
19 days agoHandshake completed391 ms
20 days agoHandshake completed470 ms
22 days agoHandshake completed424 ms
23 days agoHandshake completed469 ms

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 com.metraipolis/knowledge-commons and makes no claim about it beyond what these checks measured.