Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Pipe2.ai

REMOTE · MCP.PIPE2.AI · SCANNED SEP 20

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

Available components

0 this week 79 Trust /100
Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability80
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 536 tokens (~67/item across 8 items; 5 tools + 3 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 (100% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
Install

How do I install the Pipe2.ai MCP server?

Pipe2.ai is a hosted endpoint at https://mcp.pipe2.ai/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 · mcp.pipe2.ai

# add to Claude Code
claude mcp add --transport http ai-pipe2-mcp 'https://mcp.pipe2.ai/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "ai-pipe2-mcp": {
      "url": "https://mcp.pipe2.ai/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ai-pipe2-mcp": {
      "type": "http",
      "url": "https://mcp.pipe2.ai/mcp"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-pipe2-mcp --url 'https://mcp.pipe2.ai/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ai-pipe2-mcp:
    url: "https://mcp.pipe2.ai/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ai-pipe2-mcp": {
      "Transport": "http",
      "Url": "https://mcp.pipe2.ai/mcp"
    }
  }
}
# add to Vellum
assistant mcp add ai-pipe2-mcp -t streamable-http -u 'https://mcp.pipe2.ai/mcp'
// mcp.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 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.

  • 30 Aug 26 0
    • Stability: 0.97 → pass security
  • 29 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Aug 26 +1

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

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 1 Aug 26 0
    • Tool “get_pipeline_run_status” no longer declares itself destructive security
    • Tool “get_pipeline_schema” no longer declares itself destructive security
    • Tool “list_pipelines” no longer declares itself destructive security
    • Tool “request_upload” no longer declares itself destructive security
    • Stability: unverified → 0.03 functional
    • Tool “get_pipeline_run_status” now declares an output schema functional
    • Tool “get_pipeline_schema” now declares an output schema functional
    • Tool “list_pipelines” now declares an output schema functional
    • Tool “request_upload” now declares an output schema functional
    • Tool “run_pipeline” now declares an output schema functional
    • First check of Tool coverage: 100 functional
  • 31 Jul 26 0

    First indexed and scored.

Diagnostics

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://mcp.pipe2.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.pipe2.ai CN=YR1,O=Let's Encrypt,C=US 22 Aug 2026 20 Nov 2026 RSA 4096 SHA256-RSA 66645ef6fb2d994f015d897e0e45d868cdf
SANs: mcp.pipe2.ai
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.pipe2.ai. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
pipe2.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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://mcp.pipe2.ai/mcp Verified 200
http (plaintext) http://mcp.pipe2.ai/mcp HTTPS enforced 301 https://mcp.pipe2.ai/mcp
MCP tools · 5 exposed · ~449 tokens

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 →

Tool Tokens
get_pipeline_run_status ~58

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

NameTypeReqDescription
run_idstringyesThe pipeline run ID returned by run_pipeline
NameTypeReqDescription
agent_actual_credits_mcintegeryes
assetsarrayyes
completed_atstringyes
created_atstringyes
credits_chargedintegeryes
error_messagestringyes
idstringyes
inputyes
outputyes
parent_run_idstringyes
pipelineobjectyes
share_tokenstringyes
share_watermarkbooleanyes
statusstringyes
workflow_executionobjectyes

No examples provided.

get_pipeline_schema ~67

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.

NameTypeReqDescription
pipeline_slugstringyesThe slug identifier of the pipeline (e.g., 'image-generator', 'video-generator')
NameTypeReqDescription
categorystringyes
input_schemaobjectyes
namestringyes
providersarray
slugstringyes

No examples provided.

list_pipelines ~37

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

Input schema present but exposes no named parameters.

NameTypeReqDescription
pipelinesarrayyes

No examples provided.

request_upload ~190

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)

NameTypeReqDescription
content_typestringyesMIME type of the file (e.g., 'image/jpeg', 'image/png', 'video/mp4', 'audio/mpeg')
filenamestringyesName of the file to upload (e.g., 'photo.jpg', 'video.mp4')
NameTypeReqDescription
asset_urlstringyes
keystringyes
upload_urlstringyes

No examples provided.

run_pipeline ~97

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.

NameTypeReqDescription
inputobjectyesPipeline input fields as a JSON object. Use get_pipeline_schema to see required fields for each pipeline.
pipeline_slugstringyesThe slug identifier of the pipeline to run (e.g., 'image-generator', 'video-generator')
NameTypeReqDescription
run_idstringyes
workflow_idstringyes

No examples provided.

Common questions

What is the Pipe2.ai MCP server?

Pipe2.ai is an MCP server listed in the public MCP registry as ai.pipe2/mcp. Run multi-step AI pipelines for video, image, audio and text: upload media, run, poll results. This page covers its hosted endpoint (https://mcp.pipe2.ai/mcp).

Is the Pipe2.ai MCP server safe to use?

Pipe2.ai scores 79 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 Pipe2.ai MCP server expose?

Pipe2.ai exposes 5 tools: get_pipeline_run_status, get_pipeline_schema, list_pipelines, request_upload, run_pipeline. Their descriptions and schemas cost roughly 449 tokens of context every time the server is loaded.

Does the Pipe2.ai MCP server require authentication?

No. We connected to Pipe2.ai without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Pipe2.ai MCP server still maintained?

Pipe2.ai 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.