getsonar-mcp 0.1.0

MCP server for SONAR — competitive intelligence, KYB due diligence, and adverse media screening for AI agents.

getsonar-mcp

MCP server for SONAR — competitive intelligence, KYB due diligence, and adverse media screening, exposed as tools any MCP-compatible AI client can call.

Works with Claude Desktop, Claude Code, Cursor, Windsurf, Continue.dev, and any other Model Context Protocol client.

What it does

Adds 7 tools to your AI assistant:

Tool	What it does	Cost (after free tier)
kyb_findings	Quick KYB lookup — corporate registration, sanctions, FCA, directors, UBOs	$0.40
kyb_run_submit	Full KYB report (async, with Claude analysis)	$2.00
competitive_findings	Quick competitor intel — pricing, hiring, product, sentiment	$0.40
competitive_run_submit	Full CI report (async, with Claude analysis)	$2.00
adverse_media	Negative news + complaints + bad-review screening	$0.40
check_report_status	Poll the result of an async *_run_submit call	free
account_balance	Check remaining free-tier calls + usage	free

Free tier: 100 calls/month per API key. Beyond that, balance-deducted at the prices above.

Get an API key

1. Sign up at getsonar.report
2. Go to API Keys in the sidebar
3. Click Create API Key, copy the sk-sonar-... key
4. (Optional) Top up your account on the same page if you'll exceed 100 calls/month

Install

Recommended: uvx (no install needed)

If you have uv installed (most modern Python setups), nothing to install — uvx getsonar-mcp runs the latest version on demand.

Alternative: pipx

pipx install getsonar-mcp

Configure your MCP client

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "sonar": {
      "command": "uvx",
      "args": ["getsonar-mcp"],
      "env": {
        "SONAR_API_KEY": "sk-sonar-YOUR_KEY_HERE"
      }
    }
  }
}

Restart Claude Desktop. The 7 tools should appear in the 🔌 menu.

Claude Code

Add to your project's .mcp.json or run:

claude mcp add sonar -- uvx getsonar-mcp
# Then in your shell: export SONAR_API_KEY=sk-sonar-...

Or with the env var inline:

claude mcp add sonar --env SONAR_API_KEY=sk-sonar-... -- uvx getsonar-mcp

Cursor

~/.cursor/mcp.json:

{
  "mcpServers": {
    "sonar": {
      "command": "uvx",
      "args": ["getsonar-mcp"],
      "env": {
        "SONAR_API_KEY": "sk-sonar-YOUR_KEY_HERE"
      }
    }
  }
}

Windsurf / Continue.dev

Same config shape as Claude Desktop. See your client's MCP docs for the config file path.

Configuration

Environment variables (all optional except SONAR_API_KEY):

Variable	Default	Purpose
SONAR_API_KEY	(required)	Your sk-sonar-... API key
SONAR_API_BASE	https://api.getsonar.report	Override for staging / self-hosted SONAR
SONAR_API_TIMEOUT	120	Per-request timeout in seconds
SONAR_MCP_LOG_LEVEL	INFO	DEBUG for verbose tool dispatch logs

Example prompts

After configuring, try these in Claude:

"Run a KYB check on Tesco PLC and tell me if anything looks risky."

Claude calls kyb_findings("Tesco PLC") → ~30s → reads back the structured findings → highlights the FCA Register hit, any sanctions matches, director-level red flags.

"Submit a full competitive analysis for Notion and tell me when it's done."

Claude calls competitive_run_submit("Notion") → gets run_id → polls check_report_status every 30s → returns the narrative report.

"Am I close to my free-tier limit?"

Claude calls account_balance() → tells you how many of your 100 free monthly calls you've used.

How async reports work

The *_run_submit tools return a run_id immediately (in <1s). Claude then needs to call check_report_status(run_id, agent_type) to fetch the result, which is normally ready in 60-180s. Most MCP clients handle this seamlessly — Claude knows from the tool descriptions to poll until status="completed".

The cheaper *_findings tools are synchronous and complete in 30-90s on a single call. Use those when the LLM just needs raw structured data and will do its own analysis.

Verify your install

Use the MCP Inspector to confirm the server starts and tool dispatch works:

SONAR_API_KEY=sk-sonar-... npx @modelcontextprotocol/inspector uvx getsonar-mcp

You should see all 7 tools listed and be able to invoke them with test inputs.

Source

getsonar-mcp is a thin client for the SONAR public API. The source is currently maintained privately; for issues, feature requests, or transport changes, email [e-mail].

Troubleshooting

Claude says "tool not available" — check claude_desktop_config.json is valid JSON, restart Claude Desktop, then verify uvx --version runs in your terminal.

401 Unauthorized — SONAR_API_KEY is missing or wrong. Verify in the SONAR dashboard at getsonar.report/api-keys.

402 Payment Required — your free tier is exhausted and your balance is $0. Top up at getsonar.report/api-keys.

Timeouts — bump SONAR_API_TIMEOUT in your env config. The /run tools can take 3+ minutes for complex KYB subjects.

License

MIT — see LICENSE.