ForgeOps is answering right now. Last checked 13 min ago.
Production errors and incidents for your agent: stack traces, breadcrumbs, likely causes, triage.
Today is the operative word: we check ForgeOps every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.
claude mcp add forgeops --transport http https://getforgeops.net/api/v1/mcp
https://getforgeops.net/api/v1/mcp
[mcp_servers.forgeops]
url = "https://getforgeops.net/api/v1/mcp"
{
"mcpServers": {
"forgeops": {
"url": "https://getforgeops.net/api/v1/mcp"
}
}
}
{
"servers": {
"forgeops": {
"type": "http",
"url": "https://getforgeops.net/api/v1/mcp"
}
}
}
This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://getforgeops.net/api/v1/mcp | streamable-http | needs auth | 324 ms | 13 min ago |
Exception tracking for .NET. Let your AI coding agent search and triage errors and stack traces.
Production errors your coding agent can read: search, stack traces, context, trends, resolve.
Error tracking for Laravel and PHP apps. Let your agent fetch errors, stack traces and context.
Read LogBrew errors, slow traces, logs, and product analytics, and triage issues with consent.
Read your Condux issues, events and stack traces (deminified with source maps). Triage optional.
Your coding agent adds Probecast uptime monitors and reads incidents for projects you ship.
Ask your AI what's broken: incidents, monitors, servers, logs, errors and traces from Vigil.
Production telemetry for NestJS apps: traces, errors, regressions, jobs and alerts.
Answers built from our own checks of this server.