Model Context Protocol server for Rollbar
Nothing to run from here
SIGNL4 MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
18
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Read SIGNL4 alerts, teams, users and duty schedules; raise, acknowledge, close and annotate alerts.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http signl4-mcp-by-usefulapi https://signl4.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# signl4_list_teams, signl4_get_team, signl4_list_users and 15 more
SIGNL4 MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http signl4-mcp-by-usefulapi https://signl4.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
18 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List the SIGNL4 teams the API key can access: id, name, description, time zone and member ids. Team ids are needed to raise alerts and to look up categories and duties. GET /v3/teams.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| team_ids | array | no | Limit to these team ids (default: all teams the key can access). |
One SIGNL4 team: name, description, time zone, member ids. GET /v3/teams/{teamId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| team_id | string | yes | SIGNL4 team id (a GUID); get it from signl4_list_teams. |
List the SIGNL4 users the key can access with name, e-mail, contact addresses, activation state and duty status per team (dutyMode, onDutyTime). User ids are needed to acknowledge/close/annotate alerts. GET /v3/users.
No parameter schema on file.
One SIGNL4 user: name, e-mail, contact addresses, time zone and duty status per team. GET /v3/users/{userId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| user_id | string | yes | SIGNL4 user id (a GUID); get it from signl4_list_users. |
List the users of the given teams (all accessible teams by default) with duty status. Teams that cannot be read are reported under errors. GET /v3/teams/users.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| team_ids | array | no | Limit to these team ids (default: all teams the key can access). |
List the alert categories of a team (name, color, keywords used to auto-classify alerts). The category name can be passed to signl4_raise_alert. GET /v3/categories/{teamId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| team_id | string | yes | SIGNL4 team id (a GUID); get it from signl4_list_teams. |
Search SIGNL4 alerts (signls), newest first, with status, severity, category and history (created, acknowledged, closed). Filter by team, status, creation time, text or external id. Up to 100 per page; pass the returned continuation_token to get the next page. POST /v3/signls/paged (a read).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| team_ids | array | no | Limit to these team ids (default: all teams the key can access). |
| status | string | no | Only alerts in this state (default: all). |
| created_after | string | no | ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z. |
| created_before | string | no | ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z. |
| text | string | no | Free-text search in title and text. |
| external_id | string | no | Only alerts raised with this external id. |
| category_ids | array | no | Only alerts of these category ids (see signl4_list_categories). |
| max_results | integer | no | Alerts per page, 1-100 (default 25). |
| continuation_token | string | no | The continuation_token of the previous page. |
Full detail of one alert: title, text, severity, category, status and delivery status, history (who acknowledged/closed it and when), parameters, attachments and escalations with per-user delivery. GET /v3/signls/{signlId}/details.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| alert_id | string | yes | Alert (signl) id; get it from signl4_list_alerts or the id returned by signl4_raise_alert. |
The ordered timeline of an alert: creation, notifications, acknowledgements, annotations, escalations and remote actions. GET /v3/signls/{signlId}/timeline.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| alert_id | string | yes | Alert (signl) id; get it from signl4_list_alerts or the id returned by signl4_raise_alert. |
Alert volume and response statistics per team over several time periods: acknowledged, closed and unhandled counts, overall and per category (optionally for one user). Teams that cannot be read are reported under errors. GET /v3/signls/report.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| team_ids | array | no | Limit to these team ids (default: all teams the key can access). |
| user_id | string | no | Report for this user only. |
WRITE: raise a new alert in a SIGNL4 team. THIS NOTIFIES REAL PEOPLE: every team member currently on duty is paged (push, SMS and/or voice call according to their settings) and the alert escalates if nobody acknowledges it. Only use it when the user clearly asked to alert the team; never for tests unless they said so. Not idempotent: a second call pages the team again. Returns the new alert incl.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| team_id | string | yes | SIGNL4 team id (a GUID); get it from signl4_list_teams. |
| title | string | yes | Alert title, shown on the pager screen. |
| text | string | yes | Alert message body. |
| severity | string | no | Severity (default: SIGNL4's default for the team). |
| category | string | no | Category name, see signl4_list_categories (default: automatic). |
| external_id | string | no | Your own reference for this alert, for later look-up (and for SIGNL4 to group follow-ups). |
WRITE: acknowledge an alert on behalf of a SIGNL4 user (recorded in its history under that user). Stops escalation to further tiers for that alert. POST /v3/signls/{signlId}/acknowledge.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| alert_id | string | yes | Alert (signl) id; get it from signl4_list_alerts or the id returned by signl4_raise_alert. |
| user_id | string | yes | The SIGNL4 user the acknowledgement is recorded for; see signl4_list_users. |
| comment | string | no | Optional comment stored with the acknowledgement. |
WRITE: close (resolve) an alert on behalf of a SIGNL4 user; it leaves the open list and stops all further notifications. POST /v3/signls/{signlId}/close.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| alert_id | string | yes | Alert (signl) id; get it from signl4_list_alerts or the id returned by signl4_raise_alert. |
| user_id | string | yes | The SIGNL4 user the closure is recorded for; see signl4_list_users. |
| comment | string | no | Optional comment stored with the closure. |
WRITE: add a text note to an alert's timeline on behalf of a SIGNL4 user. The note is visible to the team in the app. It does not page anyone by itself. POST /v3/signls/{signlId}/annotate.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| alert_id | string | yes | Alert (signl) id; get it from signl4_list_alerts or the id returned by signl4_raise_alert. |
| user_id | string | yes | The SIGNL4 user the note is recorded for; see signl4_list_users. |
| text | string | yes | The note. |
Planned on-call duty schedules (who is on duty when): start/end, team, user, tier, stand-in and shift info. Filter by team, user and time window. POST /v3/schedules (a read).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| team_ids | array | no | Limit to these team ids (default: all teams the key can access). |
| user_id | string | no | Only this user's duties. |
| from | string | no | Start of the window, ISO 8601 with timezone. |
| to | string | no | End of the window, ISO 8601 with timezone. |
| limit | integer | no | Maximum schedules to return, 1-500 (default 100). |
Whether a user is currently on or off duty in each of their teams (dutyMode, onDutyTime, tier). GET /v3/users/{userId}/dutyStatus.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| user_id | string | yes | SIGNL4 user id (a GUID); get it from signl4_list_users. |
| team_ids | array | no | Limit to these team ids (default: all teams the key can access). |
Duty assistant info per team: whether it is enabled and the last two (or all) duty periods. GET /v3/duties/summary.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| team_ids | array | no | Limit to these team ids (default: all teams the key can access). |
| last_two_only | boolean | no | Only the last two duties (default true). |
Audit log of changes and events in the SIGNL4 subscription (who changed what, when). Filter by team, time window and message text; pass the returned continuation_token for the next page. GET /v3/audits.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| team_ids | array | no | Limit to these team ids (default: all teams the key can access). |
| from | string | no | ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z. |
| to | string | no | ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z. |
| message_contains | string | no | Only entries whose message contains this text. |
| max_results | integer | no | Entries per page, 1-200 (default 50). |
| continuation_token | string | no | The continuation_token of the previous page. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install SIGNL4 MCP by usefulapi or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish SIGNL4 MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.