Categories › Business & Finance › Market data, stocks & crypto
Which creator posts brought paying customers: your WhichPost reports, with ranges.
Remote server: your requests and data go to whichpost.app. Claude Code: claude mcp add --transport http whichpost https://whichpost.app/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
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 sihow_it_works — How WhichPost works in plain language: the three setup steps, the revenue sources it reads (Stripe, RevenueCat, Superwall, or a Shopify ordeget_pricing — WhichPost's plans and prices in US dollars (Creator Audit, Monitoring, Studio, Agency), what each is for, and current offers. Public informaget_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 prodprivacy_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 connectcheck_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 list_workspaces — The WhichPost workspace this connection can read. A connection sees one workspace, chosen by the founder when connecting. Returns its name, list_campaigns — Every campaign report in the connected workspace, newest first: when it was made, the posting dates, how many creators, the headline answer 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, 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 froexplain_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 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 whecampaign_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 viewsget_sample_report — A labelled sample report built from simulated data, so anyone can see what WhichPost answers before connecting their own data: paying users 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 ralist_events — The launches, press, newsletters, ad pushes, promotions and other events marked in the connected workspace, oldest first, with their dates idata_status — Which revenue source (Stripe, RevenueCat or Superwall) and post source the connected workspace uses, whether each is working and when it lasrefresh_report — Creates a new report for the connected workspace from its latest data (Stripe or RevenueCat, the creators' posts and marked events), the samNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.