← Registry

Marketing

herculeradar.com

An MCP server for brand monitoring that creates workspaces and manages keyword/source monitors for brands, products, or competitors.

1 endpoint14 known toolsFirst detected September 19, 2026Last detected September 19, 2026

ENDPOINT 1

https://herculeradar.com/api/mcp

No auth detected

MCP server metadata

Name
herculeradar
Version
1.1.0
Capabilities
toolsresourcesprompts
Server instructions

HerculeRadar watches public posts about a brand and classifies them. Typical flow: list_monitors to see what is watched, list_mentions to read what people said, get_mention_analytics to summarise a period, create_monitor to start watching something new. Every tool returns { data, meta }. Page lists with the returned nextCursor. Read https://herculeradar.com/llms-full.txt for the full contract.

Known tools 14

list_projects

List the projects this credential can reach.

Inferred read-only
create_project

Create a workspace for a brand.

Potential side effects
list_monitors

List what is currently being watched: keywords, aliases, sources and whether each monitor is active.

Inferred read-only
create_monitor

Start watching a brand, product or competitor.

Inferred read-only
update_monitor

Change a monitor’s keywords, sources or active state.

Inferred read-only
delete_monitor

Permanently remove a monitor.

Potential side effects
list_mentions

The main read tool.

Inferred read-only
get_mention

Fetch one mention in full, with its AI classification and a link to the original post.

Potential side effects
update_mention_status

Move a mention through triage.

Inferred read-only
get_mention_analytics

Counts for a window — totals, relevance rate, how many need attention, and breakdowns by category, sentiment and source.

Inferred read-only
list_alerts

List alert rules — what triggers a notification and where it is sent.

Inferred read-only
create_alert

Notify an email address or https webhook when a matching mention arrives.

Potential side effects
delete_alert

Permanently remove an alert rule.

Potential side effects
get_usage

Plan and mentions used against the quota.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.herculeradar]
url = "https://herculeradar.com/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "herculeradar": {
      "type": "http",
      "url": "https://herculeradar.com/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: herculeradar
Remote MCP URL: https://herculeradar.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "herculeradar": {
      "url": "https://herculeradar.com/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "herculeradar": {
      "type": "http",
      "url": "https://herculeradar.com/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "herculeradar",
  "transport": "streamable-http",
  "url": "https://herculeradar.com/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.