Remote MCP · Endpoint
Fidren MCP server
No. Fidren answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.fidren.net/mcp
The last check completed an MCP handshake.
- Registry name
- net.fidren/counterparty
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 475 ms
- Tools exposed
- 1 tool
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Checks a counterparty before an AI agent pays: what the evidence supports, and for how much.
- Website
- https://fidren.net/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 475 ms |
| 1 day ago | Handshake completed | 459 ms |
| 2 days ago | Handshake completed | 835 ms |
| 3 days ago | Handshake completed | 499 ms |
| 4 days ago | Handshake completed | 508 ms |
| 5 days ago | Handshake completed | 525 ms |
| 6 days ago | Handshake completed | 533 ms |
| 8 days ago | Handshake completed | 460 ms |
| 11 days ago | Handshake completed | 445 ms |
| 13 days ago | Handshake completed | 566 ms |
| 16 days ago | Handshake completed | 559 ms |
| 18 days ago | Handshake completed | 422 ms |
| 20 days ago | Handshake completed | 497 ms |
| 22 days ago | Handshake completed | 449 ms |
| 24 days ago | Handshake completed | 427 ms |
| 26 days ago | Handshake completed | 517 ms |
| 27 days ago | Handshake completed | 429 ms |
| 29 days ago | Handshake completed | 576 ms |
| 30 days ago | Handshake completed | 580 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 Fidren and makes no claim about it beyond what these checks measured.