Remote MCP · Endpoint

io.github.gigshow/decker MCP server

No. io.github.gigshow/decker answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.decker-ai.com/api/v1/mcp

The last check completed an MCP handshake.

Registry name
io.github.gigshow/decker
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
301 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Deterministic market-state engine for trading agents — state, gate, coordinates, with receipts.
Listing
From the official MCP registry (active).
Recent checks of io.github.gigshow/decker
CheckedResultHandshake
1 hour agoHandshake completed301 ms
1 day agoHandshake completed256 ms
2 days agoHandshake completed285 ms
3 days agoHandshake completed356 ms
4 days agoHandshake completed276 ms
5 days agoHandshake completed301 ms
6 days agoHandshake completed277 ms
9 days agoHandshake completed267 ms
11 days agoHandshake completed283 ms
14 days agoHandshake completed265 ms
16 days agoHandshake completed378 ms
18 days agoHandshake completed352 ms
20 days agoHandshake completed319 ms
22 days agoHandshake completed267 ms
24 days agoHandshake completed279 ms
26 days agoHandshake completed264 ms
27 days agoHandshake completed952 ms
29 days agoHandshake completed264 ms

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

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 io.github.gigshow/decker and makes no claim about it beyond what these checks measured.