Remote MCP · Endpoint

GF Agent Toll MCP server

No. GF Agent Toll answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://api.gfpick.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.hamadalmajdouie-rgb/gf-agent-toll
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
83 ms
Tools exposed
21 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
GF Pick MCP: Saudi import costs and GCC commerce analytics. Free tool; x402 from 0.25 USDC.
Listing
From the official MCP registry (active).
Recent checks of GF Agent Toll
CheckedResultHandshake
5 hours agoHandshake completed83 ms
9 days agoHandshake completed81 ms
10 days agoHandshake completed69 ms
11 days agoHandshake completed70 ms
12 days agoHandshake completed91 ms
14 days agoHandshake completed156 ms
14 days agoHandshake completed96 ms
15 days agoHandshake completed55 ms
17 days agoHandshake completed178 ms
19 days agoHandshake completed103 ms
21 days agoHandshake completed87 ms
24 days agoHandshake completed59 ms
26 days agoHandshake completed103 ms
28 days agoHandshake completed65 ms

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

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