Hosted MCP¶
The hosted MCP server lets an assistant that supports remote MCP servers connect to BreachSpider by URL, with you signing in and approving its access in your browser. There is nothing to install and no key to copy.
https://mcp.breachspider.com/mcp
Tested with Claude and ChatGPT. Other remote MCP clients that support OAuth sign-in should work; they are shown as Unverified app on the approval screen.
Turned on per organization
Connecting by URL is open per organization. Integrations shows the address when it is open for yours, or says it is not open yet. Until then, use the local MCP server with an API key.
Connect¶
- In your assistant, add a custom connector (remote MCP server) with the address above.
- The assistant opens BreachSpider's sign-in page. Enter your BreachSpider email; we send a sign-in link and a 6-digit code, and approval happens only in the browser that proved the email.
-
The approval screen shows which app is asking (and whether it is a verified app) and the access it wants:
Access Allows Device and CVE checks correlate_devices,check_changes,get_fix_plan,lookup_cve,check_windows_host,search_productsBatch jobs submit_device_batch,get_device_batchStays connected The app refreshes its access without asking you again -
Approve. The app now acts for your organization with that access.
Tools¶
The same tools as the local server, plus search_products (how the catalog names a vendor and its products, with CVE counts). Per call: at most 25 devices for correlate_devices, 5 hosts for check_windows_host and 200 devices for check_changes. For long inventories use submit_device_batch and get_device_batch.
What it refuses¶
The hosted server refuses host names, IP and MAC addresses, serial numbers, email addresses, user names and site names. It names the field and the reason, never the value, and sends nothing. Unknown fields are refused as well. Use a neutral asset id such as PLC-01.
How access works behind the scenes¶
- Each approval creates a grant with its own connection credential, limited to exactly the routes the hosted tools call. Your usage allowance and batch settings apply to it like to a key.
- Access tokens last 60 minutes and are refreshed for up to 30 days at a time; refresh tokens are rotated, and reuse of an old one is detected. A grant unused for 90 days ends.
- An organization can have at most 20 active grants.
- The hosted service never touches the database: it calls the API on the same server, which applies the same tenant isolation as every other request. See Security model.
Revoke¶
Integrations, Connected apps, lists every connected app with who approved it and when it was last used. Revoke stops it at once.
Local or hosted?¶
Choose the local server when identifying data must never leave your machine or your assistant runs locally; choose hosted when your assistant runs in the browser or a cloud app and you prefer signing in to handling keys.