mcpbeat Sign in

Condux error monitoring MCP Server

answering

Condux error monitoring is answering right now. Last checked 7 min ago. Last commit 13 Oct 2026.

Read your Condux issues, events and stack traces (deminified with source maps). Triage optional.

Uptime history 64 hours of history
64 hours agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
134 ms
Response time
average over 24h
0
Stars
last commit 13 Oct 2026

What the code does

We read the source, 1 d ago · rules ccca72095570

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

                        $"{DashboardUrl(cfg, state.ReturnPath, "select")}"
                        + $"&selection={Uri.EscapeDataString(selection)}");
        var start = new ProcessStartInfo(options.LlvmSymbolizerPath)
Includes a file named by a variable sdks/php/src/autoload.php:16
        require $path;
Asks for container control access backend/src/Condux.Agent/Sandbox/SandboxOptions.cs:29
    public const string DefaultEndpoint = "unix:///var/run/docker.sock";

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

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 7 min ago.

run in your terminal
claude mcp add mcp --transport http https://app.condux.ai/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://app.condux.ai/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://app.condux.ai/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://app.condux.ai/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://app.condux.ai/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints

URLTransportStateLatencyChecked
https://app.condux.ai/api/mcp streamable-http needs key 128 ms 7 min ago

Alternatives to Condux error monitoring

same job, measured the same way
Sourcemap Retrace MCP
by vola-trebla

Decodes minified production stack traces back to original TypeScript source using source maps.

29 installs/wk local only
Sentry MCP
by getsentry

MCP server for Sentry - error monitoring, issue tracking, and debugging for AI assistants

92 171 installs/wk answering
Source Map Parser MCP
by masonchow

Parse JavaScript error stack traces back to original source code using source maps

47 installs/wk local only
Signal Bureau
by evolutionlabs-dev

SigB (Signal Bureau): maintained, source-traced record of entities and events in your named domain.

29 tools answering
Raygun
by mindscapehq

Investigate errors, track deployments, analyze performance, and manage application monitoring

answering
RealUptime
by realuptime

RealUptime monitors, incidents, status pages, Errors issues, and free third-party outage checks.

7 tools answering
StackShield
by stackshield

External security monitoring for Laravel apps: list domains, trigger scans, read issues and fixes.

answering
Flare
by flareapp

Error tracking for Laravel and PHP apps. Let your agent fetch errors, stack traces and context.

answering

Condux error monitoring — questions

Answers built from our own checks of this server.

Why is there no tool list for Condux error monitoring?
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 Condux error monitoring working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 134 ms. The bar chart above shows every period we have measured.
How do I connect Condux error monitoring?
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 key: it refuses anonymous clients.
Does Condux error monitoring need an API key?
Yes. Every time we knock, Condux error monitoring 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 Condux error monitoring?
It answers our handshake in 134 ms on average, which is faster than 78% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Condux error monitoring open source?
We cannot say either way: written in C# and 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.