Is the Airpipe MCP server down?

mcp-registry/io.airpipe/airpipe · v3.11.0

healthy
Last checked 2026-10-18 22:42 UTC · handshake 443ms

As of 2026-10-18 22:42 UTC, the Airpipe MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 2 minutes.

uptime (30d checks)
100%
checks observed
3,719
outages (90d)
1
tools
19

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

Install Airpipe MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http airpipe-mcp-server https://api.airpipe.io/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "airpipe-mcp-server": {
      "type": "http",
      "url": "https://api.airpipe.io/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: D (65/100)

D (65/100): 0 error(s), 4 warning(s) across 19 tool(s); ~2,047 tokens of tool definitions.
Scores higher than 1% of 15,338 MCP servers Glimind has audited.
Its tool list costs an agent ~2,047 tokens per session — lighter than 55% of servers.
65 → 65 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints0
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability100

What to fix (5)

19 of 19 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: create_config, create_module, delete_config, delete_module, deploy_config_revision and 14 more

63 parameter(s) across 18 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: create_config, create_module, delete_config, delete_module, deploy_config_revision and 13 more

8 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: create_config, create_module, delete_config, delete_module, deploy_config_revision and 3 more

Handshake + tools/list takes ~1,795 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 14 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 18 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.airpipe%2Fairpipe/fixes

create_config 1 change
{
  "name": "create_config",
  "description": "Create a new AirPipe configuration (config_yaml is base64-encoded YAML) and optionally deploy it to staging or production.",
  "inputSchema": {
    "type": "object",
    "required": [
      "config_yaml"
    ],
    "properties": {
      "role_uuid": {
        "type": "string"
      },
      "permission": {
        "type": "string"
      },
      "config_yaml": {
        "type": "string"
      },
      "deploy_staging": {
        "type": "string"
      },
      "deploy_production": {
        "type": "string"
      },
      "organization_uuid": {
        "type": "string",
        "format": "uuid"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
create_module 1 change
{
  "name": "create_module",
  "description": "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).",
  "inputSchema": {
    "type": "object",
    "required": [
      "handle",
      "module_type",
      "spec_yaml"
    ],
    "properties": {
      "handle": {
        "type": "string"
      },
      "role_uuid": {
        "type": "string"
      },
      "spec_yaml": {
        "type": "string"
      },
      "permission": {
        "type": "string"
      },
      "description": {
        "type": "string"
      },
      "module_type": {
        "type": "string"
      },
      "deploy_staging": {
        "type": "string"
      },
      "deploy_production": {
        "type": "string"
      },
      "organization_uuid": {
        "type": "string",
        "format": "uuid"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
delete_config 1 change
{
  "name": "delete_config",
  "description": "Delete one or more AirPipe configurations by config_uuid.",
  "inputSchema": {
    "type": "object",
    "required": [
      "organization_uuid",
      "config_uuids"
    ],
    "properties": {
      "config_uuids": {
        "type": "array"
      },
      "organization_uuid": {
        "type": "string",
        "format": "uuid"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.airpipe/airpipe"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.airpipe/airpipe"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.airpipe%2Fairpipe.svg)](https://glimind.com/server/mcp-registry%2Fio.airpipe%2Fairpipe?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.airpipe%2Fairpipe?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.airpipe%2Fairpipe.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.airpipe%2Fairpipe.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.airpipe%2Fairpipe?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:2857b473d3f9a0f0…, first seen 2026-10-17, included at leaf 6891 of 23,647. Version history · verify what your client received.

Tools (19)

Compare: most reliable devops servers · most reliable code servers · most reliable other servers · most reliable knowledge servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Airpipe MCP server down right now?

As of 2026-10-18 22:42 UTC, the Airpipe MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 2 minutes.

How many tools does Airpipe MCP server provide?

Airpipe MCP server advertises 19 tools, including create_config, create_module, delete_config, delete_module, deploy_config_revision.

How do I install Airpipe MCP server?

Point your MCP client at this streamable-http endpoint: https://api.airpipe.io/mcp

Is the Airpipe MCP server safe to connect to an AI agent?

Glimind scanned all 19 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Airpipe MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve