Remote MCP · Endpoint

The Knowledge MCP server

No. The Knowledge answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://the-knowledge-commons.lorh89.chatgpt.site/api/agent/mcp

The last check completed an MCP handshake.

Registry name
site.chatgpt.lorh89.the-knowledge-commons/evidence
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.15 s
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Free MCP, D1 and SQLite evidence lookup with sources and dates. Share findings for others to reuse.
Listing
From the official MCP registry (active).
Recent checks of The Knowledge
CheckedResultHandshake
5 hours agoHandshake completed1.15 s
9 days agoHandshake completed1.40 s
10 days agoHandshake completed275 ms
11 days agoHandshake completed1.15 s
12 days agoHandshake completed873 ms
14 days agoHandshake completed1.07 s
14 days agoHandshake completed1.36 s
15 days agoHandshake completed674 ms
17 days agoHandshake completed961 ms
19 days agoHandshake completed918 ms
21 days agoHandshake completed989 ms
24 days agoHandshake completed249 ms
26 days agoHandshake completed825 ms
28 days agoHandshake completed180 ms

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

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