Airbrake MCP Server
NPM · AIRBRAKE-MCP-SERVER · SCANNED SEP 20
Query Airbrake errors, notices, deploys, and project stats from MCP clients
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 171 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 792 tokens (~49/item across 16 items; 16 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "create_deploy" implies "deploy" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Airbrake MCP Server server?
Airbrake MCP Server runs locally as an npm package, launched with npx -y airbrake-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · airbrake-mcp-server
claude mcp add dach3r-airbrake-mcp-server -- npx -y airbrake-mcp-server
{
"mcpServers": {
"dach3r-airbrake-mcp-server": {
"command": "npx",
"args": [
"-y",
"airbrake-mcp-server"
]
}
}
} {
"servers": {
"dach3r-airbrake-mcp-server": {
"command": "npx",
"args": [
"-y",
"airbrake-mcp-server"
]
}
}
} codex mcp add dach3r-airbrake-mcp-server -- npx -y airbrake-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dach3r-airbrake-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"airbrake-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add dach3r-airbrake-mcp-server --command npx --arg -y --arg airbrake-mcp-server
mcp_servers:
dach3r-airbrake-mcp-server:
command: "npx"
args: ["-y", "airbrake-mcp-server"] {
"McpServers": {
"dach3r-airbrake-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"airbrake-mcp-server"
]
}
}
} assistant mcp add dach3r-airbrake-mcp-server -t stdio -c npx -a -y airbrake-mcp-server
{
"mcpServers": {
"dach3r-airbrake-mcp-server": {
"command": "npx",
"args": [
"-y",
"airbrake-mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 −3
- Stability: pass → 0.80 functional
- 14 Sept 26 +1
- Stability: 0.97 → pass security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 −3
- Stability: pass → 0.80 functional
- 7 Sept 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/airbrake-mcp-server@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_error_comment ~40
Add a comment to an error group
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Comment text |
| error_id | string | yes | The ID of the error group |
No output schema declared.
No examples provided.
create_deploy ~76
Create a deployment notification in Airbrake
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | yes | Environment name (e.g., production, staging) |
| repository | string | – | Repository URL |
| revision | string | – | Git revision/commit hash |
| username | string | – | Username of person deploying |
| version | string | – | Version being deployed |
No output schema declared.
No examples provided.
filter_errors_by_status ~58
Filter errors by their status (open, resolved, ignored)
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | Filter by environment |
| limit | number | – | Number of results (default: 20) |
| status | string | yes | Filter by error status |
No output schema declared.
No examples provided.
get_error_comments ~32
Get all comments for a specific error group
| Name | Type | Req | Description |
|---|---|---|---|
| error_id | string | yes | The ID of the error group |
No output schema declared.
No examples provided.
get_error_details ~62
Get comprehensive information about a specific error group including all occurrences, stack traces, and metadata
| Name | Type | Req | Description |
|---|---|---|---|
| error_id | string | yes | The ID of the error group to retrieve |
| include_notices | boolean | – | Include individual error occurrences/notices (default: true) |
No output schema declared.
No examples provided.
get_error_notices ~66
Get all individual occurrences (notices) of a specific error group with full stack traces and context
| Name | Type | Req | Description |
|---|---|---|---|
| error_id | string | yes | The ID of the error group |
| limit | number | – | Number of notices to return (default: 10, max: 100) |
No output schema declared.
No examples provided.
get_error_trend ~65
Get occurrence trend data for a specific error over time
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | End date in ISO format (optional) |
| error_id | string | yes | The ID of the error group |
| start_date | string | – | Start date in ISO format (optional) |
No output schema declared.
No examples provided.
get_notice_details ~47
Get complete details of a specific error occurrence including full stack trace, parameters, session, and environment data
| Name | Type | Req | Description |
|---|---|---|---|
| notice_id | string | yes | The ID of the specific error occurrence/notice |
No output schema declared.
No examples provided.
get_project_stats ~16
Get project statistics and health metrics
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ignore_error ~29
Mark an error as ignored
| Name | Type | Req | Description |
|---|---|---|---|
| error_id | string | yes | The ID of the error to ignore |
No output schema declared.
No examples provided.
link_error_to_issue ~56
Link an error group to an external issue tracker (GitHub, Jira, etc.)
| Name | Type | Req | Description |
|---|---|---|---|
| error_id | string | yes | The ID of the error group |
| issue_url | string | yes | URL of the issue in external tracker |
No output schema declared.
No examples provided.
list_deploys ~35
List recent deployments for the project
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Number of deploys to return (default: 10) |
No output schema declared.
No examples provided.
list_errors ~78
List errors from Airbrake project. Returns recent errors with their details.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | Filter by environment (e.g., production, staging) |
| limit | number | – | Number of errors to return (default: 20, max: 100) |
| page | number | – | Page number for pagination (default: 1) |
No output schema declared.
No examples provided.
reopen_error ~31
Reopen a resolved or ignored error
| Name | Type | Req | Description |
|---|---|---|---|
| error_id | string | yes | The ID of the error to reopen |
No output schema declared.
No examples provided.
resolve_error ~29
Mark an error as resolved
| Name | Type | Req | Description |
|---|---|---|---|
| error_id | string | yes | The ID of the error to resolve |
No output schema declared.
No examples provided.
search_errors ~72
Search errors by text query, filtering by message, class, file, or any text content
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | Filter by environment |
| limit | number | – | Number of results (default: 20) |
| query | string | yes | Search query to match against error messages, classes, files, etc. |
No output schema declared.
No examples provided.
What is the Airbrake MCP Server server?
Airbrake MCP Server is listed in the public MCP registry as io.github.Dach3r/airbrake-mcp-server. Query Airbrake errors, notices, deploys, and project stats from MCP clients. This page covers its npm package (airbrake-mcp-server).
Is the Airbrake MCP Server server safe to use?
Airbrake MCP Server scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Airbrake MCP Server server expose?
Airbrake MCP Server exposes 16 tools: list_errors, get_error_details, get_error_notices, get_notice_details, search_errors, and 11 more. Their descriptions and schemas cost roughly 792 tokens of context every time the server is loaded.
Is the Airbrake MCP Server server still maintained?
Airbrake MCP Server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Airbrake MCP Server server under?
Airbrake MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.