mcp-serverBLOCK
SutramX MCP server (stdio + hosted HTTP): let AI agents manage monitors, incidents and status pages.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
A Model Context Protocol server that lets AI agents and assistants (Claude Code, Claude Desktop and other MCP clients) work with your SutramX workspace: list and change monitors, read check results, handle incidents and manage status pages.
It talks to the public SutramX API with a workspace API key, so it can do exactly what that key can do and nothing more.
Tools
13aba5451e8eOBSERVED · 2026-10-11Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add mcp-server --env SUTRAMX_API_KEY=${SUTRAMX_API_KEY} -- npx -y @sutramx/[email protected]Exposed tools (26)
17 read · 7 write · 2 destructive. Blast radius: 2 tools can delete or overwrite — an agent that can be talked into calling a tool can be talked into calling this one.
| Tool | Risk | Description |
|---|---|---|
sutramx_acknowledge_incident | read | |
sutramx_add_incident_note | write | |
sutramx_create_monitor | write | |
sutramx_create_status_page | write | |
sutramx_delete_monitor | destructive | |
sutramx_delete_status_page | destructive | |
sutramx_explain_incident | read | |
sutramx_get_check_results | read | |
sutramx_get_incident | read | |
sutramx_get_monitor | read | |
sutramx_get_status_page | read | |
sutramx_list_incidents | read | |
sutramx_list_maintenance_windows | read | |
sutramx_list_monitors | read | |
sutramx_list_regions | read | |
sutramx_list_status_pages | read | |
sutramx_monitor_summary | read | |
sutramx_pause_monitor | read | |
sutramx_resolve_incident | read | |
sutramx_resume_monitor | read | |
sutramx_run_check | write | |
sutramx_set_status_page_monitors | write | |
sutramx_update_monitor | write | |
sutramx_update_status_page | write | |
sutramx_uptime_report | read | |
sutramx_whoami | read |
Trust audit
BLOCKgrade D · trust 69/100 Do not install this without reading the findings. The audit found something that could harm you or your machine.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | FAIL |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | WARN |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (1 observation(s))
- Network
- declared (8 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- found
Findings (13)
console.error('Warning: NODE_TLS_REJECT_UNAUTHORIZED=0 disables TLS certificate checks; API keys can be intercepted.');CMD node -e "fetch('http://127.0.0.1:'+(process.env.PORT||3333)+'/health').then(r=>process.exit(r.ok?0:1),()=>process.exit(1))"const redirectUri = 'http://127.0.0.1:53682/callback';
const SECRET = 'proof-0123456789abcdef';
const SECRET = 'proof-0123456789abcdef';
sutramx_delete_monitor, sutramx_delete_status_page
for (const args of [{ key: '..' }, { key: '../admin' }, { key: '.' }, { monitor_id: '../../admin/users' }]) {The endpoint is `POST http://127.0.0.1:3333/mcp` (stateless, JSON responses). Every request must send its own SutramX key:
claude mcp add --transport http sutramx http://127.0.0.1:3333/mcp \
assert.equal(validateInternalApiUrl('http://10.0.0.5:3003'), 'http://10.0.0.5:3003');@modelcontextprotocol/sdk, express, zod, @types/express, @types/node, tsx, typescript
- Use read-only mode for assistants that only need to look (triage, reporting), ideally together with a Read-only API key (below).
In SutramX, open **Settings → API keys → Create API key**. Keys start with `sk_` and are shown once.
Gates applied: no_behavioural_pass.
13aba5451e8efull audit observations/trust-audit/mcp-server/sutramx__mcp-server.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-11 | 13aba5451e8e | BLOCK | D | 69 | first audit |
Questions
What is the mcp-server MCP server?
SutramX MCP server (stdio + hosted HTTP): let AI agents manage monitors, incidents and status pages.
What tools does mcp-server expose?
26 in total: 17 read-only, 7 that write, and 2 that can delete or overwrite (sutramx_delete_monitor, sutramx_delete_status_page). Every one is listed on this page with its risk.
Is mcp-server safe to connect to an agent?
No — not without reading the findings first. The audit graded it D (69/100) and found 1 critical or high issue in the source. Each one is listed on this page with the file and line it is on. Separately from the audit: 2 of its tools can destroy data, so scope the token you give it to what you actually need.
What credentials does mcp-server need?
It reads NODE_TLS_REJECT_UNAUTHORIZED, OAUTH_RESOURCE_PROXY_SECRET and SUTRAMX_API_KEY from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does mcp-server run?
It speaks stdio and streamable-http, so it runs as a local process your client starts. It is published on npm as @sutramx/mcp-server at 0.1.5.
How current is this page?
The grade is for one exact copy of the source (13aba5451e8e), read on 2026-10-11. The repository is watched and re-audited when it changes.