postcache
REMOTE · POSTCACHE.DEV
Public, short-lived media URLs for agents posting to Instagram, Threads and Facebook.
Available components
Last scanned (1 hour ago)
Scores higher than 47% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Marketing and SEO
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 398 tokens (~99/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 71% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_media" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 4 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
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.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 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.
- 13 Oct 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.
- 12 Oct 26 61
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 18 Oct 2026 · Probed https://postcache.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=postcache.dev | CN=YR1,O=Let's Encrypt,C=US | 7 Oct 2026 | 5 Jan 2027 | RSA 4096 | SHA256-RSA | 5ab2d1f2bcc8245b12787126ea0a02b53a8 |
| SANs: postcache.dev | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of postcache.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| postcache.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://postcache.dev/mcp | Verified | 200 | |
| http (plaintext) | http://postcache.dev/mcp | HTTPS enforced | 301 | https://postcache.dev/mcp |
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 →
check_media ~139
Check a file against a platform without storing it. With convert, also says whether conversion can fix it.
| Name | Type | Req | Description |
|---|---|---|---|
| convert | string | – | Fix what fails the platform rules by cropping or padding and re-encoding. |
| data_base64 | string | – | The file, base64-encoded (max 10 MB). Use source_url for larger files. |
| filename | string | – | – |
| source_url | string | – | Public http(s) URL to fetch the file from. |
| target | string | yes | Platform the file is for. |
| ttl | integer | – | Seconds the URL stays valid, 3600-604800, default 86400. |
No output schema declared.
No examples provided.
delete_media ~28
Delete an uploaded file now (call after the post is published).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_media ~35
Status (converting, ready, failed), URL, expiry and fetch count of an uploaded file.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
upload_media ~196
Upload an image or video for a social platform. Returns a public URL that passes the platform media rules, or the problems with fixes. With convert, a fixable file comes back as status "converting": poll get_media until status is "ready" (url set) or "failed". Give the URL to the platform API (image_url / video_url), then call delete_media.
| Name | Type | Req | Description |
|---|---|---|---|
| convert | string | – | Fix what fails the platform rules by cropping or padding and re-encoding. |
| data_base64 | string | – | The file, base64-encoded (max 10 MB). Use source_url for larger files. |
| filename | string | – | – |
| source_url | string | – | Public http(s) URL to fetch the file from. |
| target | string | yes | Platform the file is for. |
| ttl | integer | – | Seconds the URL stays valid, 3600-604800, default 86400. |
No output schema declared.
No examples provided.
How do I install the postcache MCP server?
postcache is a hosted endpoint at https://postcache.dev/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 · postcache.dev
claude mcp add --transport http dev-postcache-postcache 'https://postcache.dev/mcp'
What is the postcache MCP server?
postcache is an MCP server listed in the public MCP registry as dev.postcache/postcache. Public, short-lived media URLs for agents posting to Instagram, Threads and Facebook. This page covers its hosted endpoint (https://postcache.dev/mcp).
Is the postcache MCP server safe to use?
postcache scores 64 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 postcache MCP server expose?
postcache exposes 4 tools: upload_media, check_media, get_media, delete_media. Their descriptions and schemas cost roughly 398 tokens of context every time the server is loaded.
Does the postcache MCP server require authentication?
No. We connected to postcache without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the postcache MCP server still maintained?
postcache is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.