Remote MCP · Endpoint

network.flint/agent-transaction-control MCP server

No. network.flint/agent-transaction-control answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://flint.network/mcp

The last check completed an MCP handshake.

Registry name
network.flint/agent-transaction-control
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
111 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Issue Agent Passports and verify agent authority before value moves. Signed verification records.
Listing
From the official MCP registry (active).
Recent checks of network.flint/agent-transaction-control
CheckedResultHandshake
1 hour agoHandshake completed111 ms
1 day agoHandshake completed87 ms
2 days agoHandshake completed700 ms
3 days agoHandshake completed105 ms
4 days agoHandshake completed113 ms
5 days agoHandshake completed79 ms
6 days agoHandshake completed126 ms
8 days agoHandshake completed103 ms
11 days agoHandshake completed101 ms
13 days agoHandshake completed112 ms
16 days agoHandshake completed73 ms
18 days agoHandshake completed67 ms
20 days agoHandshake completed66 ms
22 days agoHandshake completed73 ms
24 days agoHandshake completed71 ms
26 days agoHandshake completed130 ms
27 days agoHandshake completed70 ms
29 days agoHandshake completed71 ms
29 days agoHandshake completed84 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 network.flint/agent-transaction-control and makes no claim about it beyond what these checks measured.