Skip to main content

Remote MCP

Bring live dark-web intelligence into any compatible MCP client

Query threat actors, ransomware, and leak-site posts in plain language from a compatible remote client. Included with Pro and Enterprise.

MCP endpoint

https://connect.darkwebsonar.io/mcp

Not included in the 14-day trial.

The key is created after sign-in. Included with Pro and Enterprise. Uses monthly API credits.

  1. 01

    Your MCP client

    Any remote client that speaks Streamable HTTP and OAuth.

  2. 02

    Hosted endpoint

    connect.darkwebsonar.io/mcp

  3. 03

    Read-only tools

    Ten public tools over the same intelligence feed as the REST API.

  4. 04

    Grounded answer

    The client answers from DarkWebSonar data, charged to your API credits.

  • Hosted
  • OAuth
  • Streamable HTTP
  • Read-only
  • 10 tools

What you can ask

Three jobs an analyst actually runs

Prompts go to the same intelligence feed as the REST API. Time windows such as the last 30 days are rolling, not a calendar month.

  1. 01

    Investigate an actor

    A named group is in the news and you need current targeting, not a generic biography.

    Illustrative example, not real data

    Who is Qilin, and which countries and industries has it targeted in the last 90 days?

    Background: Dark Web Most Wanted: Qilin.

  2. 02

    Quantify a sector

    Brief your leadership, board, or a client with volume and the groups behind it over a rolling window.

    Illustrative example, not real data

    How many ransomware events hit healthcare organisations in the last 30 days, and which groups were behind them?
  3. 03

    Brief your own footprint

    Check whether your organization appeared on a leak site, and which actors fit your sector and country.

    Illustrative example, not real data

    Recommend threat actors for a US financial-services company like ours, and check whether we appeared on a leak site in the last 30 days.

Capabilities

Ten read-only tools, grouped by job

Each tool call uses one API request. One answer can trigger several calls. The public server does not look up leaked credentials, read monitored keywords or watchlists, fetch full entry text, or write anything back.

Actor discovery and profiles

Resolve a group by name, pull compact or full profiles, list valid filter values, and rank actors against an industry and country footprint.

Tool names
  • dws_search_actors
  • dws_get_threat_actor_profile
  • dws_get_threat_actor_profile_by_id
  • dws_get_threat_actor_facets
  • dws_recommend_threat_actors

Incident search and counts

Count or list leak-site posts and other intelligence entries, including filters for victim organisation, site, industry, and country.

Tool names
  • dws_count_entries
  • dws_count_by_country
  • dws_count_by_field
  • dws_fetch_entries

MITRE enrichment

Resolve MITRE ATT&CK technique IDs to names and tactics. This looks up a technique map; it does not rank which techniques appear most often.

Tool names
  • dws_get_mitre_techniques

Connect

Connect it in three steps

The same endpoint works in any remote MCP client that supports Streamable HTTP and OAuth. Local stdio-only servers are a different protocol path and are not compatible.

  1. 1

    Create an API key

    Sign in, open Profile, go to API Keys, name a key by the client app, and copy it. Paste this key when your MCP client asks you to authorize. Worker keys are not accepted.

  2. 2

    Add the server in your client

    Add https://connect.darkwebsonar.io/mcp as a remote MCP server over Streamable HTTP. The client must support remote MCP and OAuth. Do not put the API key in the client config file.

  3. 3

    Authorize and ask

    When the DarkWebSonar authorize screen opens, paste your API key and approve. Ask a first question. To disconnect, revoke the key and remove the connector in the client.

Tested setup guides

Claude and Cursor are the clients we have published recipes for. Other compatible remote clients use the same URL and authorize screen.

Claude

Customize → Connectors → Add custom connector, then paste the endpoint. On Team or Enterprise, an Owner adds it under Organization settings first. Claude connects from Anthropic's cloud, not your machine. See Claude's connector help.

Cursor

Add the URL to your MCP config. Cursor opens the authorize screen so you can paste the API key. Keep the key out of the file.

Cursor MCP config

{
  "mcpServers": {
    "darkwebsonar": {
      "url": "https://connect.darkwebsonar.io/mcp"
    }
  }
}

Limits and handling

Credits, access, and what stays off the wire

Plans and credits
Pro includes 1,000 API requests a month; Enterprise includes 5,000. One credit is one request, REST or MCP. Unused credits do not roll over. Full plan details.
Read-only OAuth
Authorization code with PKCE. The API key stays on DarkWebSonar's authorize screen. Revoking the key disconnects the client. None of the public tools write or change monitors.
Your AI provider
Answers land in the connected client's context. Follow your clients' data policies and only connect servers from vendors you trust. Use one key per client app.

Prefer REST for scripts and scheduled pulls? Start with the Dark Web Monitoring API, then the integration guide. Continuous domain and keyword alerts stay on integrations and credential monitoring.

Common questions

Frequently asked questions

Is there an MCP server for dark web threat intelligence?

Yes. DarkWebSonar runs a hosted MCP server at https://connect.darkwebsonar.io/mcp. Compatible remote clients that support Streamable HTTP and OAuth can ask in plain language about threat actors, ransomware and leak-site activity, and event counts by industry, country or time range. It uses your DarkWebSonar API key and is included with the Pro and Enterprise plans.

Can I ask which ransomware groups are targeting my sector?

Yes. With the connector enabled, ask something like "How many ransomware events hit healthcare organisations in the last 30 days, and which groups were behind them?" or "Recommend threat actors for financial services in the United States." The client calls DarkWebSonar tools and answers from the intelligence feed. Each tool call uses API credits from your plan.

How do I connect a compatible MCP client?

Create an API key in your DarkWebSonar profile. Add https://connect.darkwebsonar.io/mcp as a remote MCP server. When the authorize screen opens, paste your API key and approve. Tested setup recipes for Claude and Cursor are on this page. The same endpoint works in other clients that support remote Streamable HTTP and OAuth.

Which plans include the MCP server?

MCP access is part of API access, which comes with Pro ($199/month, 1,000 API requests a month) and Enterprise (from $499/month, 5,000 requests a month). Starter, Growth, and the 14-day platform trial do not include API or MCP access. MCP queries draw from the same monthly API credits as REST calls. Each tool call uses one request; one answer can trigger more than one call.

Do I need to install anything?

No. The DarkWebSonar MCP server is hosted and uses Streamable HTTP, so you only add the endpoint URL to a compatible remote client and authorize with your API key. There is no package to install or update on your machine. Local stdio-only MCP clients are not compatible.

Is the MCP server a replacement for dark web monitoring alerts?

No. MCP is for asking questions on demand. Continuous monitoring of your domains, keywords, and threat actors, with alerts by email, Slack, Microsoft Teams, PagerDuty, ServiceNow, or webhooks, still runs in the DarkWebSonar platform. Use MCP to investigate and brief; use alerts to know when something new appears.

Can the MCP server look up leaked credentials for a domain?

No. The public MCP server exposes the intelligence feed and threat-actor tools only. It does not search breach dumps, stealer logs, or monitored-account data. Credential monitoring stays in the platform, and credential lookup through the API is on Enterprise.

Is it read-only? How do I revoke access?

Yes. All ten public tools are read-only: they query threat intelligence and do not write, export alerts, or change monitors. Your API key is entered on DarkWebSonar's authorize screen, not stored in the client config file. Revoke the key in your profile and remove the connector to disconnect.

401, missing tools, or out of credits?

A 401 or invalid_token means the session has no token or the key was revoked — remove the connector and authorize again with a current key. If the client shows no tools, finish the authorize step in the same session. When credits run out, the server tells the client not to retry; unused credits do not roll over.

Connect DarkWebSonar to your MCP client

MCP access ships with Pro. Create an API key after you sign in, add the endpoint, and start with a sector briefing.

We use cookies to improve your experience

Help us understand how visitors interact with our website by collecting anonymous information (Google Analytics, Ahrefs, PostHog).