Developer · Remote MCP server
StackWitness
Independent monitoring: status, monitors, and incidents from your StackWitness workspace.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.stackwitness/mcp- Version
- 1.0.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-01
- Updated
- 2026-09-01
- Publisher
- com.stackwitness
- Namespace
- Namespace verified by the MCP Registry via the domain stackwitness.com · how
- Website
- stackwitness.com/integrations/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.stackwitness.com/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect StackWitness
StackWitness is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.stackwitness.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| StackhawkAn MCP server that provides interaction with StackHawk's security scanning platform. | Local · stdio |
| StackMapSearch 344 human-reviewed AI/agent repos and the 817 typed connections between them. | Local · stdio |
| StackQL MCP ServerSQL-native query and provisioning engine for cloud infrastructure, served over MCP. | Local · stdio |
| StackShieldExternal security monitoring for Laravel apps: list domains, trigger scans, read issues and fixes. | Remote · HTTPLive check: sign-in required |
| StallhuntEvidence-backed Linux performance triage over MCP. | Local · stdio |
| StandoutAnti-slop design taste for AI coding agents: art directions, section code, 0-100 page critic. | Remote · HTTPLive check: ✓ handshake |
| StandupbotTurns your GitHub activity into a daily standup - commits, PRs, reviews & issues. | Local · stdio |
| Star NinjaStar Ninja reports sky darkness, cloud cover and moonless hours for a night-sky spot you name. | Remote · HTTPLive check: ✓ handshake |