Remote MCP · Endpoint

MaximoFN Content MCP server

No. MaximoFN Content answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://www.maximofn.com/mcp

The last check completed an MCP handshake.

Registry name
com.maximofn/content
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
258 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read-only search over the AI/ML posts, tips and projects of maximofn.com (es/en/pt).
Listing
From the official MCP registry (active).
Recent checks of MaximoFN Content
CheckedResultHandshake
6 hours agoHandshake completed258 ms
2 days agoHandshake completed232 ms
4 days agoHandshake completed280 ms
6 days agoHandshake completed199 ms
8 days agoHandshake completed193 ms
10 days agoHandshake completed189 ms
12 days agoHandshake completed676 ms
13 days agoHandshake completed316 ms
14 days agoHandshake completed344 ms
15 days agoHandshake completed384 ms
18 days agoHandshake completed202 ms
20 days agoHandshake completed226 ms
21 days agoHandshake completed214 ms
23 days agoHandshake completed274 ms

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

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