# FirmaRED · Sellado y verificación (remote · firmared.com)

Timestamp any SHA-256 hash (post-quantum signed), verify FirmaRED codes, read Argentine front pages.

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `firmared.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-firmared-firmared/firmared.md), [page](https://verifymcp.io/servers/com-firmared-firmared/firmared)

## Channel facts

- Endpoint: `https://firmared.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

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

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 543 tokens (~90/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 75% 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**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the FirmaRED · Sellado y verificación MCP server?

FirmaRED · Sellado y verificación is a hosted endpoint at https://firmared.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 com-firmared-firmared 'https://firmared.com/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-firmared-firmared": {
      "type": "http",
      "url": "https://firmared.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-05 (score 74, +1)

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

### 2026-11-03 (score 73, +1)

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

### 2026-11-01 (score 72, +1)

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

### 2026-10-31 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-30 (score 71)

First indexed and scored.

## MCP tools (6)

### `verificar` (~110 tokens)

Verificar código de FirmaRED

Verifica un código de FirmaRED: una firma, un hecho de la máquina (acta, nota de Hoy, pronóstico, cierre del día). Acepta el código completo, un hash SHA-256, sus primeros 10 o más caracteres, o la URL https://firmared.com/v/<código>. Devuelve qué es, cuándo se firmó y la página pública de verificación.

Input parameters:

- `codigo` (string, required): Código, hash, prefijo (≥10) o URL /v/

### `sellar` (~146 tokens)

Sellar un hash con hora cierta

Sella un hash SHA-256 con hora cierta: queda un acta firmada por FirmaRED (Ed25519 + ML-DSA-44) con sándwich de tiempo (drand/NIST antes, TSA después) y la publica como hecho verificable. No sube el documento: solo el hash. Máximo 20 por hora por origen.

Input parameters:

- `hash` (string, required): SHA-256 en hexadecimal (64 caracteres)
- `quien` (string): Quién pide el sello, p. ej. el nombre del agente (opcional, ≤60)
- `titulo` (string): Nombre breve de lo que se sella (opcional, ≤120)

### `hoy` (~84 tokens)

Portada de FirmaRED Hoy

La portada de FirmaRED Hoy ahora mismo: noticias de 71 medios argentinos e internacionales, cada una con fuente, hora de ingreso sellada y link a la ficha de FirmaRED (no al medio).

Input parameters:

- `n` (integer): Cantidad (1–30, por defecto 10)
- `tema` (string): Filtra por palabra en título o resumen (opcional)

### `oraculo` (~45 tokens)

Pronósticos del Oráculo

Los pronósticos del Oráculo de FirmaRED para hoy (qué va a ser noticia mañana), sellados con la hora, y el estado que les dio el Juez.

### `search` (~42 tokens)

Buscar en FirmaRED Hoy y verificaciones

Busca en FirmaRED Hoy (noticias recientes) y en las verificaciones públicas. Devuelve id, título y URL de cada resultado.

Input parameters:

- `query` (string, required)

### `fetch` (~37 tokens)

Traer un resultado completo

Trae el contenido completo de un resultado de search por su id (slug de nota o código de verificación).

Input parameters:

- `id` (string, required)

## Diagnostics

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

## Score history

- 2026-11-05: 74
- 2026-11-04: 73
- 2026-11-03: 73
- 2026-11-02: 72
- 2026-11-01: 72
- 2026-10-31: 71
- 2026-10-30: 71

## Common questions

### What is the FirmaRED · Sellado y verificación MCP server?

FirmaRED · Sellado y verificación is an MCP server listed in the public MCP registry as com.firmared/firmared. Timestamp any SHA-256 hash (post-quantum signed), verify FirmaRED codes, read Argentine front pages. This page covers its hosted endpoint (https://firmared.com/mcp).

### Is the FirmaRED · Sellado y verificación MCP server safe to use?

FirmaRED · Sellado y verificación scores 74 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 FirmaRED · Sellado y verificación MCP server expose?

FirmaRED · Sellado y verificación exposes 6 tools: verificar, sellar, hoy, oraculo, search, fetch. Their descriptions and schemas cost roughly 464 tokens of context every time the server is loaded.

### Does the FirmaRED · Sellado y verificación MCP server require authentication?

No. We connected to FirmaRED · Sellado y verificación without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the FirmaRED · Sellado y verificación MCP server still maintained?

FirmaRED · Sellado y verificación is still listed as active in the MCP registry. We last reached this channel on 5 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 FirmaRED · Sellado y verificación MCP server?

VerifyMCP ran 13 checks on FirmaRED · Sellado y verificación, 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://firmared.com/mcp
- Website: https://firmared.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-firmared-firmared/firmared.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-firmared-firmared/firmared/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-firmared-firmared/firmared.json
- HTML version of this page: https://verifymcp.io/servers/com-firmared-firmared/firmared