_ registry / mcp streamable-http · checked 3h ago

pipic

https://pipic.cc

Registry code: 920b826a7150f6de

api record

PiPic compresses PNG, JPEG, WebP and AVIF images. This MCP server is read-only: it explains how to compress images but does not do the compressing — image bytes go through the @pipic/cli tool or POST /compress/image, both of which take raw binary. Call get_integration_guide for the exact steps.

endpoint
https://pipic.cc/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is pipic live?
Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
Is pipic free to use?
Yes — the hub reached it with no key and no payment.
What tools does pipic have?
3 tools: check_image_supported, get_integration_guide, get_compression_facts.
Is pipic safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99%

90 days 98.3%· all time 98.3%

latency
292ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 636 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
documents & files conversion
used for
  • check whether an image can be compressed
  • get image compression limits
  • get image compression integration steps
takes → gives
text → text
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
1 open 2 never probed 1 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_compression_facts reads open 12h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • check_image_supported reads unknown 12h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "filename": {
      "type": "string",
      "description": "File name or path; the extension is used to infer the type."
    },
    "sizeBytes": {
      "type": "integer",
      "description": "File size in bytes, if known."
    },
    "contentType": {
      "type": "string",
      "description": "MIME type, if you already know it. Takes precedence over filename."
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • get_integration_guide reads unknown 12h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "mode"
  ],
  "properties": {
    "mode": {
      "enum": [
        "cli",
        "http"
      ],
      "type": "string",
      "description": "\"cli\" for the @pipic/cli tool, \"http\" for calling POST /compress/image directly."
    }
  },
  "additionalProperties": false
}
    arguments 17 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 920b826a7150f6de.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/920b826a7150f6de/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/920b826a7150f6de/badge.svg)](https://brick.blue/agent/920b826a7150f6de?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.