ZeroTrace OSINT
MCP server
Turn on OSINT's built-in MCP server, what it exposes to a connected AI tool, and the per-session bearer token that keeps it locked to clients you choose.
MCP server
ZeroTrace OSINT can act as an MCP server. MCP (Model Context Protocol) is a common way for AI tools to use each other's capabilities, and turning this on lets another AI tool — an assistant you already use elsewhere, or your own MCP-speaking script — reach into OSINT and run its tools.
Turning it on
- Start the server
From Settings, start the MCP server on a local address of your choosing (host and port). It listens only on that address.
- Copy the session token
A fresh bearer token is generated for the session while the server runs. A connecting client has to present it — the address alone isn't enough to reach the tools.
- Point your other tool at it
Configure your external MCP client with the address and token. It can now see and call OSINT's tools like any other MCP server.
- Stop it when you're done
Stopping the server invalidates the session — a new start issues a new token, so an old one you shared can't be replayed against a later session.
What it exposes
The server exposes the same tool registry you already have in the workbench — the same ~150 tools across Network & IP, Web & threat intelligence, Crypto & hash, Accounts & identity, and File forensics — no more and no less. A tool added to the library shows up here automatically, with the same input schema and the same network/live/local behavior: a lookup run through MCP touches the network, or the target, exactly when the same tool would in the app. A connected client doesn't gain any capability beyond what OSINT itself can do.
The server binds to an address you choose, typically on your own machine. It is not exposed to the network by anything OSINT does on its own — reaching it from elsewhere is a choice you'd have to make deliberately (port forwarding, a tunnel), not something the toggle does for you.
Your choice, and revocable
The MCP server is off until you turn it on. It exists to extend your own workflow — letting an assistant you already use elsewhere reach into OSINT's toolkit — and it stays entirely in your hands: start it, stop it, and rotate access at any time by restarting it for a fresh token.
Think of the MCP server as a doorway you open when you want another tool to use OSINT's library. Nothing reaches your tools through it unless you've opened that door, and the bearer token is the key that door checks.