Remote MCP · Endpoint

FreeDailyPro Tools MCP server

No. FreeDailyPro Tools answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.freedailypro.com/mcp

The last check completed an MCP handshake.

Registry name
com.freedailypro/tools
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
343 ms
Tools exposed
252 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
200+ MCP tools: PDF, PowerPoint, text, calculators, media, publishing. Nothing stored.
Listing
From the official MCP registry (active).
Recent checks of FreeDailyPro Tools
CheckedResultHandshake
1 hour agoHandshake completed343 ms
3 days agoHandshake completed208 ms
13 days agoHandshake completed216 ms
14 days agoHandshake completed185 ms
15 days agoHandshake completed188 ms
16 days agoHandshake completed135 ms
18 days agoHandshake completed141 ms
18 days agoHandshake completed150 ms
19 days agoHandshake completed139 ms
21 days agoHandshake completed164 ms
22 days agoHandshake completed173 ms
25 days agoHandshake completed234 ms
27 days agoHandshake completed322 ms

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

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