AbuseZero MCP server

AbuseZero runs a remote MCP server that any client supporting the standard Streamable HTTP transport can use. AI apps work with the same actions as the AbuseZero REST API, with the same envelopes, permission checks and idempotency. Every tool also has a matching command in the AbuseZero CLI. A connection only sees the tools its scopes allow, and it only reaches the workspaces it was granted.

https://mcp.abusezero.com/mcp

Connect an AI app to the MCP serverCopy Anchor Link

Remote MCP serverCopy Anchor Link

Add a remote MCP server with the address above. The app opens your browser to sign in to AbuseZero with OAuth, where you approve the permissions it asks for. Configuration formats vary by app. A typical entry looks like this:

{
  "mcpServers": {
    "abusezero": { "url": "https://mcp.abusezero.com/mcp" }
  }
}

When you approve a new app, AbuseZero emails you that it was connected. You can disconnect an app at any time in Developers → Connected apps.

Local MCP serverCopy Anchor Link

For apps that start MCP servers on your computer, run the local server from the abusezero package:

{
  "mcpServers": {
    "abusezero": { "command": "npx", "args": ["-y", "abusezero", "mcp"] }
  }
}

The local server connects to the remote server, so its tools, resources and prompts are identical. It uses your AbuseZero CLI sign-in and selected workspace. To use a secret or restricted key instead, set ABUSEZERO_API_KEY in the app's environment for the server.

MCP server authenticationCopy Anchor Link

Publishable keys can't connect.

Choose a workspaceCopy Anchor Link

OAuth connections start without a workspace:

1. Call abusezero_list_workspaces to see the workspaces the sign-in can use.
2. Call abusezero_select_workspace with a workspace_id such as ws_8a1f3c6e-2d4b-4e9a-b7c5-0f3d6a9e2b81.
3. Call abusezero_get_connection_context at any time to see the credential type and selected workspace.

Workspace tools return WORKSPACE_REQUIRED until a workspace is selected. Key connections already use their key's workspace, so selecting one returns WORKSPACE_ALREADY_BOUND.

MCP tool behaviorCopy Anchor Link

• Inputs are the request fields of the matching REST API endpoint. Path IDs, such as id, are inputs too.
• Changes take an idempotency_key input of 1 to 128 printable characters with no spaces. Send the same key to retry a change safely.
• Annotations mark each tool as read-only, changing data or permanent, so your app can ask before it acts.
• Results carry the same response envelope as the REST API in structuredContent, plus request_id, and a one-line text summary.
• Errors set isError. structuredContent carries the error envelope, and the text reads CODE: message.

MCP toolsCopy Anchor Link

Every tool links to the AbuseZero REST API endpoint it calls, where its inputs, response and errors are described. The Scope column is the tool's scope.

MCP resourcesCopy Anchor Link

Apps that read MCP resources can open single records by address:

MCP promptsCopy Anchor Link

Prompts give an AI app a ready-made, careful workflow. None of them changes anything on its own.

Actions not available through the MCP serverCopy Anchor Link

Browser observation, which needs the AbuseZero browser SDK, and dashboard-only work, such as API keys, billing and members, aren't MCP tools. See Exclusions for the full list and the reasons.