Remote MCP · Endpoint

Auralogs MCP server

No. Auralogs answered an MCP handshake 10 hours ago.

UpLast checked 10 hours ago

Server URL

https://mcp.auralogs.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.auralogs/auralogs
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
102 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Read-only access to Auralogs production logs: search logs, inspect errors, review AI analyses.
Listing
From the official MCP registry (active).
Recent checks of Auralogs
CheckedResultHandshake
10 hours agoHandshake completed102 ms
2 days agoHandshake completed121 ms
4 days agoHandshake completed113 ms
5 days agoHandshake completed88 ms
7 days agoHandshake completed129 ms
8 days agoHandshake completed112 ms
10 days agoHandshake completed67 ms
12 days agoHandshake completed106 ms
13 days agoHandshake completed76 ms
15 days agoHandshake completed89 ms
16 days agoHandshake completed78 ms
17 days agoHandshake completed74 ms
18 days agoHandshake completed96 ms
19 days agoHandshake completed71 ms
20 days agoHandshake completed81 ms
21 days agoHandshake completed33 ms
23 days agoHandshake completed99 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 Auralogs and makes no claim about it beyond what these checks measured.