Remote MCP · Endpoint

ACM-68000 signals for listed issuers MCP server

No. ACM-68000 signals for listed issuers answered an MCP handshake 16 hours ago.

UpLast checked 16 hours ago

Server URL

https://mcp.getissuer.ai/signals/mcp

The last check completed an MCP handshake.

Registry name
io.github.allooloo/acm-signals
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
38 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
The ACM-68000 signal of a listed security in its home market: trading, not listed, read the filing.
Listing
From the official MCP registry (active).
Recent checks of ACM-68000 signals for listed issuers
CheckedResultHandshake
16 hours agoHandshake completed38 ms
4 days agoHandshake completed57 ms
8 days agoHandshake completed77 ms
17 days agoHandshake completed81 ms
17 days agoHandshake completed53 ms
19 days agoHandshake completed46 ms
20 days agoHandshake completed311 ms
21 days agoHandshake completed405 ms
22 days agoHandshake completed82 ms
22 days agoHandshake completed186 ms
24 days agoHandshake completed122 ms
27 days agoHandshake completed188 ms
29 days agoHandshake completed272 ms

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

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 ACM-68000 signals for listed issuers and makes no claim about it beyond what these checks measured.