# wyro API (remote · wyroapi.com)

Publica en Instagram, TikTok, LinkedIn, X y más desde tu agente. En español, prueba sin registro.

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

## Components

- remote · `wyroapi.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/wyroapi-wyro/wyroapi-2.md), [page](https://verifymcp.io/servers/wyroapi-wyro/wyroapi-2)
- 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`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

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

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 997 tokens (~199/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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, 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'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  wyroapi-wyro:
    url: "https://wyroapi.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

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

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-06 (score 70, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-04 (score 69, +1)

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

### 2026-11-03 (score 68, −2)

- [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

### 2026-11-02 (score 70, +1)

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

### 2026-10-31 (score 69, +1)

- [cosmetic] “wyro_publicar” added an optional parameter “formato”

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

- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (5)

### `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` (~46 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.

### `wyro_publicar` (~239 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. 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:

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

### `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_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-2#diagnostics

## Score history

- 2026-11-06: 70
- 2026-11-05: 69
- 2026-11-04: 69
- 2026-11-03: 68
- 2026-11-02: 70
- 2026-11-01: 69
- 2026-10-31: 69
- 2026-10-30: 68
- 2026-10-29: 68
- 2026-10-28: 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. Publica en Instagram, TikTok, LinkedIn, X y más desde tu agente. En español, prueba sin registro. This page covers its hosted endpoint (https://wyroapi.com/mcp).

### Is the wyro API MCP server safe to use?

wyro API scores 70 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 5 tools: wyro_empezar, wyro_cuentas, wyro_publicar, wyro_estado_post, wyro_conectar_cuenta. Their descriptions and schemas cost roughly 513 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 6 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 12 checks on wyro API, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about wyro API: Authorization. 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
- Repository: https://github.com/wyroapi/wyro
- Website: https://wyroapi.com/
- Changelog RSS feed: https://verifymcp.io/servers/wyroapi-wyro/wyroapi-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyroapi-wyro/wyroapi-2/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/wyroapi-wyro/wyroapi-2.json
- HTML version of this page: https://verifymcp.io/servers/wyroapi-wyro/wyroapi-2