Skip to content

PiPic Integration Guide MCP server

cc.pipic/pipicpipic.ccstreamable-httpv1.0.0Scanned

Read-only PiPic CLI and HTTP API guidance; no image bytes are transferred.

3 tools: 1 change things and 2 only read.

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

Tools listed without sign-in. Remote posture

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Its sign-in does not let Anlyon set up an OAuth client on its own, so there is no link to it here.

What the PiPic Integration Guide MCP server can do

The PiPic Integration Guide MCP server is published by pipic.cc, a domain the MCP Registry verified. It has 3 tools. It can create or change data (1 tool: check_image_supported), but cannot delete data. 2 tools only read.

2 tools read private data (get_compression_facts and get_integration_guide); 2 tools bring in text other people can write (get_compression_facts and get_integration_guide).

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 12, 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.

3 tools

Changes things 1Claude Code: ask
  • check_image_supportedGiven a filename, MIME type and/or byte size, says whether PiPic will accept the image and, if not, which error an upload would return.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
    Given a filename, MIME type and/or byte size, says whether PiPic will accept the image and, if not, which error an upload would return. Use it to filter a file list locally instead of spending quota on requests that are going to be rejected.
Only reads 2Show 2 read-only tools
  • get_compression_factsWhat PiPic can compress, the file-size and batch limits, and how the free/Pro monthly allowance for the CLI and HTTP API works.Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "file": it reads files.
    • untrusted-inputThe description's first sentence says "http": it reads web pages, which anyone can write.
    Description, as the server wrote it
    What PiPic can compress, the file-size and batch limits, and how the free/Pro monthly allowance for the CLI and HTTP API works. Read this before telling a user what PiPic can do for them.
  • get_integration_guideStep-by-step integration instructions for actually compressing images — either through the @pipic/cli command-line tool (best for whole directories) or over plain HTTP (no Node req…Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "directory": it reads files.
    • untrusted-inputThe description's first sentence says "http": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Step-by-step integration instructions for actually compressing images — either through the @pipic/cli command-line tool (best for whole directories) or over plain HTTP (no Node required). Includes the output contract, exit codes, error codes and which failures are worth retrying.

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 data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
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:31 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
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://pipic.cc/.well-known/oauth-protected-resource
Authorization servers
https://pipic.cc
Legacy HTTP+SSE transport
no
Dynamic client registration
no
Client ID metadata documents
no
  • WarnThe whole server

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

    Matched text

    https://pipic.cc/mcp: tools/list returned 3 tools to an anonymous client, including check_image_supported (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 pipic https://pipic.cc/mcp
claude mcp add --transport http pipic https://pipic.cc/mcp

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__pipic__get_compression_facts",
      "mcp__pipic__get_integration_guide"
    ],
    "ask": [
      "mcp__pipic__check_image_supported"
    ],
    "deny": []
  }
}

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 pipic. Review it before you use it.

Capability tags behind 2 rules
  • mcp__pipic__get_compression_facts private-data, untrusted-input
  • mcp__pipic__get_integration_guide 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/cc.pipic/pipic/verify?hash=cd220d53c9fdd6e378419c662f076df34b541bf4b103c6c08705c4ec0e72ae88" | jq -e '.changed == false'

Pinned hash cd220d53c9fd, from Nov 12, 2026, 08:18 UTC.

Watch

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

https://radar.anlyon.com/servers/cc.pipic/pipic/changes.xml

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

Badge

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

Source: MCP Registry. Synced Oct 21, 2026, 17:46 UTC.

PiPic Integration Guide MCP server: questions and answers

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

Is the PiPic Integration Guide MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 1 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 PiPic Integration Guide MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the PiPic Integration Guide 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 PiPic Integration Guide MCP server have?

3 tools: 1 write, 2 read. check_image_supported, get_compression_facts and get_integration_guide.

Does the PiPic Integration Guide MCP server need sign-in or OAuth?

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

Does the PiPic Integration Guide MCP server send data to outside services?

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

Has the PiPic Integration Guide MCP server changed its tools?

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