Aiyogg_tinypng Mcp Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Aiyogg TinyPNG MCP Server?

Aiyogg TinyPNG MCP Server is a server application that allows users to compress images using the TinyPNG API, providing an efficient way to reduce image file sizes for web and application use.

how to use Aiyogg TinyPNG MCP Server?

To use the server, you need to install the necessary dependencies, configure the mcp.json file with your TinyPNG API key, and then run the server using either bun or node.

key features of Aiyogg TinyPNG MCP Server?

  • Compress local and remote images using the TinyPNG API.
  • Easy configuration through a JSON file.
  • Supports various output formats for compressed images.

use cases of Aiyogg TinyPNG MCP Server?

  1. Reducing the size of images for faster web page loading.
  2. Compressing images for mobile applications to save bandwidth.
  3. Automating image compression in development workflows.

FAQ from Aiyogg TinyPNG MCP Server?

  • What is the required API key for?

The API key is necessary to authenticate your requests to the TinyPNG service for image compression.

  • Can I compress images in bulk?

Yes, you can set up scripts to compress multiple images by calling the server with different image paths.

  • Is there a limit to the size of images I can compress?

Yes, TinyPNG has limitations on the size of images that can be compressed, which is typically around 5MB per image.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
-
License
Apache-2.0 license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago