SIGNL4 MCP by usefulapi is answering right now. Last checked 5 min ago. It exposes 18 tools. Last commit 12 Oct 2026.
Read SIGNL4 alerts, teams, users and duty schedules; raise, acknowledge, close and annotate alerts.
Uptime history
4 hours of history
4 hours agonow
100.0%
Uptime 24h
14 of 14 checks
18
Tools
read from the server
156 ms
Response time
average over 24h
0
Stars
last commit 12 Oct 2026
Nothing serious here today
Today is the operative word: we check SIGNL4 MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.
run in your terminal
claude mcp add signl4 --transport http https://signl4.usefulapi.io/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"signl4": {
"url": "https://signl4.usefulapi.io/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.signl4]
url = "https://signl4.usefulapi.io/mcp".cursor/mcp.json
{
"mcpServers": {
"signl4": {
"url": "https://signl4.usefulapi.io/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"signl4": {
"url": "https://signl4.usefulapi.io/mcp"
}
}
}Available tools 18
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
signl4
signl4_acknowledge_alert
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.
signl4_annotate_alert
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.
signl4_close_alert
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.
signl4_get_alert
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.
signl4_get_alert_report
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.
signl4_get_alert_timeline
The ordered timeline of an alert: creation, notifications, acknowledgements, annotations, escalations and remote actions. GET /v3/signls/{signlId}/timeline.
signl4_get_duty_status
Whether a user is currently on or off duty in each of their teams (dutyMode, onDutyTime, tier). GET /v3/users/{userId}/dutyStatus.
signl4_get_duty_summary
Duty assistant info per team: whether it is enabled and the last two (or all) duty periods. GET /v3/duties/summary.
signl4_get_team
One SIGNL4 team: name, description, time zone, member ids. GET /v3/teams/{teamId}.
signl4_get_user
One SIGNL4 user: name, e-mail, contact addresses, time zone and duty status per team. GET /v3/users/{userId}.
signl4_list_alerts
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).
signl4_list_audit_logs
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.
signl4_list_categories
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}.
signl4_list_duty_schedules
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).
signl4_list_team_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.
signl4_list_teams
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.
signl4_list_users
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.
signl4_raise_alert
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. its id. POST /v3/signls.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://signl4.usefulapi.io/mcp | streamable-http | answering | 105 ms | 5 min ago |
Alternatives to SIGNL4 MCP by usefulapi
same job, measured the same waySquadcast MCP by usefulapi
by usefulapi
Read incidents, services, teams, on-call schedules; acknowledge, resolve and note incidents.
Spike.sh MCP by usefulapi
by usefulapi
Read Spike.sh incidents, on-call, escalations and services; acknowledge, resolve, set priority.
Dead Man's Snitch MCP by usefulapi
by usefulapi
Read Dead Man's Snitch monitors and status; create, tag, pause and unpause snitches.
Better Stack MCP by usefulapi
by usefulapi
Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.
Tick MCP by usefulapi
by usefulapi
Read Tick clients, projects, tasks, users and time entries; log and edit time entries.
Atera MCP by usefulapi
by usefulapi
Check devices, alerts and tickets in Atera, and open tickets, comment or resolve alerts.
StatusPal MCP by usefulapi
by usefulapi
Read status-page status, services, incidents and metrics; create, update and publish incidents.
Trigger.dev MCP by usefulapi
by usefulapi
Debug background jobs — runs, traces, spans, schedules, queues and deployments.
SIGNL4 MCP by usefulapi — questions
Answers built from our own checks of this server.
What can SIGNL4 MCP by usefulapi do?
It exposes 18 tools, read directly from the server on our last check. Among them: signl4_acknowledge_alert, signl4_annotate_alert, signl4_close_alert, signl4_get_alert, signl4_get_alert_report, signl4_get_alert_timeline and 12 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is SIGNL4 MCP by usefulapi working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 14 of 14 checks got a reply (100.0%), average response time 156 ms. The bar chart above shows every period we have measured.
How do I connect SIGNL4 MCP by usefulapi?
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.
Does SIGNL4 MCP by usefulapi need an API key?
No. SIGNL4 MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 18 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is SIGNL4 MCP by usefulapi?
It answers our handshake in 156 ms on average, which is faster than 71% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is SIGNL4 MCP by usefulapi open source?
Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.