Air Pipe
REMOTE · API.AIRPIPE.IO · SCANNED SEP 27
Build, validate, deploy — HTTP APIs, cron jobs, webhooks and MCP tools — from your AI client.
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 → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 19 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1224 tokens (~64/item across 19 items; 19 tools + 0 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 Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deploy_module_revision" implies "deploy" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 20 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
How do I install the Air Pipe MCP server?
Air Pipe is a hosted endpoint at https://api.airpipe.io/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 · api.airpipe.io
claude mcp add --transport http io-airpipe-airpipe 'https://api.airpipe.io/mcp'
{
"mcpServers": {
"io-airpipe-airpipe": {
"url": "https://api.airpipe.io/mcp"
}
}
} {
"servers": {
"io-airpipe-airpipe": {
"type": "http",
"url": "https://api.airpipe.io/mcp"
}
}
} [mcp_servers.io-airpipe-airpipe] url = "https://api.airpipe.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-airpipe-airpipe": {
"type": "remote",
"url": "https://api.airpipe.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-airpipe-airpipe --url 'https://api.airpipe.io/mcp' --transport streamable-http
mcp_servers:
io-airpipe-airpipe:
url: "https://api.airpipe.io/mcp" {
"McpServers": {
"io-airpipe-airpipe": {
"Transport": "http",
"Url": "https://api.airpipe.io/mcp"
}
}
} assistant mcp add io-airpipe-airpipe -t streamable-http -u 'https://api.airpipe.io/mcp'
{
"mcpServers": {
"io-airpipe-airpipe": {
"type": "http",
"url": "https://api.airpipe.io/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.
- 25 Sept 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
- 3 Sept 26 0
- Server version: 3.8.1 → 3.10.0 functional
- 1 Sept 26 0
- Server version: 3.4.0 → 3.8.1 functional
- 31 Aug 26 0
- Server version: 3.2.1 → 3.4.0 functional
- 29 Aug 26 72
- Server version: 3.0.0 → 3.2.1 functional
- 27 Aug 26 0
- Stability: 0.97 → pass security
- Server version: 2.0.2 → 3.0.0 functional
- 26 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
- 25 Aug 26 0
- Server version: 1.44.13 → 2.0.2 functional
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 27 Sept 2026 · Probed https://api.airpipe.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=airpipe.io | CN=WE1,O=Google Trust Services,C=US | 30 Aug 2026 | 28 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 3030a5082170388b13248a619eab2767 |
| SANs: airpipe.io, *.airpipe.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.airpipe.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| airpipe.io. | 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://api.airpipe.io/mcp | Verified | 200 | |
| http (plaintext) | http://api.airpipe.io/mcp | HTTPS enforced | 301 | https://airpipe.io/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. 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 →
create_config ~82
Create a new AirPipe configuration (config_yaml is base64-encoded YAML) and optionally deploy it to staging or production.
| Name | Type | Req | Description |
|---|---|---|---|
| config_yaml | string | yes | – |
| deploy_production | string | – | – |
| deploy_staging | string | – | – |
| organization_uuid | string | – | – |
| permission | string | – | – |
| role_uuid | string | – | – |
No output schema declared.
No examples provided.
create_module ~128
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 the module body; module_type is the config struct it represents (e.g. Database).
| Name | Type | Req | Description |
|---|---|---|---|
| deploy_production | string | – | – |
| deploy_staging | string | – | – |
| description | string | – | – |
| handle | string | yes | – |
| module_type | string | yes | – |
| organization_uuid | string | – | – |
| permission | string | – | – |
| role_uuid | string | – | – |
| spec_yaml | string | yes | – |
No output schema declared.
No examples provided.
delete_config ~37
Delete one or more AirPipe configurations by config_uuid.
| Name | Type | Req | Description |
|---|---|---|---|
| config_uuids | array | yes | – |
| organization_uuid | string | yes | – |
No output schema declared.
No examples provided.
delete_module ~36
Delete one or more reusable modules by module_uuid.
| Name | Type | Req | Description |
|---|---|---|---|
| module_uuids | array | yes | – |
| organization_uuid | string | yes | – |
No output schema declared.
No examples provided.
deploy_config_revision ~46
Deploy a specific past revision of a configuration to staging or production.
| Name | Type | Req | Description |
|---|---|---|---|
| config_uuid | string | yes | – |
| organization_uuid | string | yes | – |
| revision_uuid | string | yes | – |
No output schema declared.
No examples provided.
deploy_module_revision ~46
Deploy a specific past revision of a module to staging or production.
| Name | Type | Req | Description |
|---|---|---|---|
| module_uuid | string | yes | – |
| organization_uuid | string | yes | – |
| revision_uuid | string | yes | – |
No output schema declared.
No examples provided.
edit_config ~43
Edit an AirPipe configuration YAML with a natural-language instruction.
| Name | Type | Req | Description |
|---|---|---|---|
| current_yaml | string | yes | – |
| instruction | string | yes | – |
| organization_uuid | string | yes | – |
No output schema declared.
No examples provided.
get_config ~39
Get a single configuration's data by config_uuid, optionally with its revisions.
| Name | Type | Req | Description |
|---|---|---|---|
| config_uuid | string | yes | – |
| organization_uuid | string | yes | – |
No output schema declared.
No examples provided.
get_module ~39
Get a single reusable module by uuid, including its revision history and spec.
| Name | Type | Req | Description |
|---|---|---|---|
| module_uuid | string | yes | – |
| organization_uuid | string | yes | – |
No output schema declared.
No examples provided.
list_configs ~23
List the organization's AirPipe configurations.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_uuid | string | yes | – |
No output schema declared.
No examples provided.
list_modules ~30
List the organization's reusable modules (pass revisions=true to include revision history).
| Name | Type | Req | Description |
|---|---|---|---|
| organization_uuid | string | yes | – |
No output schema declared.
No examples provided.
list_organizations ~33
List the organizations you belong to and their organization_uuid. Call this first to get an organization_uuid for the config tools.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
plan_config ~115
Get airpipe config-authoring instructions plus RAG-retrieved real action examples for a natural-language request, so YOU (the calling model) write the YAML yourself instead of the server generating it. Returns { instructions, context, request, protocol }. After writing the config, validate it with the validate_config tool (repair loop) then persist it with create_config. Prefer this over generate_config whenever you can author YAML yourself.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | – |
| organization_uuid | string | – | – |
| request | string | yes | – |
No output schema declared.
No examples provided.
toggle_config ~37
Enable or disable one or more configurations by config_uuid.
| Name | Type | Req | Description |
|---|---|---|---|
| config_uuids | array | yes | – |
| organization_uuid | string | yes | – |
No output schema declared.
No examples provided.
undeploy_config ~47
Undeploy a configuration from an environment (STAGING or PRODUCTION).
| Name | Type | Req | Description |
|---|---|---|---|
| config_uuid | string | yes | – |
| environment | string | yes | – |
| organization_uuid | string | yes | – |
No output schema declared.
No examples provided.
undeploy_module ~48
Undeploy a reusable module from an environment (STAGING or PRODUCTION).
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | yes | – |
| module_uuid | string | yes | – |
| organization_uuid | string | yes | – |
No output schema declared.
No examples provided.
update_config ~89
Update an existing AirPipe configuration by config_uuid (config_yaml is base64-encoded YAML) and optionally redeploy.
| Name | Type | Req | Description |
|---|---|---|---|
| config_uuid | string | – | – |
| config_yaml | string | yes | – |
| deploy_production | string | – | – |
| deploy_staging | string | – | – |
| organization_uuid | string | – | – |
| permission | string | – | – |
| role_uuid | string | – | – |
No output schema declared.
No examples provided.
update_module ~115
Update an existing reusable module by module_uuid (adds a new revision; spec_yaml is base64-encoded YAML) and optionally redeploy.
| Name | Type | Req | Description |
|---|---|---|---|
| deploy_production | string | – | – |
| deploy_staging | string | – | – |
| description | string | – | – |
| handle | string | yes | – |
| module_type | string | yes | – |
| module_uuid | string | – | – |
| organization_uuid | string | – | – |
| permission | string | – | – |
| role_uuid | string | – | – |
| spec_yaml | string | yes | – |
No output schema declared.
No examples provided.
validate_config ~92
Schema-validate an airpipe YAML config. Send { "yaml": <the full YAML string> }. Returns { valid: true } when it passes, or { valid: false, error: <message> } when it fails — feed the error back into your fix and call again until valid. Schema check only; does not save. Use create_config to persist a valid config.
| Name | Type | Req | Description |
|---|---|---|---|
| yaml | string | yes | – |
No output schema declared.
No examples provided.
What is the Air Pipe MCP server?
Air Pipe is an MCP server listed in the public MCP registry as io.airpipe/airpipe. Build, validate, deploy, HTTP APIs, cron jobs, webhooks and MCP tools, from your AI client. This page covers its hosted endpoint (https://api.airpipe.io/mcp).
Is the Air Pipe MCP server safe to use?
Air Pipe scores 72 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 Air Pipe MCP server expose?
Air Pipe exposes 19 tools: update_module, create_module, validate_config, list_configs, list_organizations, and 14 more. Their descriptions and schemas cost roughly 1,125 tokens of context every time the server is loaded.
Does the Air Pipe MCP server require authentication?
No. We connected to Air Pipe without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Air Pipe MCP server still maintained?
Air Pipe is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.