Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

wyro API

REMOTE · WYROAPI.COM · 3 COMPONENTS

Lets Claude and AI agents post, schedule and measure on Instagram, TikTok, LinkedIn and 5 more.

+9 this week 77 Trust /100

Last scanned (17 hours ago)

Scores higher than 67% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Marketing and SEO

Recent critical change

Authorization (19 Nov 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1524 tokens (~254/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 0
    • Authorization: unverified → fail ▼ critical
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “wyro_publicar” rewrote its description, which is the text the model reads security
    • Tool “wyro_publicar” is now declared destructive security
    • Schema quality: 199 → 254 ▼ functional
    • New tool “wyro_metricas” functional
    • “wyro_publicar” added an optional parameter “a_la_cola” cosmetic
    • “wyro_publicar” added an optional parameter “permitir_duplicado” cosmetic
    • “wyro_publicar” added an optional parameter “primer_comentario” cosmetic
    • “wyro_publicar” added an optional parameter “textos_por_red” cosmetic
    • “wyro_cuentas” added an optional parameter “ver_cola” cosmetic
  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +7
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “wyro_conectar_cuenta” rewrote its description, which is the text the model reads security
    • Tool “wyro_empezar” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • “wyro_publicar” added an optional parameter “formato” cosmetic
  • 27 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 26 Oct 26 67

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://wyroapi.com/mcp?src=registry

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=wyroapi.com CN=YR1,O=Let's Encrypt,C=US 27 Oct 2026 25 Jan 2027 RSA 2048 SHA256-RSA 55d55a3858232ee10cdd9ad07f93e6221be
SANs: wyroapi.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of wyroapi.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
wyroapi.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://wyroapi.com/mcp?src=registry Verified 200
http (plaintext) http://wyroapi.com/mcp?src=registry HTTPS enforced 308 https://wyroapi.com/mcp?src=registry
MCP tools · 6 exposed · ~1,012 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
wyro_conectar_cuenta ~101

Devuelve el link para conectar la cuenta real de una red y cómo acompañar al usuario en el proceso (qué cambia, qué va a ver, requisitos de la red, qué hacer si algo falla). Úsala cuando quiera publicar de verdad o después de un post simulado que le gustó. La clave actual sigue funcionando: no hay que reconfigurar nada.

NameTypeReqDescription
redstringyesRed a conectar, por ejemplo instagram.

No output schema declared.

No examples provided.

wyro_cuentas ~82

Lista las cuentas de redes sociales disponibles (simuladas en modo prueba, reales cuando el usuario las conecta). Úsala antes de publicar para saber a qué redes puedes enviar.

NameTypeReqDescription
ver_colaboolean–true para recibir también los próximos horarios libres de la cola de publicación (para sugerir cuándo publicar o antes de usar a_la_cola).

No output schema declared.

No examples provided.

wyro_empezar ~58

Úsala primero cuando el usuario acaba de instalar Wyro o pregunta qué puede hacer, cómo funciona o cuánto cuesta: devuelve el estado y qué explicarle. Si todavía no hay clave, crea una de prueba gratis (sin registro).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

wyro_estado_post ~69

Devuelve el estado (programado, publicado, fallido) y los links de vista previa de un post. Úsala con el id que devolvió la publicación (empieza con post_).

NameTypeReqDescription
post_idstringyesId del post, por ejemplo post_abc123.

No output schema declared.

No examples provided.

wyro_metricas ~259

Cómo le fue a un post o a una cuenta: impresiones, alcance, vistas, me gusta, comentarios, compartidos, guardados, clics y tasa de interacción por red, y los seguidores de una cuenta. Úsala cuando el usuario pregunte cómo le fue a un post («¿cómo le fue a mi último post?») o cómo va una cuenta. Sin argumentos lee el último post publicado. Las redes actualizan las métricas cerca de una vez por hora; en modo prueba son simuladas.

NameTypeReqDescription
actualizarboolean–true para volver a consultar las redes ahora (como mucho una vez cada 15 minutos por post).
cuentastring–Id de la cuenta (acc_…) o nombre de la red ("instagram") para un resumen de la cuenta: seguidores, posts, totales, promedios y mejor post.
desdestring–Inicio del rango de la cuenta, YYYY-MM-DD (por defecto: hace 30 días).
hastastring–Fin del rango de la cuenta, YYYY-MM-DD, inclusive (por defecto: hoy).
post_idstring–Id del post (post_…). Sin esto (y sin cuenta), el último post publicado.

No output schema declared.

No examples provided.

wyro_publicar ~443

Publica o programa un post en Instagram, TikTok, Facebook, LinkedIn, X, Threads, YouTube o Pinterest. Úsala cuando el usuario pida publicar o programar contenido. No la uses para leer métricas (para eso, wyro_metricas). En cuentas reales, pide confirmación antes de publicar (confirmar=true). Devuelve un link de vista previa: muéstraselo al usuario. Instagram y Pinterest necesitan imagen o video; TikTok y YouTube, video.

NameTypeReqDescription
a_la_colaboolean–true para programarlo en el próximo horario libre de la cola del usuario (en vez de programar_para). La respuesta trae la hora elegida: cuéntasela al usuario.
confirmarboolean–true solo después de que el usuario confirmó publicar en cuentas reales.
formatostring–story para una historia de Instagram (una sola imagen o video). Por defecto, post.
mediosarray–URLs públicas de imágenes o videos (https).
permitir_duplicadoboolean–true solo si el usuario de verdad quiere publicar otra vez el mismo texto en la misma cuenta dentro de 24 h (si no, se rechaza como duplicate_post, que suele ser un reintento que ya salió).
primer_comentariostring–Primer comentario, publicado justo después del post en las redes que lo admiten (Instagram, Facebook, LinkedIn, Threads, YouTube). Sirve para links y hashtags.
programar_parastring–Fecha ISO 8601 con zona horaria para programar, por ejemplo 2026-11-02T10:00:00-03:00. Sin esto se publica ya.
redesarrayyesRedes donde publicar, por ejemplo ["instagram", "linkedin"].
textostringyesTexto del post.
textos_por_redobject–Texto distinto por red, por ejemplo {"x": "versión corta", "linkedin": "versión larga"}. Claves: nombres de las redes (o ids de cuenta acc_…). Las demás usan texto.

No output schema declared.

No examples provided.

Install

How do I install the wyro API MCP server?

wyro API is a hosted endpoint at https://wyroapi.com/mcp?src=registry, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · wyroapi.com

# add to Claude Code
claude mcp add --transport http wyroapi-wyro 'https://wyroapi.com/mcp?src=registry'
Common questions

What is the wyro API MCP server?

wyro API is an MCP server listed in the public MCP registry as io.github.wyroapi/wyro. Lets Claude and AI agents post, schedule and measure on Instagram, TikTok, LinkedIn and 5 more. This page covers its hosted endpoint (https://wyroapi.com/mcp?src=registry).

Is the wyro API MCP server safe to use?

wyro API scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the wyro API MCP server expose?

wyro API exposes 6 tools: wyro_empezar, wyro_cuentas, wyro_publicar, wyro_estado_post, wyro_metricas, wyro_conectar_cuenta. Their descriptions and schemas cost roughly 1,012 tokens of context every time the server is loaded.

Does the wyro API MCP server require authentication?

No. We connected to wyro API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the wyro API MCP server still maintained?

wyro API is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the wyro API MCP server?

VerifyMCP ran 13 checks on wyro API, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.