INDIVIDUAL MCP TOOL

how_it_works

How WhichPost works in plain language: the three setup steps, the revenue sources it connects to (Stripe, RevenueCat, Superwall), the post platforms it reads (TikTok, Instagram, YouTube Shorts, X), how each creator gets a decision, and what a product needs for a clear answer.

whichpost.appnone authenticationAvailability not checked

LIVE ENDPOINT

https://whichpost.app/mcp/public

No auth detected

Connect to this endpoint to inspect the live schema for how_it_works and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Potential side effects detected · medium confidence · heuristic, not a guarantee.

A tool name or description contains a write-action term.

Parent server

whichpost.app

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.whichpost-public]
url = "https://whichpost.app/mcp/public"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "whichpost-public": {
      "type": "http",
      "url": "https://whichpost.app/mcp/public"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: whichpost-public
Remote MCP URL: https://whichpost.app/mcp/public

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": {
    "whichpost-public": {
      "url": "https://whichpost.app/mcp/public"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "whichpost-public": {
      "type": "http",
      "url": "https://whichpost.app/mcp/public"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "whichpost-public",
  "transport": "streamable-http",
  "url": "https://whichpost.app/mcp/public"
}

MCP Inspector

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

Related tools

about_whichpost — What WhichPost does, who it is for and who it isn't for, what a team gets from a report, and where to start.
get_pricing — WhichPost's plans and prices in US dollars (Creator Audit, Monitoring, Studio, Agency), what each is for, and current offers.
get_faq — Answers to common questions: Stripe key safety, what is read, setup, how a post is credited without a link, accuracy and ranges, what a product needs, promo codes, and what happens when the data isn't enough.
privacy_and_security — How WhichPost handles data: read-only keys, what is read and kept, no device or viewer tracking, where data is processed, and what a connected assistant can and can never see.
check_fit — A quick, fixed questionnaire: from the revenue source, creators per month, new sign-ups or installs a day and a few yes/no answers, it says whether WhichPost is a good fit now, which plan suits, and the next step.
get_sample_report — A labelled sample report built from simulated data, so anyone can see what WhichPost answers before connecting their own data: paying users with their likely range, cost per paying user, and a decision per creator.