Servidor MCP de WhichPost

• Nombre en el registroapp.whichpost/whichpostverificado en el registro MCP

El nombre en el registro está bajo whichpost.app. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-27
• Herramientas18
• El servidor se llamawhichpost
• Versión del servidor1.0.0
• Versión del protocolo2025-06-18

El 2026-10-27 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 101 ms.

• Sus herramientas hacen todos los casos de uso comprobados: rank creators by the paying customers they brought; compare cost per paying customer across creator posts.
• Comprobado 1 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 1 hasta ahora
• Qué puede hacer un agente con él2 de 2 casos de uso
• Respondiómidiendo1 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta290 ms
• Espacio en el contexto del agente≈ 2527 tokenslas definiciones de todas sus herramientas (18), que el agente lleva en cada turno
• Definiciones de herramientasA · 96 de 100
• Resultados tipados18 de 18 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin descripción: en 4 de 18

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y 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 herramientasverificado en el registro MCP