Remote MCP · Endpoint

DirectIQ MCP server

No. DirectIQ answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://mcp.directiq.com/mcp

The last check completed an MCP handshake.

Registry name
com.directiq.mcp/directiq
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
27 ms
Tools exposed
30 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Manage DirectIQ contacts, lists and tags, see campaign results, and send transactional email.
Listing
From the official MCP registry (active).
Recent checks of DirectIQ
CheckedResultHandshake
20 minutes agoHandshake completed27 ms
3 days agoHandshake completed29 ms
14 days agoHandshake completed22 ms
14 days agoHandshake completed21 ms
15 days agoHandshake completed30 ms
16 days agoHandshake completed25 ms
18 days agoHandshake completed22 ms
18 days agoHandshake completed30 ms
19 days agoHandshake completed24 ms
21 days agoHandshake completed24 ms
22 days agoHandshake completed27 ms
25 days agoHandshake completed29 ms
27 days agoHandshake completed21 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 DirectIQ and makes no claim about it beyond what these checks measured.