Remote MCP · Endpoint

KnowMapped MCP server

No. KnowMapped answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://mcp.knowmapped.com/mcp

The last check completed an MCP handshake.

Registry name
com.knowmapped/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
42 ms
Tools exposed
13 tools
Uptime, last 30 days
94.1% from 17 checks
Described by its publisher as
Search, retrieve, create, and update visual knowledge maps in a user's KnowMapped account.
Listing
From the official MCP registry (active).
Recent checks of KnowMapped
CheckedResultHandshake
9 hours agoHandshake completed42 ms
2 days agoHandshake completed60 ms
4 days agoHandshake completed49 ms
5 days agoHandshake completed54 ms
7 days agoHandshake completed55 ms
8 days agoHandshake completed50 ms
9 days agoHandshake completed61 ms
12 days agoHandshake completed45 ms
13 days agoHandshake completed50 ms
15 days agoHandshake completed173 ms
16 days agoHandshake completed52 ms
17 days agoFailed - the request timed out—
19 days agoHandshake completed55 ms
19 days agoHandshake completed52 ms
20 days agoHandshake completed50 ms
21 days agoHandshake completed70 ms
22 days agoHandshake completed57 ms

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

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