Threatbyte MCP Server

If you already use Threatbyte MCP, the threatbyte mcp mcp server is the piece that lets your assistant work with it directly. The MCP server exposes JSON-RPC at POST http://localhost:5002/mcp (Streamable HTTP). The web UI calls the MCP server through a server-side proxy to keep auth consistent with the SOC session; the proxy streams agent responses to the.

What the server does

• Safe web authentication (signup/login/logout)
• Case management UI (create/list/view cases)
• Notes and attachments tied to cases
• Indicator search and agent workflows via MCP tools
• Agent customization with schema-based tool registry

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Persistence — agent_contexts, agent_logs, mcp_audit_logs
• X-TBMCP-Token — shared secret from TBMCP_MCP_SERVER_TOKEN (configured on both servers)
• X-TBMCP-User — current user id from the authenticated SOC session
• cases.create — cases.list
• cases.list_all — cases.get
• cases.rename — cases.set_status
• cases.delete — notes.create
• notes.list — notes.update
• notes.delete — files.upload (base64)
• files.list — files.get (base64)
• files.read_path — indicators.search
• agent.summarize_case — agent.run_task

Credentials and setup notes

Configuration is passed through the environment: TBMCP_MCP_SERVER_TOKEN, TBMCP_MCP_USER_ID, OPENAI_API_KEY, TBMCP_OPENAI_API_KEY, TBMCP_MCP_SERVER_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Threatbyte MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

This sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Threatbyte MCP's toolset — Persistence, X-TBMCP-Token, X-TBMCP-User and 11 more — is a fair guide to whether it matches your workflow. It is maintained by anotherik; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Threatbyte MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.