# Razi Media Tools (remote · www.razi.pro)

Image processing over MCP: compress and split images, generate images and QR codes.

- Trust score: 36/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `www.razi.pro`: 36/100 (this document), [markdown](https://verifymcp.io/servers/razikallayi-razi-media/api-mcp-media.md), [page](https://verifymcp.io/servers/razikallayi-razi-media/api-mcp-media)

## Channel facts

- Endpoint: `https://www.razi.pro/api/mcp/media`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**Unverified: 6 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Razi Media Tools MCP server?

Razi Media Tools is a hosted endpoint at https://www.razi.pro/api/mcp/media, 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.

### Claude

```bash
claude mcp add --transport http razikallayi-razi-media 'https://www.razi.pro/api/mcp/media'
```

### Cursor

```json
{
  "mcpServers": {
    "razikallayi-razi-media": {
      "url": "https://www.razi.pro/api/mcp/media"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "razikallayi-razi-media": {
      "type": "http",
      "url": "https://www.razi.pro/api/mcp/media"
    }
  }
}
```

### Codex

```toml
[mcp_servers.razikallayi-razi-media]
url = "https://www.razi.pro/api/mcp/media"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "razikallayi-razi-media": {
      "type": "remote",
      "url": "https://www.razi.pro/api/mcp/media",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add razikallayi-razi-media --url 'https://www.razi.pro/api/mcp/media' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  razikallayi-razi-media:
    url: "https://www.razi.pro/api/mcp/media"
```

### Netclaw

```json
{
  "McpServers": {
    "razikallayi-razi-media": {
      "Transport": "http",
      "Url": "https://www.razi.pro/api/mcp/media"
    }
  }
}
```

### Vellum

```bash
assistant mcp add razikallayi-razi-media -t streamable-http -u 'https://www.razi.pro/api/mcp/media'
```

### Other

```json
{
  "mcpServers": {
    "razikallayi-razi-media": {
      "type": "http",
      "url": "https://www.razi.pro/api/mcp/media"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-09 (score 36, −27)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Authorization: unverified → fail
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → unverified
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-09-08 (score 63)

First indexed and scored.

## MCP tools (4)

### `compress_image` (~448 tokens)

Re-encode a single raster image to webp, jpeg, png or avif, optionally resizing it and/or converting it to grayscale. HEIC/HEIF input is converted to JPEG first, and SVG input is rasterised at 300 DPI, fitted inside 800x800 unless width or height is given. Lossy for webp, jpeg and avif at any quality below 1.0. Images only — use compress_pdf for PDFs and compress_video for video. Output shape depends on size: an input under 5MB is processed in-app and the encoded image bytes are returned, while anything larger is sent to razi.pro's worker and the reply is JSON { url, size, metadata } pointing at a hosted copy instead of bytes. Paid compute; 30 calls per hour per IP. There is no upload channel over MCP: pass `fileUrl`, a URL in razi.pro's own storage (for example the `url` returned by upload_file); third-party URLs are rejected.

Input parameters:

- `format` (string): Output container/codec. Default webp; an unrecognised value also falls back to webp. Transparency survives in webp, png and avif but not jpeg.
- `grayscale` (boolean): Drop colour before encoding. Default false.
- `height` (number): Target height in pixels. Give only one of width/height to scale the other proportionally. Omit both to keep the original dimensions.
- `keepAspectRatio` (boolean): Only has an effect when BOTH width and height are given. Default false, which centre-crops the image to fill the box exactly. Set true to fit the whole image inside the box instead, so the result may…
- `quality` (number): Encoder quality as a fraction from 0.1 to 1.0, scaled to the encoder's 0-100 range. Default 0.9. Higher means larger and closer to the original.
- `width` (number): Target width in pixels. Give only one of width/height to scale the other proportionally. Omit both to keep the original dimensions. Enlarging is allowed.

### `generate_qr_code` (~214 tokens)

Render text or a URL as a QR code image. Returns JSON { dataUrl, text, size } where dataUrl is a base64 PNG data URI embedded in the response — not a hosted link, so nothing is stored and the image cannot be fetched later. Runs locally and costs nothing. Reading a QR code is not supported, only writing one. To turn a long address into a shorter, more scannable one first, call shorten_url and pass its shortUrl here.

Input parameters:

- `errorCorrection` (string): Declared for compatibility but currently ignored — the code is always generated at the library default, level M (about 15% damage tolerance).
- `size` (number): Width and height of the output PNG in pixels; the code is always square. Default 300. Only applied when given as a number.
- `text` (string, required): The exact payload to encode. A URL must include its scheme to be actionable when scanned. Very long values force a denser code that is harder to scan.

### `generate_image` (~281 tokens)

Generate a new image from a text description with a diffusion model. Returns a single PNG; over MCP it arrives inline when under 1MB and otherwise as a stored URL that stays retrievable for about 24 hours. This invents an image from scratch — it cannot edit, upscale or restyle a picture you already have. Use compress_image to re-encode or resize an existing file. Requires a signed-in razi.pro account; an anonymous call is rejected with 401. Paid compute, 20 images per hour per account, and generation can take tens of seconds. Providers are tried in turn (Fireworks FLUX.1-schnell, Hugging Face FLUX.1-schnell, SDXL, Cloudflare SDXL, Replicate), so the model that actually ran varies with availability and there is no seed or size control. No two calls give identical output, and the image is not automatically hosted anywhere permanent.

Input parameters:

- `negativePrompt` (string): What to keep out of the image, e.g. 'text, watermark, blurry'. Maximum 2,000 characters. Only the Replicate fallback provider honours it, so on the usual path it has no effect.
- `prompt` (string, required): What the image should show. Subject, style and composition all help. Required, non-blank, maximum 2,000 characters.

### `split_image` (~355 tokens)

Cut one storyboard, collage or grid image into its separate panels and return them as a ZIP, one file per panel in reading order. Over MCP the ZIP is not inlined: it comes back as a stored URL that stays retrievable for about 24 hours. Two modes. Give both rows and cols for an exact equal division, which is free of model cost and predictable. Omit them and a vision model locates the panels, excluding borders, gaps and captions — better on uneven layouts, but it is a paid inference whose panel count and crops can vary between runs, and it fails with 400 if it finds nothing. Panels are cropped, never resized; a lossy re-encode at quality 90 is applied for jpeg and webp. This splits one image into several — it does not split a PDF (use split_pdf) or shrink a file (use compress_image). Paid compute; 20 calls per hour per IP. There is no upload channel over MCP: pass `fileUrl`, a URL in razi.pro's own storage (for example the `url` returned by upload_file); third-party URLs are rejected.

Input parameters:

- `cols` (number): Number of equal-width columns in the grid. Only takes effect when rows is also given. Omit both rows and cols to have the panels detected automatically.
- `format` (string): Encoding for each extracted panel and its file extension inside the ZIP. Default png, which is lossless; jpeg and webp are written at quality 90.
- `rows` (number): Number of equal-height rows in the grid. Only takes effect when cols is also given; supplying both switches off vision detection and divides the image evenly, ignoring any borders or gaps.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/razikallayi-razi-media/api-mcp-media#diagnostics

## Score history

- 2026-09-20: 36
- 2026-09-19: 36
- 2026-09-18: 36
- 2026-09-17: 36
- 2026-09-16: 36
- 2026-09-15: 36
- 2026-09-14: 36
- 2026-09-13: 36
- 2026-09-12: 36
- 2026-09-11: 36
- 2026-09-10: 36
- 2026-09-09: 36
- 2026-09-08: 63

## Common questions

### What is the Razi Media Tools MCP server?

Razi Media Tools is an MCP server listed in the public MCP registry as io.github.razikallayi/razi-media. Image processing over MCP: compress and split images, generate images and QR codes. This page covers its hosted endpoint (https://www.razi.pro/api/mcp/media).

### Is the Razi Media Tools MCP server safe to use?

Razi Media Tools scores 36 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 Razi Media Tools MCP server expose?

Razi Media Tools exposes 4 tools: compress_image, generate_qr_code, generate_image, split_image. Their descriptions and schemas cost roughly 1,298 tokens of context every time the server is loaded.

### Does the Razi Media Tools MCP server require authentication?

Yes. Razi Media Tools asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Razi Media Tools MCP server still maintained?

Razi Media Tools 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.

## Links

- Remote endpoint: https://www.razi.pro/api/mcp/media
- Repository: https://github.com/razikallayi/razikallayi.com
- Website: https://www.razi.pro/developer
- Changelog RSS feed: https://verifymcp.io/servers/razikallayi-razi-media/api-mcp-media.xml
- Changelog JSON feed: https://verifymcp.io/servers/razikallayi-razi-media/api-mcp-media.json
- HTML version of this page: https://verifymcp.io/servers/razikallayi-razi-media/api-mcp-media