Remote MCP · Endpoint

AssetFare USDC Bridge MCP server

No. AssetFare USDC Bridge answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.assetfare.dev/mcp/bridge

The last check completed an MCP handshake.

Registry name
io.github.assetfare/assetfare-bridge
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
454 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Exact-amount top-two routing for six pilots; caller signs; AssetFare never signs or submits
Listing
From the official MCP registry (active).
Recent checks of AssetFare USDC Bridge
CheckedResultHandshake
1 hour agoHandshake completed454 ms
2 days agoHandshake completed588 ms
4 days agoHandshake completed502 ms
6 days agoHandshake completed507 ms
8 days agoHandshake completed504 ms
10 days agoHandshake completed506 ms
12 days agoHandshake completed503 ms
14 days agoHandshake completed506 ms
15 days agoHandshake completed507 ms
16 days agoHandshake completed509 ms
17 days agoHandshake completed501 ms
20 days agoHandshake completed536 ms
22 days agoHandshake completed507 ms
23 days agoHandshake completed503 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 AssetFare USDC Bridge and makes no claim about it beyond what these checks measured.