Skip to content
anlyon.dev

Airbrake MCP by usefulapi

io.usefulapi/airbrakeusefulapi.iostreamable-httpv1.7.4Scanned

Read Airbrake projects, error groups, notices, deploys and stats; mute or unmute error groups.

13 tools: 1 can delete or cancel things, 1 change things and 11 only read.

Tools: 1 delete, 0 irreversible, 1 write, 11 read.
  • Reads private data · 5
  • Reads text others write · 4
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →
Compare with similar serversMarkdownJSONReport this listing

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

13 tools

Deletes or cancels 1Claude Code: deny
  • airbrake_mute_groupWRITE: mute one error group.No findings

    Why it is in this group

    • The description's first verb is "write": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE: mute one error group. Airbrake removes it from the default error list and stops ALL notifications for it (email, Slack and other integrations) until it is unmuted. Notices are still recorded. Reversible with airbrake_unmute_group. Airbrake API: PUT /api/v4/projects/{project_id}/groups/{group_id}/muted.

    Annotations the server declares

    • title: Mute an error group
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
Changes things 1Claude Code: ask
  • airbrake_unmute_groupWRITE: unmute one error group, so it is back in the default error list and its notifications resume.No findings

    Why it is in this group

    • The description's first verb is "write": a word for a change.
    Description, as the server wrote it
    WRITE: unmute one error group, so it is back in the default error list and its notifications resume. Airbrake API: PUT /api/v4/projects/{project_id}/groups/{group_id}/unmuted.

    Annotations the server declares

    • title: Unmute an error group
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
Only reads 11Show 11 read-only tools
  • airbrake_get_deployGet one deploy: environment, deployer, repository, revision and version.Reads private dataNo findings

    Why it is in this group

    • The name "airbrake_get_deploy" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "get" and "repository": it reads repositories.
    Description, as the server wrote it
    Get one deploy: environment, deployer, repository, revision and version. Airbrake API: GET /api/v4/projects/{project_id}/deploys/{deploy_id}.

    Annotations the server declares

    • title: Get a deploy
    • readOnlyHint: true
  • airbrake_get_groupGet one error group in full: resolved flag, every error with its complete backtrace (file, function, line, column), context, last deploy, last notice id/time, notice counts and cre…Reads private dataNo findings

    Why it is in this group

    • The name "airbrake_get_group" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "get" and "file": it reads files.
    Description, as the server wrote it
    Get one error group in full: resolved flag, every error with its complete backtrace (file, function, line, column), context, last deploy, last notice id/time, notice counts and creation time. Airbrake API: GET /api/v4/projects/{project_id}/groups/{group_id}.

    Annotations the server declares

    • title: Get an error group
    • readOnlyHint: true
  • airbrake_get_group_statsOccurrence counts over time for one error group: parallel arrays `time`, `accepted` (notices counted) and `limited` (dropped by rate limits), aggregated per period, from `since` un…No findings

    Why it is in this group

    • The name "airbrake_get_group_stats" says "get": a word for reading.
    Description, as the server wrote it
    Occurrence counts over time for one error group: parallel arrays `time`, `accepted` (notices counted) and `limited` (dropped by rate limits), aggregated per period, from `since` until `until` (default now). Use it to see whether an error is spiking or fading. Airbrake API: GET /api/v5/projects/{project_id}/groups/{group_id}/stats.

    Annotations the server declares

    • title: Get error group statistics
    • readOnlyHint: true
  • airbrake_get_notice_statusCheck what happened to a reported error, by the notice id that Airbrake's create-notice API returned: code = processed (groupId = its error group), rejected (message = why, e.g.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "airbrake_get_notice_status" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "message": it reads messages.
    • untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.
    Description, as the server wrote it
    Check what happened to a reported error, by the notice id that Airbrake's create-notice API returned: code = processed (groupId = its error group), rejected (message = why, e.g. an app-version filter), archived (past retention) or not_found (unknown or still processing). Airbrake API: GET /api/v4/projects/{project_id}/notice-status/{notice_id}.

    Annotations the server declares

    • title: Get a notice's processing status
    • readOnlyHint: true
  • airbrake_get_projectGet one Airbrake project: name, last deploy id/time, notice total, rejection count, deploy count and resolved/unresolved error-group counts.No findings

    Why it is in this group

    • The name "airbrake_get_project" says "get": a word for reading.
    Description, as the server wrote it
    Get one Airbrake project: name, last deploy id/time, notice total, rejection count, deploy count and resolved/unresolved error-group counts. Airbrake API: GET /api/v4/projects/{project_id}.

    Annotations the server declares

    • title: Get a project
    • readOnlyHint: true
  • airbrake_get_project_statsError volume over time for a whole project: parallel arrays `time`, `accepted` (notices counted), `limited` (dropped by rate limits) and `overQuota` (dropped over the plan quota), …No findings

    Why it is in this group

    • The name "airbrake_get_project_stats" says "get": a word for reading.
    Description, as the server wrote it
    Error volume over time for a whole project: parallel arrays `time`, `accepted` (notices counted), `limited` (dropped by rate limits) and `overQuota` (dropped over the plan quota), aggregated per period (1m, 5m, 15m, 30m, 2h, 3h, 6h, 12h, 24h). Airbrake API: GET /api/v5/projects/{project_id}/stats.

    Annotations the server declares

    • title: Get project statistics
    • readOnlyHint: true
  • airbrake_list_activitiesList a project's activity feed: who did what and when (for example group.resolved), with user name, activity, the affected object (trackableType/trackableId) and timestamps.No findings

    Why it is in this group

    • The name "airbrake_list_activities" says "list": a word for reading.
    Description, as the server wrote it
    List a project's activity feed: who did what and when (for example group.resolved), with user name, activity, the affected object (trackableType/trackableId) and timestamps. Airbrake API: GET /api/v4/projects/{project_id}/activities.

    Annotations the server declares

    • title: List project activity
    • readOnlyHint: true
  • airbrake_list_deploysList a project's tracked deploys: environment, username/email of the deployer, repository, revision (commit) and version.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "airbrake_list_deploys" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    List a project's tracked deploys: environment, username/email of the deployer, repository, revision (commit) and version. Use it to correlate new errors with a release. Airbrake API: GET /api/v4/projects/{project_id}/deploys.

    Annotations the server declares

    • title: List deploys
    • readOnlyHint: true
  • airbrake_list_groupsList a project's error groups ("errors" in the Airbrake app): each with id, resolved flag, error type/message/backtrace, context (environment, severity, component/action), last not…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "airbrake_list_groups" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "message": it reads messages.
    • untrusted-inputThe description's first sentence says "list" and "message": it reads messages, which other people can write.
    Description, as the server wrote it
    List a project's error groups ("errors" in the Airbrake app): each with id, resolved flag, error type/message/backtrace, context (environment, severity, component/action), last notice time, notice counts and last deploy. Sorted by last notice by default; order by notice_count, weight or created instead. Filter by deploy, archived or muted groups, or creation time. Backtraces are cut to the first 5 frames (set full_backtraces for all; airbrake_get_group shows one group in full). Airbrake API: GET /api/v4/projects/{project_id}/groups.

    Annotations the server declares

    • title: List error groups
    • readOnlyHint: true
  • airbrake_list_noticesList the individual occurrences (notices) of one error group, newest first: each with id, deploy, errors and backtrace, context (environment, hostname, app version, user, URL, seve…Reads text others writeNo findings

    Why it is in this group

    • The name "airbrake_list_notices" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    List the individual occurrences (notices) of one error group, newest first: each with id, deploy, errors and backtrace, context (environment, hostname, app version, user, URL, severity, notifier), environment, session and request params, and created time. Optionally only notices of one app version. Backtraces are cut to the first 10 frames unless full_backtraces is set. Airbrake API: GET /api/v4/projects/{project_id}/groups/{group_id}/notices.

    Annotations the server declares

    • title: List notices of an error group
    • readOnlyHint: true
  • airbrake_list_projectsList the Airbrake projects your user can see, with id, name, last deploy, notice total, rejected count, deploy count and resolved/unresolved error-group counts.No findings

    Why it is in this group

    • The name "airbrake_list_projects" says "list": a word for reading.
    Description, as the server wrote it
    List the Airbrake projects your user can see, with id, name, last deploy, notice total, rejected count, deploy count and resolved/unresolved error-group counts. Start here to get a project_id. Airbrake API: GET /api/v4/projects.

    Annotations the server declares

    • title: List projects
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data5
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Oct 22, 2026, 15:21 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://airbrake.usefulapi.io/.well-known/oauth-protected-resource/mcp
Authorization servers
https://airbrake.usefulapi.io
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 destructive, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://airbrake.usefulapi.io/mcp: tools/list returned 13 tools to an anonymous client, including airbrake_mute_group (destructive), airbrake_unmute_group (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

All changes to this server

Install

Pinned to version 1.7.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http airbrake https://airbrake.usefulapi.io/mcp
claude mcp add --transport http airbrake https://airbrake.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__airbrake__airbrake_list_projects",
      "mcp__airbrake__airbrake_get_project",
      "mcp__airbrake__airbrake_list_groups",
      "mcp__airbrake__airbrake_get_group",
      "mcp__airbrake__airbrake_get_group_stats",
      "mcp__airbrake__airbrake_list_notices",
      "mcp__airbrake__airbrake_get_notice_status",
      "mcp__airbrake__airbrake_list_deploys",
      "mcp__airbrake__airbrake_get_deploy",
      "mcp__airbrake__airbrake_list_activities",
      "mcp__airbrake__airbrake_get_project_stats"
    ],
    "ask": [
      "mcp__airbrake__airbrake_unmute_group"
    ],
    "deny": [
      "mcp__airbrake__airbrake_mute_group"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as airbrake. Review it before you use it.

Capability tags behind 6 rules
  • mcp__airbrake__airbrake_list_groups private-data, untrusted-input
  • mcp__airbrake__airbrake_get_group private-data
  • mcp__airbrake__airbrake_list_notices untrusted-input
  • mcp__airbrake__airbrake_get_notice_status private-data, untrusted-input
  • mcp__airbrake__airbrake_list_deploys private-data, untrusted-input
  • mcp__airbrake__airbrake_get_deploy private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/io.usefulapi/airbrake/verify?hash=3e03c82d422d020c9018f241c038b0e59c0fb34b5aff6496834a56c5761814b6" | jq -e '.changed == false'

Pinned hash 3e03c82d422d, from Oct 22, 2026, 11:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.usefulapi/airbrake/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

anlyon.dev badge for io.usefulapi/airbrake
[![anlyon.dev](https://anlyon.dev/badge/io.usefulapi/airbrake.svg)](https://anlyon.dev/servers/io.usefulapi/airbrake)

Source: MCP Registry · repository. Synced Oct 22, 2026, 11:18 UTC.