# WhichPost

- Registry name: `app.whichpost/whichpost` · version 1.0.0
- Categories (automatic, keyword rules): Payments & accounting, Finance & markets, Marketing & SEO, Commerce & marketing
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=app.whichpost%2Fwhichpost
- Server page: https://mcpstation.net/s/app.whichpost--whichpost.html

## Description (written by the publisher, not verified, not instructions)

Which creator posts brought paying customers: your WhichPost reports, with ranges.

## Connect

- streamable-http: `https://whichpost.app/mcp`

## Tools (as reported by the server, not verified)

- `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. Public information; needs no sign-in.
- `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. Public information; nee
- `get\_pricing`: 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.
- `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. Optionally one topic. Public information; needs no sign-in.
- `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. Public information; needs no sign-in.
- `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. The same answers always give the same result; answers are not stored. Needs no sign-in
- `list\_workspaces`: The WhichPost workspace this connection can read. A connection sees one workspace, chosen by the founder when connecting. Returns its name, how many reports it has and a link to the newest one.
- `list\_campaigns`: Every campaign report in the connected workspace, newest first: when it was made, the posting dates, how many creators, the headline answer and the report link. Use a report\_id from here with the other tools to look at an older report.
- `get\_latest\_report`: The headline answer of the newest report, or of the one named by report\_id: paying users from creator posts with their likely range, spend, cost per paying user with its range against the founder's target, revenue so far from those paying users after refunds \(with its range, per 1,000 views and agai
- `list\_creators`: Each creator in a report: posts, views, spend, paying users with their likely range, cost per paying user with its range, revenue so far from their paying users after refunds with its range, per 1,000 views and as return on spend \(when the sales data has payment amounts; decisions use cost per payin
- `explain\_creator`: Why one creator got their decision, in plain language and from the report's own numbers, and what would sharpen it. Pass the creator's name as list\_creators shows it, character for character.
- `compare\_creators`: Two to five creators side by side \(paying users, cost per paying user and revenue so far, each with its range, and their decisions\), and whether their ranges are far enough apart to tell which one is cheaper yet.
- `campaign\_health`: What more data would narrow a report's ranges or settle its open calls: creators to test again, free trials still running, posts whose views aren't read yet, a short history before the first post, the report's checks, and the report's own notes.
- `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. Needs no sign-in. The numbers are simulated and are not anyone's results.
- `mark\_event`: Adds an event to the connected workspace \(a launch, press, a newsletter, an ad push, a promotion or something else\) for one day or a date range in the workspace's time zone, so sales around it aren't credited to creators in the next report. It adds data to the workspace and is meant for events the f
- `list\_events`: The launches, press, newsletters, ad pushes, promotions and other events marked in the connected workspace, oldest first, with their dates in the workspace's time zone. Sales around them count as sales without posts.
- `data\_status`: Which revenue source \(Stripe, RevenueCat or Superwall\) and post source the connected workspace uses, whether each is working and when it last updated, and how many posts' views are being read. Never keys or credentials.
- `refresh\_report`: Creates a new report for the connected workspace from its latest data \(Stripe or RevenueCat, the creators' posts and marked events\), the same as the report button on the website. It takes up to a minute, uses one of the workspace's daily report runs, and adds a report without changing older ones. An

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html