# wyro API (remote · wyroapi.com)

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

- Trust score: 77/100 (medium)
- Change this week: +9
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

> **Recent critical change**: Authorization (2026-11-19). See the changelog below before you install this server.

## Components

- remote · `wyroapi.com`: 38/100, [markdown](https://verifymcp.io/servers/wyroapi-wyro/mcp-auth.md), [page](https://verifymcp.io/servers/wyroapi-wyro/mcp-auth)
- remote · `wyroapi.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/wyroapi-wyro/wyroapi.md), [page](https://verifymcp.io/servers/wyroapi-wyro/wyroapi)
- npm · `@wyroapi/mcp`: 38/100, [markdown](https://verifymcp.io/servers/wyroapi-wyro/wyroapi-mcp.md), [page](https://verifymcp.io/servers/wyroapi-wyro/wyroapi-mcp)

## Channel facts

- Endpoint: `https://wyroapi.com/mcp?src=registry`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.5`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (wyro_publicar).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## 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.

### Claude

```bash
claude mcp add --transport http wyroapi-wyro 'https://wyroapi.com/mcp?src=registry'
```

### Cursor

```json
{
  "mcpServers": {
    "wyroapi-wyro": {
      "url": "https://wyroapi.com/mcp?src=registry"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "wyroapi-wyro": {
      "type": "http",
      "url": "https://wyroapi.com/mcp?src=registry"
    }
  }
}
```

### Codex

```toml
[mcp_servers.wyroapi-wyro]
url = "https://wyroapi.com/mcp?src=registry"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyroapi-wyro": {
      "type": "remote",
      "url": "https://wyroapi.com/mcp?src=registry",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add wyroapi-wyro --url 'https://wyroapi.com/mcp?src=registry' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  wyroapi-wyro:
    url: "https://wyroapi.com/mcp?src=registry"
```

### Netclaw

```json
{
  "McpServers": {
    "wyroapi-wyro": {
      "Transport": "http",
      "Url": "https://wyroapi.com/mcp?src=registry"
    }
  }
}
```

### Vellum

```bash
assistant mcp add wyroapi-wyro -t streamable-http -u 'https://wyroapi.com/mcp?src=registry'
```

### Other

```json
{
  "mcpServers": {
    "wyroapi-wyro": {
      "type": "http",
      "url": "https://wyroapi.com/mcp?src=registry"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 77, +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.

### 2026-11-19 (score 76, 0)

- [critical regression] Authorization: unverified → fail
- [security] 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
- [functional regression] Schema quality: 199 → 254
- [functional] New tool “wyro_metricas”
- [cosmetic] “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”

### 2026-11-17 (score 76, +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.

### 2026-11-15 (score 75, +7)

- [security] 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
- [functional regression] Schema quality: pass → fail
- [cosmetic] “wyro_publicar” added an optional parameter “formato”

### 2026-10-27 (score 68, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-26 (score 67)

First indexed and scored.

## MCP tools (6)

### `wyro_empezar` (~58 tokens)

Empezar con Wyro

Ú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).

### `wyro_cuentas` (~82 tokens)

Ver cuentas

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.

Input parameters:

- `ver_cola` (boolean): 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).

### `wyro_publicar` (~443 tokens)

Publicar en redes

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.

Input parameters:

- `a_la_cola` (boolean): 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.
- `confirmar` (boolean): true solo después de que el usuario confirmó publicar en cuentas reales.
- `formato` (string): story para una historia de Instagram (una sola imagen o video). Por defecto, post.
- `medios` (array): URLs públicas de imágenes o videos (https).
- `permitir_duplicado` (boolean): 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_comentario` (string): 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_para` (string): Fecha ISO 8601 con zona horaria para programar, por ejemplo 2026-11-02T10:00:00-03:00. Sin esto se publica ya.
- `redes` (array, required): Redes donde publicar, por ejemplo ["instagram", "linkedin"].
- `texto` (string, required): Texto del post.
- `textos_por_red` (object): 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.

### `wyro_estado_post` (~69 tokens)

Estado de un post

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_).

Input parameters:

- `post_id` (string, required): Id del post, por ejemplo post_abc123.

### `wyro_metricas` (~259 tokens)

Métricas de un post o una cuenta

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.

Input parameters:

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

### `wyro_conectar_cuenta` (~101 tokens)

Conectar una cuenta real

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.

Input parameters:

- `red` (string, required): Red a conectar, por ejemplo instagram.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/wyroapi-wyro/wyroapi#diagnostics

## Score history

- 2026-11-21: 77
- 2026-11-20: 77
- 2026-11-19: 76
- 2026-11-18: 76
- 2026-11-17: 76
- 2026-11-16: 75
- 2026-11-15: 75
- 2026-10-27: 68
- 2026-10-26: 67

## 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.

## Links

- Remote endpoint: https://wyroapi.com/mcp?src=registry
- Repository: https://github.com/wyroapi/wyro
- Website: https://wyroapi.com/
- Changelog RSS feed: https://verifymcp.io/servers/wyroapi-wyro/wyroapi.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyroapi-wyro/wyroapi/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/wyroapi-wyro/wyroapi.json
- HTML version of this page: https://verifymcp.io/servers/wyroapi-wyro/wyroapi
