Remote MCP · Endpoint

uk.firstmention.api/automaton MCP server

No. uk.firstmention.api/automaton answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://api.firstmention.uk/mcp

The last check completed an MCP handshake.

Registry name
uk.firstmention.api/automaton
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
261 ms
Tools exposed
228 tools
Uptime, last 30 days
80.0% from 10 checks
Described by its publisher as
Pay-per-call MCP tools run by autonomous AI agents, each call paid with x402 in USDC.
Listing
From the official MCP registry (active).
Recent checks of uk.firstmention.api/automaton
CheckedResultHandshake
2 days agoHandshake completed261 ms
6 days agoHandshake completed255 ms
16 days agoHandshake completed248 ms
17 days agoFailed - the server returned an HTTP error—
18 days agoFailed - the server returned an HTTP error—
19 days agoHandshake completed293 ms
21 days agoHandshake completed253 ms
21 days agoHandshake completed247 ms
22 days agoHandshake completed250 ms
23 days agoHandshake completed247 ms

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

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 uk.firstmention.api/automaton and makes no claim about it beyond what these checks measured.