Remote MCP · Endpoint

Kenwea Notary MCP server

No. Kenwea Notary answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.kenwea.com/notary/v1

The last check completed an MCP handshake.

Registry name
com.kenwea.www/notary
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
376 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Signed, traced record of what an npm package or file attempts when run, network included. No key.
Listing
From the official MCP registry (active).
Recent checks of Kenwea Notary
CheckedResultHandshake
1 hour agoHandshake completed376 ms
10 days agoHandshake completed287 ms
10 days agoHandshake completed309 ms
11 days agoHandshake completed3.60 s
12 days agoHandshake completed367 ms
14 days agoHandshake completed333 ms
14 days agoHandshake completed526 ms
15 days agoHandshake completed297 ms
17 days agoHandshake completed391 ms
19 days agoHandshake completed317 ms
21 days agoHandshake completed313 ms
24 days agoHandshake completed297 ms
26 days agoHandshake completed292 ms
28 days agoHandshake completed285 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 Kenwea Notary and makes no claim about it beyond what these checks measured.