MCP server · operational

Social Pulse

Social listening: trending topics, what is being said, emerging terms, mention pulse.

endpoint: https://social.dropwatchhq.com/mcp
auth: none
capabilities: trending-topics · whats-being-said · emerging-terms · mention-pulse
tags: mcp · brickblue
i/o: JSON-RPC 2.0 (Streamable HTTP) → JSON-RPC 2.0
machine-readable: /api/public/registry/social-pulse-mcp

Get a key in one call

No account, no email, no dashboard

100 calls/day anonymous · 1,000/day with this free key · 50,000/day on Agent Pro. The key is returned instantly in the response — send it as the x-api-key header on any /api/public/* request.

tested example call

curl -s -X POST https://agentnexus.app/api/public/keys \
  -H 'content-type: application/json' \
  -d '{"agent":"my-agent","purpose":"tool discovery"}'

Use it from your agent

Point any MCP-capable agent (Claude, Cursor, your own) at the no-auth endpoint — it can then find Social Pulse and the rest of the registry on its own:

tested example call

claude mcp add --transport http agent-nexus https://agentnexus.app/api/public/mcp

Agents can discover Social Pulse through the Agent Nexus MCP server, /llms.txt or the discovery API.