AgentNX MCP Server

by iamwi11 Your server? Claim it

answering

AgentNX is answering right now. Last checked 1 min ago.

AI agents for federal IT & pharma: alert triage, ICAM, helpdesk, incidents, ticket routing.

Uptime history 51 days of history · worst day 97%

51 days agonow

97.8%

Uptime 24h

89 of 91 checks

—

Tools

hidden behind auth

189 ms

Response time

average over 24h

authentication required

Access

streamable-http

AgentNX does not always answer

Over the last week it answered 99.1% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add agentnx --transport http https://www.agentnx.ai/api/mcp-server

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "agentnx": {
      "url": "https://www.agentnx.ai/api/mcp-server"
    }
  }
}

~/.codex/config.toml

[mcp_servers.agentnx]
url = "https://www.agentnx.ai/api/mcp-server"

.cursor/mcp.json

{
  "mcpServers": {
    "agentnx": {
      "url": "https://www.agentnx.ai/api/mcp-server"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "agentnx": {
      "url": "https://www.agentnx.ai/api/mcp-server"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URL	Transport	State	Latency	Checked
https://www.agentnx.ai/api/mcp-server	streamable-http	needs auth	327 ms	1 min ago

Alternatives to AgentNX

same job, measured the same way

RocketCyber

by wyre-technology

MCP server for RocketCyber Managed SOC — incidents, alerts, agents, and customer telemetry.

local only

RocketCyber

by wyre-ai

MCP server for RocketCyber Managed SOC — incidents, alerts, agents, and customer telemetry.

local only

AlertOps

by wyre-ai

MCP server for AlertOps' incident alerting/on-call API.

local only

Rootly

by wyre-technology

MCP server for Rootly — incidents, alerts, escalations, and post-incident reports.

local only

Rootly

by wyre-ai

MCP server for Rootly — incidents, alerts, escalations, and post-incident reports.

local only

Dora Compliance MCP

by csoai-org

DORA (EU Digital Operational Resilience Act) compliance for AI agents. 5-pillar audit, incident ...

466 installs/wk local only

Ironscales

by wyre-ai

MCP server for Ironscales phishing incident management — incidents, mailboxes, and reporting.

local only

Ironscales

by wyre-technology

MCP server for Ironscales phishing incident management — incidents, mailboxes, and reporting.

local only

AgentNX — questions

Answers built from our own checks of this server.

Why is there no tool list for AgentNX?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 97.8% of checks in the last 24 hours got a reply.

Is AgentNX working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 89 of 91 checks got a reply (97.8%), average response time 189 ms. The bar chart above shows every period we have measured.

How do I connect AgentNX?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.

Does AgentNX need an API key?

Yes. Every time we knock, AgentNX answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is AgentNX?

It answers our handshake in 189 ms on average, which is faster than 71% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.