Remote MCP · Endpoint

AITWIRE MCP server

No. AITWIRE answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://api.aitwire.com/mcp

The last check completed an MCP handshake.

Registry name
com.aitwire/authority
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
826 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Business-published entity records with confirmation dates: look up, page feeds, check claims.
Listing
From the official MCP registry (active).
Recent checks of AITWIRE
CheckedResultHandshake
9 hours agoHandshake completed826 ms
2 days agoHandshake completed841 ms
4 days agoHandshake completed825 ms
6 days agoHandshake completed438 ms
7 days agoHandshake completed1.07 s
8 days agoHandshake completed982 ms
9 days agoHandshake completed887 ms
12 days agoHandshake completed758 ms
14 days agoHandshake completed412 ms
15 days agoHandshake completed883 ms
16 days agoHandshake completed113 ms
18 days agoHandshake completed87 ms
19 days agoHandshake completed368 ms
19 days agoHandshake completed391 ms
20 days agoHandshake completed486 ms
21 days agoHandshake completed425 ms
23 days agoHandshake completed385 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 AITWIRE and makes no claim about it beyond what these checks measured.