← Registry

Social Media

whatstrending.cc

Provides social media monitoring and analytics by retrieving trending topics, public posts, and engagement metrics for a workspace.

1 endpoint3 known toolsFirst detected September 1, 2026Last detected September 1, 2026

ENDPOINT 1

https://api.whatstrending.cc/mcp

No auth detected

MCP server metadata

Name
whatstrending
Version
1.0.0
Capabilities
tools
Server instructions

Use an API key as Authorization: Bearer wt_live_… to read trends, inspect evidence, or run a scan.

Known tools 3

get_trends

Return ranked topics for the authenticated workspace over a selected timeframe.

Inferred read-only
list_evidence

Return public posts, source URLs and available engagement metrics for the authenticated workspace.

Inferred read-only
run_scan

Collect fresh public evidence for the authenticated workspace.

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.whatstrending]
url = "https://api.whatstrending.cc/mcp"
enabled = true
Claude Code

.mcp.json

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

Settings → Connectors → Add custom connector

Name: whatstrending
Remote MCP URL: https://api.whatstrending.cc/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": {
    "whatstrending": {
      "url": "https://api.whatstrending.cc/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

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

Client-specific MCP configuration

{
  "name": "whatstrending",
  "transport": "streamable-http",
  "url": "https://api.whatstrending.cc/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.