Remote MCP · Endpoint

Basis Protocol MCP server

No. Basis Protocol answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://basisprotocol.xyz/mcp

The last check completed an MCP handshake.

Registry name
io.github.basis-protocol/basis
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
40 ms
Tools exposed
7 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Attested risk scores for stablecoins, DeFi protocols and wallets, with receipts.
Listing
From the official MCP registry (active).
Recent checks of Basis Protocol
CheckedResultHandshake
8 hours agoHandshake completed40 ms
2 days agoHandshake completed24 ms
4 days agoHandshake completed47 ms
6 days agoHandshake completed27 ms
8 days agoHandshake completed38 ms
10 days agoHandshake completed25 ms
12 days agoHandshake completed27 ms
13 days agoHandshake completed35 ms
14 days agoHandshake completed25 ms
16 days agoHandshake completed33 ms
18 days agoHandshake completed96 ms
20 days agoHandshake completed100 ms
22 days agoHandshake completed134 ms
23 days agoFailed - the check failed for an unclassified reason—

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 13 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 Basis Protocol and makes no claim about it beyond what these checks measured.