WhichPost

Name: WhichPost
Author: app.whichpost

MCP serverMCP

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

by app.whichposthomepage ↗v1.0.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"whichpost","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability33/33 checks ok

when	check	result	http	latency	detail
6 h ago	mcp initialize	ok	200	309 ms	server whichpost 1.0.0 · protocol 2025-06-18 · 18 tools
11 h ago	mcp initialize	ok	200	338 ms	server whichpost 1.0.0 · protocol 2025-06-18 · 18 tools
18 h ago	mcp initialize	ok	200	324 ms	server whichpost 1.0.0 · protocol 2025-06-18 · 18 tools
26 h ago	mcp initialize	ok	200	297 ms	server whichpost 1.0.0 · protocol 2025-06-18 · 18 tools
32 h ago	mcp initialize	ok	200	289 ms	server whichpost 1.0.0 · protocol 2025-06-18 · 18 tools
2 d ago	mcp initialize	ok	200	403 ms	server whichpost 1.0.0 · protocol 2025-06-18 · 18 tools
2 d ago	mcp initialize	ok	200	301 ms	server whichpost 1.0.0 · protocol 2025-06-18 · 18 tools
2 d ago	mcp initialize	ok	200	300 ms	server whichpost 1.0.0 · protocol 2025-06-18 · 18 tools
2 d ago	mcp initialize	ok	200	310 ms	server whichpost 1.0.0 · protocol 2025-06-18 · 18 tools
3 d ago	mcp initialize	ok	200	332 ms	server whichpost 1.0.0 · protocol 2025-06-18 · 18 tools

Tools observed via MCP handshake

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 (T
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-
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 cod
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
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
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
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.
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
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
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 sho
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 ar
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
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 ra
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
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 ti
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 m
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 butt

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryapp.whichpost/whichpost

first seen 9 d ago · fetched 3 d agoopen ↗

Field history (6 recent events)

9 d ago · declared · summary → "Which creator posts brought paying customers: your WhichPost reports, with ranges."
9 d ago · declared · description → "Which creator posts brought paying customers: your WhichPost reports, with ranges."
9 d ago · declared · publisherName → "app.whichpost"
9 d ago · declared · homepageUrl → "https://whichpost.app/claude-and-chatgpt"
9 d ago · declared · version → "1.0.0"
9 d ago · declared · protocols → ["mcp"]

WhichPost

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from