Remote MCP · Endpoint

own-words MCP server

No. own-words answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://own-words-mcp.alexslkmain.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.alexslkgit/own-words
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
205 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Turn notes into a study deck: answer each card in your own words, then compare.
Listing
From the official MCP registry (active).
Recent checks of own-words
CheckedResultHandshake
20 minutes agoHandshake completed205 ms
9 days agoHandshake completed169 ms
9 days agoHandshake completed214 ms
11 days agoHandshake completed197 ms
12 days agoHandshake completed161 ms
13 days agoHandshake completed190 ms
14 days agoHandshake completed194 ms
15 days agoHandshake completed155 ms
16 days agoHandshake completed151 ms
19 days agoHandshake completed173 ms
21 days agoHandshake completed220 ms
24 days agoHandshake completed375 ms
26 days agoHandshake completed170 ms
28 days agoHandshake completed180 ms

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

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