Remote MCP · Endpoint

FOXIFY Agent Commerce MCP server

No. FOXIFY Agent Commerce answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://foxify.pro/mcp

The last check completed an MCP handshake.

Registry name
pro.foxify/agent-commerce
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
2.98 s
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Hosted x402 preflight for action authority, payment mandate, destination, expiry and replay.
Listing
From the official MCP registry (active).
Recent checks of FOXIFY Agent Commerce
CheckedResultHandshake
2 hours agoHandshake completed2.98 s
2 days agoHandshake completed927 ms
4 days agoHandshake completed716 ms
7 days agoHandshake completed937 ms
9 days agoHandshake completed820 ms
11 days agoHandshake completed894 ms
13 days agoHandshake completed952 ms
15 days agoHandshake completed1.74 s
16 days agoHandshake completed1.10 s
18 days agoHandshake completed875 ms
19 days agoHandshake completed844 ms
20 days agoHandshake completed1.10 s
23 days agoHandshake completed888 ms
24 days agoHandshake completed848 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 FOXIFY Agent Commerce and makes no claim about it beyond what these checks measured.