# Pipe2.ai (remote · mcp.pipe2.ai)

Run multi-step AI pipelines for video, image, audio and text: upload media, run, poll results.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.pipe2.ai`: 66/100 (this document), [markdown](https://verifymcp.io/servers/ai-pipe2-mcp/mcp.md), [page](https://verifymcp.io/servers/ai-pipe2-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.pipe2.ai/mcp`
- 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-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (run_pipeline).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 536 tokens (~67/item across 8 items; 5 tools + 3 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ai-pipe2-mcp https://mcp.pipe2.ai/mcp
```

### Codex

```toml
[mcp_servers.ai-pipe2-mcp]
url = "https://mcp.pipe2.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-pipe2-mcp": {
      "type": "remote",
      "url": "https://mcp.pipe2.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-pipe2-mcp --url https://mcp.pipe2.ai/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-pipe2-mcp:
    url: "https://mcp.pipe2.ai/mcp"
```

### Other

```json
{
  "mcpServers": {
    "ai-pipe2-mcp": {
      "type": "http",
      "url": "https://mcp.pipe2.ai/mcp"
    }
  }
}
```

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-08-02 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 65, 0)

- [security] Tool “get_pipeline_run_status” no longer declares itself destructive
- [security] Tool “list_pipelines” no longer declares itself destructive
- [security] Tool “request_upload” no longer declares itself destructive
- [security] Tool “get_pipeline_schema” no longer declares itself destructive
- [functional improvement] Stability: unverified → 0.03
- [functional improvement] Tool “get_pipeline_run_status” now declares an output schema
- [functional improvement] Tool “get_pipeline_schema” now declares an output schema
- [functional improvement] Tool “list_pipelines” now declares an output schema
- [functional improvement] Tool “request_upload” now declares an output schema
- [functional improvement] Tool “run_pipeline” now declares an output schema
- [functional] First check of Tool coverage: 100

### 2026-07-31 (score 65)

First indexed and scored.

## MCP tools (5)

### `get_pipeline_run_status` (~58 tokens)

Check the status of a pipeline run. Returns status (pending/running/completed/failed), output data, error messages, timestamps, and generated asset URLs.

Input parameters:

- `run_id` (string, required): The pipeline run ID returned by run_pipeline

Output parameters:

- `assets` (array)
- `completed_at` (string)
- `created_at` (string)
- `credits_charged` (integer)
- `error_message` (string)
- `id` (string)
- `input`
- `output`
- `pipeline` (object)
- `share_token` (string)
- `share_watermark` (boolean)
- `status` (string)
- `workflow_execution` (object)

### `get_pipeline_schema` (~67 tokens)

Get the input schema for a specific pipeline. Returns the JSON Schema describing required and optional input fields. Use this before running a pipeline to understand what inputs are needed.

Input parameters:

- `pipeline_slug` (string, required): The slug identifier of the pipeline (e.g., 'image-generator', 'video-generator')

Output parameters:

- `category` (string)
- `input_schema` (object)
- `name` (string)
- `providers` (array)
- `slug` (string)

### `list_pipelines` (~37 tokens)

List all available AI video/image pipelines. Returns name, slug, description, category, credit cost, and required providers for each active pipeline.

Output parameters:

- `pipelines` (array)

### `request_upload` (~190 tokens)

Request a presigned S3 upload URL for a file. Use this for pipeline inputs that require file URLs (e.g., images, videos, audio).

\**Two-step upload flow:**
1\. Call this tool with filename and content_type to get a presigned upload URL and final asset URL
2\. PUT the file contents to the upload_url (presigned, expires in 5 minutes)
3\. Use the asset_url as the input value when running a pipeline

Supported content types: image/* (max 10MB), video/* (max 50MB), audio/* (max 20MB)

Input parameters:

- `content_type` (string, required): MIME type of the file (e.g., 'image/jpeg', 'image/png', 'video/mp4', 'audio/mpeg')
- `filename` (string, required): Name of the file to upload (e.g., 'photo.jpg', 'video.mp4')

Output parameters:

- `asset_url` (string)
- `key` (string)
- `upload_url` (string)

### `run_pipeline` (~97 tokens)

Run an AI pipeline by slug with the given input. Use list_pipelines to discover available pipelines and get_pipeline_schema to see required inputs. Returns a run ID for tracking status.

Input parameters:

- `input` (object, required): Pipeline input fields as a JSON object. Use get_pipeline_schema to see required fields for each pipeline.
- `pipeline_slug` (string, required): The slug identifier of the pipeline to run (e.g., 'image-generator', 'video-generator')

Output parameters:

- `run_id` (string)
- `workflow_id` (string)

## Diagnostics

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

## Score history

- 2026-08-03: 66
- 2026-08-02: 66
- 2026-08-01: 65
- 2026-07-31: 65

## Links

- Remote endpoint: https://mcp.pipe2.ai/mcp
- Website: https://pipe2.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-pipe2-mcp/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-pipe2-mcp/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-pipe2-mcp/mcp