Skip to content

postcache MCP server

dev.postcache/postcachepostcache.devstreamable-httpv1.0.0Scanned

Public, short-lived media URLs for agents posting to Instagram, Threads and Facebook.

4 tools: 1 can delete or cancel things, 2 change things and 1 only read.

Tools: 1 delete, 0 irreversible, 2 write, 1 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the postcache MCP server can do

The postcache MCP server is published by postcache.dev, a domain the MCP Registry verified. It has 4 tools. It can delete or cancel things (1 tool: delete_media) and create or change data (2 tools: upload_media and check_media). 1 tool only reads.

1 tool reads private data (get_media); 1 tool brings in text other people can write (get_media).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 15, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Deletes or cancels 1Claude Code: deny
  • delete_mediaDelete an uploaded file now (call after the post is published).No findings

    Why it is in this group

    • The name "delete_media" says "delete": a word for removing or ending something.
    Description, as the server wrote it
    Delete an uploaded file now (call after the post is published).
Changes things 2Claude Code: ask
  • check_mediaCheck a file against a platform without storing it.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Check a file against a platform without storing it. With convert, also says whether conversion can fix it.
  • upload_mediaUpload an image or video for a social platform.No findings

    Why it is in this group

    • The name "upload_media" says "upload": a word for a change.
    Description, as the server wrote it
    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.
Only reads 1Show 1 read-only tool
  • get_mediaStatus (converting, ready, failed), URL, expiry and fetch count of an uploaded file.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_media" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "status" and "file": it reads files.
    • untrusted-inputThe description's first sentence says "status" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Status (converting, ready, failed), URL, expiry and fetch count of an uploaded file.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:52 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://postcache.dev/mcp: tools/list returned 4 tools to an anonymous client, including delete_media (destructive), upload_media (write), check_media (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http postcache https://postcache.dev/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http postcache https://postcache.dev/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__postcache__get_media"
    ],
    "ask": [
      "mcp__postcache__upload_media",
      "mcp__postcache__check_media"
    ],
    "deny": [
      "mcp__postcache__delete_media"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as postcache. Review it before you use it.

Capability tags behind 1 rule
  • mcp__postcache__get_media private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.postcache/postcache/verify?hash=9e8d034e44627527898ca12ee7ff8df75861018f9a3f8a3ae831dd9e9d6b8670" | jq -e '.changed == false'

Pinned hash 9e8d034e4462, from Nov 15, 2026, 03:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.postcache/postcache/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.postcache/postcache
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.postcache/postcache.svg)](https://radar.anlyon.com/servers/dev.postcache/postcache)

Source: MCP Registry. Synced Oct 21, 2026, 18:12 UTC.

postcache MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the postcache MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the postcache MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: delete_media.

Can the postcache MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the postcache MCP server have?

4 tools: 1 destructive, 2 write, 1 read. delete_media, upload_media, check_media and get_media.

Does the postcache MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the postcache MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the postcache MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.