mcpbeat Sign in

NEXUS AGI MCP Server

by eblas-nexus Your server? Claim it
answering

NEXUS AGI is answering right now. Last checked 3 min ago.

Keeps AI agents from repeating costly mistakes: past decisions, rules and incidents, shared by all.

Uptime history 30 days of history · worst day 97%
30 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
686 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

NEXUS AGI missed 2 checks this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add nexus-agi --transport http https://nexus.eblas.link/mcp
Settings → Connectors → Add custom connector, then paste this address
https://nexus.eblas.link/mcp
~/.codex/config.toml
[mcp_servers.nexus-agi]
url = "https://nexus.eblas.link/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "nexus-agi": {
      "url": "https://nexus.eblas.link/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "nexus-agi": {
      "type": "http",
      "url": "https://nexus.eblas.link/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://nexus.eblas.link/mcp streamable-http sign-in 691 ms 3 min ago

Alternatives to NEXUS AGI

same job, measured the same way
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
WardenPoint
by wardenpoint

Configure on-call alerting from an AI agent: recipients, groups, escalation policies, schedules.

36 installs/wk local only
Statuser
by statuser-cloud

Monitor services, manage incidents and status pages in Statuser.cloud from your AI assistant.

116 installs/wk answering
Pagerduty
by mcparmory

Manage incidents, on-call schedules, escalation policies, and alert notifications

222 installs/wk local only
Rootly
by rootly

Incident management, on-call scheduling, and intelligent analysis powered by Rootly.

1 904 installs/wk answering
Openuptime
by openuptime

Manage uptime monitors, incidents and status pages from any MCP client.

answering
hiveWiki
by hivewiki

Shared project wiki for AI agents: read and write pages, next actions, and activity logs over MCP.

answering

NEXUS AGI — questions

Answers built from our own checks of this server.

Why is there no tool list for NEXUS AGI?
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: 100.0% of checks in the last 24 hours got a reply.
Is NEXUS AGI working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 686 ms. The bar chart above shows every period we have measured.
How do I connect NEXUS AGI?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to NEXUS AGI?
No API key is involved. NEXUS AGI answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is NEXUS AGI?
It answers our handshake in 686 ms on average, which is faster than 14% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.