Post Reef
REMOTE · POSTREEF.COM
Turn YouTube, TikTok, Instagram, Facebook, X and article URLs into transcripts, comments and JSON.
Available components
Last scanned (14 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Web Scraping
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability40
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
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 →
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.
- 21 Nov 26 +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.
- 19 Nov 26 +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.
- 17 Nov 26 +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.
- 15 Nov 26 +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.
- 13 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Nov 26 66
First indexed and scored.
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://postreef.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=postreef.com | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6fd36d04016b92670e49bcd699ee169d |
| SANs: postreef.com, *.postreef.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of postreef.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| postreef.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://postreef.com/.well-known/oauth-protected-resource", error="invalid_token", error_description="Connect your Post Reef account to continue"
Bearer resource_metadata="https://postreef.com/.well-known/oauth-protected-resource", error="invalid_token", error_description="Connect your Post Reef account to continue" Protected resource metadata
| Document | https://postreef.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://postreef.com/mcp |
| Authorisation server | https://postreef.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://postreef.com/mcp | Verified | 200 | |
| http (plaintext) | http://postreef.com/mcp | Inconclusive | 405 |
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 →
extract Extract from a link ~393
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| extraction | object | yes | – |
| kind | string | yes | – |
| note | string | – | – |
No examples provided.
get_extraction Get an extraction ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| comments_max | integer | – | How many comments to return (default 30). |
| id | string | yes | 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). |
| Name | Type | Req | Description |
|---|---|---|---|
| extraction | object | yes | – |
| kind | string | yes | – |
| note | string | – | – |
No examples provided.
get_profile Get account ~23
Use this to see which Post Reef account is connected and its credit balance.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| credits | object | yes | – |
| string | yes | – | |
| id | string | yes | – |
| kind | string | yes | – |
| name | string | yes | – |
No examples provided.
list_extractions List recent extractions ~52
Use this to find the user's previous extractions, newest first, with their ids for get_extraction.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many recent extractions to list (1-25, default 10). |
| Name | Type | Req | Description |
|---|---|---|---|
| extractions | array | yes | – |
| kind | string | yes | – |
No examples provided.
list_schemas List schemas ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| schemaId | string | – | Also return the full JSON Schema definition of this schema (name or id). |
| Name | Type | Req | Description |
|---|---|---|---|
| definition | object | – | – |
| kind | string | yes | – |
| mine | array | yes | – |
| predefined | array | yes | – |
No examples provided.
quote Quote an extraction ~265
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Public link to one video, post or web page (YouTube, Shorts, TikTok, Instagram, Facebook, X, Vimeo, an article, …). |
| Name | Type | Req | Description |
|---|---|---|---|
| credits | number | yes | – |
| durationSec | – | yes | – |
| fetches | array | yes | – |
| hasComments | boolean | yes | – |
| hasSubtitles | boolean | yes | – |
| kind | string | yes | – |
| mode | string | yes | – |
| title | – | yes | – |
| url | string | yes | – |
No examples provided.
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.
remote · postreef.com
claude mcp add --transport http franciscobmacedo-postreef 'https://postreef.com/mcp'
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.