WhichPost (public)

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

What WhichPost is, how it works, pricing and a simulated sample report. No sign-in.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "WhichPost (public)": {
      "url": "https://whichpost.app/mcp/public",
      "transport": "streamable-http"
    }
  }
}

Measured tools (7)

• about_whichpost read-only

  What WhichPost does, who it is for and who it isn't for, what a team gets from a report, and where to start. Public information; needs no sign-in.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• how_it_works read-only

  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. Public information; needs no sign-in.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_pricing read-only

  WhichPost's plans and prices in US dollars (Creator Audit, Monitoring, Studio, Agency), what each is for, and current offers. Public information; needs no sign-in.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_faq read-only

  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. Optionally one topic. Public information; needs no sign-in.

  Parameters:

  • topic — string — One topic only. Leave out for every question.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• privacy_and_security read-only

  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. Public information; needs no sign-in.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• check_fit read-only

  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. The same answers always give the same result; answers are not stored. Needs no sign-in.

  Parameters:

  • apps — integer — How many apps or products.
  • is_agency — boolean — Whether this is an agency running creators for clients.
  • revenue_source — string — Where the product's payments are recorded. 'none' if it has no payments yet.
  • spark_ads_only — boolean — Whether the campaign runs only as TikTok Spark Ads.
  • creators_per_month — integer — How many creators the team pays for posts in a typical month.
  • new_signups_per_day — integer — New sign-ups, trials or installs on a typical day.
  • has_paying_customers — boolean — Whether the product already has paying customers.
  • history_days_before_campaign — integer — Days of sales history before the campaign's first post.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_sample_report read-only

  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. Needs no sign-in. The numbers are simulated and are not anyone's results.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.