# io.airpipe/airpipe

Build, validate, deploy — HTTP APIs, cron jobs, webhooks and MCP tools — from your AI client.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 2026.7.28
- **Author:** io.airpipe
- **License:** Unknown
- **Endpoints:** streamable-http https://api.airpipe.io/mcp
- **Source:** https://airpipe.io/
- **Endpoint health:** reachable (last checked 2026-09-22T05:23:58.338Z, 5 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-22T05:23:58.338Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

19 declared. Observed from a live `tools/list` probe.
- `update_module` — Update an existing reusable module by module_uuid (adds a new revision; spec_yaml is base64-encoded YAML) and optionally redeploy.
- `create_module` — Create a reusable module (a typed config fragment referenced by handle) and optionally deploy it to staging or production. spec_yaml is base64-encoded YAML of t
- `validate_config` — Schema-validate an airpipe YAML config. Send { "yaml": <the full YAML string> }. Returns { valid: true } when it passes, or { valid: false, error: <message> } w
- `list_configs` — List the organization's AirPipe configurations.
- `list_organizations` — List the organizations you belong to and their organization_uuid. Call this first to get an organization_uuid for the config tools.
- `deploy_module_revision` — Deploy a specific past revision of a module to staging or production.
- `plan_config` — Get airpipe config-authoring instructions plus RAG-retrieved real action examples for a natural-language request, so YOU (the calling model) write the YAML your
- `get_config` — Get a single configuration's data by config_uuid, optionally with its revisions.
- `list_modules` — List the organization's reusable modules (pass revisions=true to include revision history).
- `get_module` — Get a single reusable module by uuid, including its revision history and spec.
- `update_config` — Update an existing AirPipe configuration by config_uuid (config_yaml is base64-encoded YAML) and optionally redeploy.
- `undeploy_module` — Undeploy a reusable module from an environment (STAGING or PRODUCTION).
- `create_config` — Create a new AirPipe configuration (config_yaml is base64-encoded YAML) and optionally deploy it to staging or production.
- `undeploy_config` — Undeploy a configuration from an environment (STAGING or PRODUCTION).
- `delete_config` — Delete one or more AirPipe configurations by config_uuid.
- `delete_module` — Delete one or more reusable modules by module_uuid.
- `toggle_config` — Enable or disable one or more configurations by config_uuid.
- `edit_config` — Edit an AirPipe configuration YAML with a natural-language instruction.
- `deploy_config_revision` — Deploy a specific past revision of a configuration to staging or production.

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"airpipe\": {\n      \"type\": \"http\",\n      \"url\": \"https://api.airpipe.io/mcp\"\n    }\n  }\n}"
```

## Blast radius

Extensive blast radius — deletes data; runs on someone else's infrastructure.
- Floor 34, ceiling 58 (tier: extensive)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/io.airpipe%2Fairpipe
- Install plan: https://forgeregistry.com/api/v1/packages/io.airpipe%2Fairpipe/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/io.airpipe%2Fairpipe
- HTML page: https://forgeregistry.com/registry/io.airpipe%2Fairpipe
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.