Pipe2.ai
REMOTE · MCP.PIPE2.AI · SCANNED AUG 3
Run multi-step AI pipelines for video, image, audio and text: upload media, run, poll results.
Available components
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 →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (run_pipeline). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- 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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.pipe2.ai
claude mcp add --transport http ai-pipe2-mcp https://mcp.pipe2.ai/mcp
[mcp_servers.ai-pipe2-mcp] url = "https://mcp.pipe2.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-pipe2-mcp": {
"type": "remote",
"url": "https://mcp.pipe2.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-pipe2-mcp --url https://mcp.pipe2.ai/mcp --transport streamable-http
mcp_servers:
ai-pipe2-mcp:
url: "https://mcp.pipe2.ai/mcp" {
"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.
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.
- 2 Aug 26 +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.
- 1 Aug 26 0
- 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 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 65
First indexed and scored.
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 3 Aug 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=YR2,O=Let's Encrypt,C=US | 27 Jun 2026 | 25 Sept 2026 | RSA 4096 | SHA256-RSA | 5c40229656e7a37d8e9638a8c61d5d14a31 |
| SANs: mcp.pipe2.ai | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 |
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 |
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 |
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.
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.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | The pipeline run ID returned by run_pipeline |
| Name | Type | Req | Description |
|---|---|---|---|
| assets | array | yes | — |
| completed_at | string | yes | — |
| created_at | string | yes | — |
| credits_charged | integer | yes | — |
| error_message | string | yes | — |
| id | string | yes | — |
| input | — | yes | — |
| output | — | yes | — |
| pipeline | object | yes | — |
| share_token | string | yes | — |
| share_watermark | boolean | yes | — |
| status | string | yes | — |
| workflow_execution | object | yes | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pipeline_slug | string | yes | The slug identifier of the pipeline (e.g., 'image-generator', 'video-generator') |
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | — |
| input_schema | object | yes | — |
| name | string | yes | — |
| providers | array | — | — |
| slug | string | yes | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pipelines | array | yes | — |
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)
| Name | Type | Req | Description |
|---|---|---|---|
| content_type | string | yes | MIME type of the file (e.g., 'image/jpeg', 'image/png', 'video/mp4', 'audio/mpeg') |
| filename | string | yes | Name of the file to upload (e.g., 'photo.jpg', 'video.mp4') |
| Name | Type | Req | Description |
|---|---|---|---|
| asset_url | string | yes | — |
| key | string | yes | — |
| upload_url | string | yes | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | Pipeline input fields as a JSON object. Use get_pipeline_schema to see required fields for each pipeline. |
| pipeline_slug | string | yes | The slug identifier of the pipeline to run (e.g., 'image-generator', 'video-generator') |
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | — |
| workflow_id | string | yes | — |
No examples provided.