Remote MCP · Endpoint

io.github.ghdejr11-beep/numerology-api MCP server

No. io.github.ghdejr11-beep/numerology-api answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://numerology-api.kunstudio.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.ghdejr11-beep/numerology-api
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
145 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Deterministic Pythagorean numerology MCP. Life Path, Destiny, Soul Urge, compatibility. No API key.
Listing
From the official MCP registry (active).
Recent checks of io.github.ghdejr11-beep/numerology-api
CheckedResultHandshake
2 hours agoHandshake completed145 ms
1 day agoHandshake completed45 ms
3 days agoHandshake completed180 ms
3 days agoHandshake completed75 ms
4 days agoHandshake completed157 ms
5 days agoHandshake completed54 ms
7 days agoHandshake completed73 ms
10 days agoHandshake completed63 ms
12 days agoHandshake completed72 ms
15 days agoHandshake completed70 ms
17 days agoHandshake completed75 ms
19 days agoHandshake completed110 ms
21 days agoHandshake completed113 ms
23 days agoHandshake completed197 ms
25 days agoHandshake completed130 ms
26 days agoHandshake completed65 ms
28 days agoHandshake completed90 ms
29 days agoHandshake completed63 ms

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

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 io.github.ghdejr11-beep/numerology-api and makes no claim about it beyond what these checks measured.