Remote MCP · Endpoint

OT Intel API MCP server

No. OT Intel API answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://ot-intel-api.onrender.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.No3men60/ot-intel-api
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
716 ms
Tools exposed
40 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
OT/ICS threat intel for AI agents: 40 tools, pay per call in USDC on Base via x402.
Listing
From the official MCP registry (active).
Recent checks of OT Intel API
CheckedResultHandshake
34 minutes agoHandshake completed716 ms
9 days agoHandshake completed320 ms
10 days agoHandshake completed157 ms
11 days agoHandshake completed123 ms
12 days agoHandshake completed116 ms
14 days agoHandshake completed167 ms
14 days agoHandshake completed153 ms
15 days agoHandshake completed183 ms
17 days agoHandshake completed259 ms
19 days agoHandshake completed303 ms
21 days agoHandshake completed266 ms
24 days agoHandshake completed275 ms
26 days agoHandshake completed375 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 OT Intel API and makes no claim about it beyond what these checks measured.