WhichPost

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

• 연결 방식: 클라우드에서 실행
• 전송 방식: Streamable HTTP
• 카테고리: 기타

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

필요한 것

• 클라우드에서 실행설치할 것 없음. 인터넷으로 연결돼요

어떤 앱을 쓰세요?

https://whichpost.app/mcp

claude mcp add --transport http whichpost https://whichpost.app/mcp

{
  "mcpServers": {
    "whichpost": {
      "url": "https://whichpost.app/mcp"
    }
  }
}

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

https://whichpost.app/mcp

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

도구 이름과 설명은 서버가 2026년 11월 8일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.

• 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. Pub

• 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 stor

• 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

• 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; decision

• 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

• 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 me

• 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 cha

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 8일 점검

• ! 주의

  제작자와 저장소 일치

  레지스트리에 소스 저장소가 없어서, 게시자(whichpost.app)와 코드를 맞춰 볼 수 없어요

• … 아직 점검 안 함

  계속 관리되고 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• … 아직 점검 안 함

  라이선스 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• ✓ 통과

  엔드포인트 응답

  160ms 만에 응답(HTTP 200)

• – 해당 없음

  OAuth로 로그인

  로그인 필요 없음

• ✓ 통과

  도구 설명에 숨겨진 지시 없음

  도구 설명 18개를 읽었고, AI에게 보내는 숨겨진 지시는 없었어요

기타 카테고리의 다른 서버와 비교i

• 이 카테고리의 다른 서버 18595개 중 0%보다 스타가 많아요
• 이 카테고리의 다른 서버 18595개 중 64%보다 최근에 레지스트리에 공개됐어요
• 기본 점검 결과가 이 카테고리의 다른 서버 18595개 중 36%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:↓ 주간 다운로드i★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

제작자의 README

저장소에서 README를 찾지 못했어요