# Post Reef (remote · postreef.com)

Turn YouTube, TikTok, Instagram, Facebook, X and article URLs into transcripts, comments and JSON.

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

## Components

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

## Channel facts

- Endpoint: `https://postreef.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- 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-21.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 40/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1069 tokens (~152/item across 7 items; 6 tools + 1 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **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 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Post Reef MCP server?

Post Reef is a hosted endpoint at https://postreef.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 franciscobmacedo-postreef 'https://postreef.com/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "franciscobmacedo-postreef": {
      "type": "http",
      "url": "https://postreef.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-21 (score 71, +1)

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

### 2026-11-19 (score 70, +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-17 (score 69, +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-11-15 (score 68, +1)

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

### 2026-11-13 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-12 (score 66)

First indexed and scored.

## MCP tools (6)

### `quote` (~265 tokens)

Quote an extraction

Use this before extract to see what a link is (title, duration, whether it has subtitles and comments) and exactly how many credits the extraction would cost with the same parameters. Nothing is charged and nothing is started.

Input parameters:

- `inputs` (array): AI runs (with schemaId or schema): what the model reads. Any of transcript, comments, audio, video. Default transcript + comments. Do not combine with parts.
- `parts` (array): Download-only runs (no schema): which artifacts to fetch. Any of transcript, comments, audio, video. Omit for all of them. Metadata, thumbnail and description always come back.
- `schema` (object): Inline JSON Schema (top-level object) for the extracted JSON, instead of schemaId. No type unions; enums of strings only; optional fields are simply left out of required.
- `schemaId` (string): Turn the content into JSON with a saved schema: a predefined one by name (Recipe, Workout, Product review, …) or id, or one of the user's own schema ids. See list_schemas.
- `url` (string, required): Public link to one video, post or web page (YouTube, Shorts, TikTok, Instagram, Facebook, X, Vimeo, an article, …).

Output parameters:

- `credits` (number)
- `durationSec`
- `fetches` (array)
- `hasComments` (boolean)
- `hasSubtitles` (boolean)
- `kind` (string)
- `mode` (string)
- `title`
- `url` (string)

### `extract` (~393 tokens)

Extract from a link

Use this when the user wants the transcript, comments, metadata, video/audio files or structured JSON from a video, post or web page. Starts an extraction on the user's Post Reef account (debits its credits; refunded if it fails) and waits up to wait_seconds for the result. Pass schemaId or schema for JSON, otherwise it is a download. Call quote first if the user wants to know the cost.

Input parameters:

- `force` (boolean): Run fresh even if an identical extraction from the last 30 days could be reused for free.
- `inputs` (array): AI runs (with schemaId or schema): what the model reads. Any of transcript, comments, audio, video. Default transcript + comments. Do not combine with parts.
- `maxComments` (integer): Cap on how many comments to fetch (1-1000, default 1000).
- `parts` (array): Download-only runs (no schema): which artifacts to fetch. Any of transcript, comments, audio, video. Omit for all of them. Metadata, thumbnail and description always come back.
- `schema` (object): Inline JSON Schema (top-level object) for the extracted JSON, instead of schemaId. No type unions; enums of strings only; optional fields are simply left out of required.
- `schemaId` (string): Turn the content into JSON with a saved schema: a predefined one by name (Recipe, Workout, Product review, …) or id, or one of the user's own schema ids. See list_schemas.
- `url` (string, required): Public link to one video, post or web page (YouTube, Shorts, TikTok, Instagram, Facebook, X, Vimeo, an article, …).
- `wait_seconds` (integer): How long to wait for the result before returning (0-50, default 45). If it is not done by then, call get_extraction.

Output parameters:

- `extraction` (object)
- `kind` (string)
- `note` (string)

### `get_extraction` (~125 tokens)

Get an extraction

Use this to check on or read an extraction by id: its status, and once complete the metadata, transcript, comments, extracted JSON and links to every file.

Input parameters:

- `comments_max` (integer): How many comments to return (default 30).
- `id` (string, required): The extraction id returned by extract or list_extractions.
- `transcript_max_chars` (integer): How much of the transcript to return (default 20000 characters).
- `wait_seconds` (integer): Wait up to this long for a running extraction to finish (0-50, default 0).

Output parameters:

- `extraction` (object)
- `kind` (string)
- `note` (string)

### `list_extractions` (~52 tokens)

List recent extractions

Use this to find the user's previous extractions, newest first, with their ids for get_extraction.

Input parameters:

- `limit` (integer): How many recent extractions to list (1-25, default 10).

Output parameters:

- `extractions` (array)
- `kind` (string)

### `list_schemas` (~72 tokens)

List schemas

Use this to see which schemas can turn content into JSON: the predefined ones (Recipe, Workout, Product review, …) and the user's own. Pass schemaId to get one schema's full definition.

Input parameters:

- `schemaId` (string): Also return the full JSON Schema definition of this schema (name or id).

Output parameters:

- `definition` (object)
- `kind` (string)
- `mine` (array)
- `predefined` (array)

### `get_profile` (~23 tokens)

Get account

Use this to see which Post Reef account is connected and its credit balance.

Output parameters:

- `credits` (object)
- `email` (string)
- `id` (string)
- `kind` (string)
- `name` (string)

## Diagnostics

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

## Score history

- 2026-11-21: 71
- 2026-11-20: 70
- 2026-11-19: 70
- 2026-11-18: 69
- 2026-11-17: 69
- 2026-11-16: 68
- 2026-11-15: 68
- 2026-11-14: 67
- 2026-11-13: 67
- 2026-11-12: 66

## Common questions

### What is the Post Reef MCP server?

Post Reef is an MCP server listed in the public MCP registry as io.github.franciscobmacedo/postreef. Turn YouTube, TikTok, Instagram, Facebook, X and article URLs into transcripts, comments and JSON. This page covers its hosted endpoint (https://postreef.com/mcp).

### Is the Post Reef MCP server safe to use?

Post Reef scores 71 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 Post Reef MCP server expose?

Post Reef exposes 6 tools: quote, extract, get_extraction, list_extractions, list_schemas, get_profile. Their descriptions and schemas cost roughly 930 tokens of context every time the server is loaded.

### Does the Post Reef MCP server require authentication?

Yes. Post Reef asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Post Reef MCP server still maintained?

Post Reef 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 Post Reef MCP server?

VerifyMCP ran 13 checks on Post Reef, covering TLS certificate, Authorization, HSTS header, DNSSEC and 9 more. One item could not be completed, a gap on our side rather than a finding about Post Reef: HTTPS. 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://postreef.com/mcp
- Website: https://postreef.com/
- Changelog RSS feed: https://verifymcp.io/servers/franciscobmacedo-postreef/postreef.xml
- Changelog JSON feed: https://verifymcp.io/servers/franciscobmacedo-postreef/postreef/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/franciscobmacedo-postreef/postreef.json
- HTML version of this page: https://verifymcp.io/servers/franciscobmacedo-postreef/postreef
