Remote MCP · Endpoint

Alkemata Knowledge Gateway MCP server

No. Alkemata Knowledge Gateway answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://alkemata.com/wp-json/mcp/alkemata-public

The last check completed an MCP handshake.

Registry name
com.alkemata/public-knowledge
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
300 ms
Tools exposed
32 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read Alkemata articles and maps; submit reviewed proposals; create map content with authorization.
Listing
From the official MCP registry (active).
Recent checks of Alkemata Knowledge Gateway
CheckedResultHandshake
1 hour agoHandshake completed300 ms
9 days agoHandshake completed307 ms
9 days agoHandshake completed305 ms
11 days agoHandshake completed307 ms
12 days agoHandshake completed321 ms
13 days agoHandshake completed309 ms
14 days agoHandshake completed347 ms
14 days agoHandshake completed333 ms
16 days agoHandshake completed361 ms
19 days agoHandshake completed317 ms
21 days agoHandshake completed313 ms
24 days agoHandshake completed369 ms
26 days agoHandshake completed303 ms
28 days agoHandshake completed308 ms

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

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