Remote MCP · Endpoint

Philidor DeFi Vault Risk Analytics MCP server

No. Philidor DeFi Vault Risk Analytics answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.philidor.io/api/mcp

The last check completed an MCP handshake.

Registry name
io.philidor/defi-vaults
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
428 ms
Tools exposed
24 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search 700+ DeFi vaults, compare risk scores, analyze protocols. No API key needed.
Listing
From the official MCP registry (active).
Recent checks of Philidor DeFi Vault Risk Analytics
CheckedResultHandshake
1 hour agoHandshake completed428 ms
9 days agoHandshake completed634 ms
10 days agoHandshake completed471 ms
11 days agoHandshake completed334 ms
12 days agoHandshake completed487 ms
14 days agoHandshake completed403 ms
14 days agoHandshake completed553 ms
15 days agoHandshake completed439 ms
17 days agoHandshake completed486 ms
19 days agoHandshake completed873 ms
21 days agoHandshake completed371 ms
24 days agoHandshake completed959 ms
26 days agoHandshake completed391 ms
28 days agoHandshake completed807 ms

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

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 Philidor DeFi Vault Risk Analytics and makes no claim about it beyond what these checks measured.