PiPic Integration Guide
REMOTE · PIPIC.CC · SCANNED SEP 20
Read-only PiPic CLI and HTTP API guidance; no image bytes are transferred.
Available components
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 Security60
- 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 3 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 389 tokens (~77/item across 5 items; 3 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 (33% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
How do I install the PiPic Integration Guide MCP server?
PiPic Integration Guide is a hosted endpoint at https://pipic.cc/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 · pipic.cc
claude mcp add --transport http cc-pipic-pipic 'https://pipic.cc/mcp'
{
"mcpServers": {
"cc-pipic-pipic": {
"url": "https://pipic.cc/mcp"
}
}
} {
"servers": {
"cc-pipic-pipic": {
"type": "http",
"url": "https://pipic.cc/mcp"
}
}
} [mcp_servers.cc-pipic-pipic] url = "https://pipic.cc/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cc-pipic-pipic": {
"type": "remote",
"url": "https://pipic.cc/mcp",
"enabled": true
}
}
} openclaw mcp add cc-pipic-pipic --url 'https://pipic.cc/mcp' --transport streamable-http
mcp_servers:
cc-pipic-pipic:
url: "https://pipic.cc/mcp" {
"McpServers": {
"cc-pipic-pipic": {
"Transport": "http",
"Url": "https://pipic.cc/mcp"
}
}
} assistant mcp add cc-pipic-pipic -t streamable-http -u 'https://pipic.cc/mcp'
{
"mcpServers": {
"cc-pipic-pipic": {
"type": "http",
"url": "https://pipic.cc/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Probed https://pipic.cc/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pipic.cc | CN=WE1,O=Google Trust Services,C=US | 12 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 9d49fea1a9912595132c131dec75a82b |
| SANs: pipic.cc, *.pipic.cc | ||||||
| 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 secure
Validation of pipic.cc. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cc. | present | 12593 | 13 | Verified |
| pipic.cc. | present | 2371 | 13 | Verified |
| pipic.cc. | Verified address RRset verified with the apex keys |
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://pipic.cc/mcp | Verified | 200 | |
| http (plaintext) | http://pipic.cc/mcp | HTTPS enforced | 301 | https://pipic.cc/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_image_supported Check a file before uploading it ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contentType | string | – | MIME type, if you already know it. Takes precedence over filename. |
| filename | string | – | File name or path; the extension is used to infer the type. |
| sizeBytes | integer | – | File size in bytes, if known. |
| Name | Type | Req | Description |
|---|---|---|---|
| contentType | string|null | – | The MIME type that was determined, to send as the Content-Type header. |
| reason | string | yes | Why — including which error code an upload would return. |
| supported | boolean | yes | Whether PiPic will accept this image. |
No examples provided.
get_compression_facts PiPic capabilities and limits ~54
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_integration_guide How to compress images with PiPic ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | yes | "cli" for the @pipic/cli tool, "http" for calling POST /compress/image directly. |
No output schema declared.
No examples provided.
What is the PiPic Integration Guide MCP server?
PiPic Integration Guide is an MCP server listed in the public MCP registry as cc.pipic/pipic. Read-only PiPic CLI and HTTP API guidance; no image bytes are transferred. This page covers its hosted endpoint (https://pipic.cc/mcp).
Is the PiPic Integration Guide MCP server safe to use?
PiPic Integration Guide scores 82 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 PiPic Integration Guide MCP server expose?
PiPic Integration Guide exposes 3 tools: get_compression_facts, get_integration_guide, check_image_supported. Their descriptions and schemas cost roughly 266 tokens of context every time the server is loaded.
Does the PiPic Integration Guide MCP server require authentication?
No. We connected to PiPic Integration Guide without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PiPic Integration Guide MCP server still maintained?
PiPic Integration Guide is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.