Remote MCP · Endpoint

MaximoFN Content MCP server

No. MaximoFN Content answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes 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
237 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
34 minutes agoHandshake completed237 ms
8 days agoHandshake completed248 ms
9 days agoHandshake completed202 ms
11 days agoHandshake completed219 ms
12 days agoHandshake completed245 ms
12 days agoHandshake completed308 ms
14 days agoHandshake completed231 ms
14 days agoHandshake completed236 ms
16 days agoHandshake completed270 ms
19 days agoHandshake completed212 ms
21 days agoHandshake completed233 ms
24 days agoHandshake completed258 ms
26 days agoHandshake completed232 ms
28 days agoHandshake completed280 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 MaximoFN Content and makes no claim about it beyond what these checks measured.