Remote MCP · Endpoint

Flipnem MCP server

No. Flipnem answered an MCP handshake 1 hour ago.

Up · key neededLast checked 1 hour ago

Server URL

https://flipnem.com/api/mcp

The handshake completes, but listing its tools needs credentials.

Registry name
com.flipnem/flipnem
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
47 ms
Tools exposed
Behind credentials
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Build and study spaced-repetition flashcards with your agent.
Listing
From the official MCP registry (active).
Recent checks of Flipnem
CheckedResultHandshake
1 hour agoHandshake completed47 ms
2 days agoHandshake completed44 ms
4 days agoHandshake completed37 ms
5 days agoHandshake completed66 ms
7 days agoHandshake completed87 ms
8 days agoHandshake completed44 ms
9 days agoHandshake completed42 ms
12 days agoHandshake completed50 ms
13 days agoHandshake completed59 ms
15 days agoHandshake completed43 ms
16 days agoHandshake completed46 ms
17 days agoHandshake completed39 ms
18 days agoHandshake completed40 ms
19 days agoHandshake completed47 ms
20 days agoHandshake completed42 ms
21 days agoHandshake completed47 ms
22 days agoHandshake completed38 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 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 Flipnem and makes no claim about it beyond what these checks measured.