Remote MCP · Endpoint

Axint MCP server

No. Axint answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://mcp.axint.ai/mcp

The last check completed an MCP handshake.

Registry name
io.github.agenticempire/axint
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
119 ms
Tools exposed
36 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Proof and repair for Apple coding agents: validate Swift, run Xcode evidence, and repair failures.
Listing
From the official MCP registry (active).
Recent checks of Axint
CheckedResultHandshake
7 hours agoHandshake completed119 ms
2 days agoHandshake completed82 ms
4 days agoHandshake completed57 ms
5 days agoHandshake completed63 ms
7 days agoHandshake completed138 ms
8 days agoHandshake completed88 ms
9 days agoHandshake completed74 ms
12 days agoHandshake completed130 ms
13 days agoHandshake completed82 ms
15 days agoHandshake completed129 ms
16 days agoHandshake completed28 ms
17 days agoHandshake completed37 ms
19 days agoHandshake completed70 ms
19 days agoHandshake completed32 ms
20 days agoHandshake completed73 ms
21 days agoHandshake completed55 ms
22 days agoHandshake completed56 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 Axint and makes no claim about it beyond what these checks measured.