Servidor MCP de WhichPost

• Nome no registroapp.whichpost/whichpostverificado no registro MCP

O nome no registro fica sob whichpost.app. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.

• Estadorespondeverificado em 2026-10-27
• Ferramentas18
• O servidor se chamawhichpost
• Versão do servidor1.0.0
• Versão do protocolo2025-06-18

Em 2026-10-27 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 101 ms.

• As ferramentas fazem todos os casos de uso verificados: rank creators by the paying customers they brought; compare cost per paying customer across creator posts.
• Verificado em 1 dos 7 dias necessários para julgar a confiabilidade.

Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.

• Nota INITE MCPdepois de uma semanaa nota precisa de 7 verificações diárias: 1 até agora
• O que um agente consegue fazer com ele2 de 2 casos de uso
• Respondeumedindo1 das 7 verificações diárias necessárias para mostrar a porcentagem
• Mediana da primeira resposta290 ms
• Espaço no contexto do agente≈ 2.527 tokensas definições de todas as ferramentas (18), que o agente carrega a cada turno
• Definições das ferramentasA · 96 de 100
• Resultados tipados18 de 18 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez

• Parâmetros sem descrição: em 4 de 18

Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (25%), se faz o trabalho do produto (25%), definições (20%), contexto (10%), uso (10%) e a facilidade de conectar (10%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e números →

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

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

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

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

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

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

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

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

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

• app.whichpost/whichpost-publicresponde, 7 ferramentasverificado no registro MCP