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
497 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Checks a counterparty before an AI agent pays: what the evidence supports, and for how much.
Listing
From the official MCP registry (active).
Recent checks of Fidren
CheckedResultHandshake
1 hour agoHandshake completed497 ms
2 days agoHandshake completed449 ms
4 days agoHandshake completed427 ms
5 days agoHandshake completed517 ms
7 days agoHandshake completed429 ms
8 days agoHandshake completed576 ms
9 days agoHandshake completed580 ms
12 days agoHandshake completed418 ms
13 days agoHandshake completed434 ms
15 days agoHandshake completed430 ms
17 days agoHandshake completed427 ms
18 days agoHandshake completed416 ms
19 days agoHandshake completed441 ms
20 days agoHandshake completed428 ms
21 days agoHandshake completed410 ms
21 days agoHandshake completed482 ms
23 days agoHandshake completed411 ms

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

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.