Skip to content

Air Pipe MCP server

io.airpipe/airpipeairpipe.iostreamable-httpv2026.7.28Scanned

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

19 tools: 2 can delete or cancel things, 10 change things and 7 only read.

Tools: 2 delete, 0 irreversible, 10 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Air Pipe MCP server can do

The Air Pipe MCP server is published by airpipe.io, a domain the MCP Registry verified. It has 19 tools. It can delete or cancel things (2 tools: delete_module and delete_config) and create or change data (10 tools: toggle_config, edit_config, create_config, deploy_module_revision and 6 more). 7 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 15, 2026, version 2026.7.28.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

19 tools

Deletes or cancels 2Claude Code: deny
  • delete_configDelete one or more AirPipe configurations by config_uuid.No findings

    Why it is in this group

    • The name "delete_config" says "delete": a word for removing or ending something.
    Description, as the server wrote it
    Delete one or more AirPipe configurations by config_uuid.
  • delete_moduleDelete one or more reusable modules by module_uuid.No findings

    Why it is in this group

    • The name "delete_module" says "delete": a word for removing or ending something.
    Description, as the server wrote it
    Delete one or more reusable modules by module_uuid.
Changes things 10Claude Code: ask
  • create_configCreate a new AirPipe configuration (config_yaml is base64-encoded YAML) and optionally deploy it to staging or production.No findings

    Why it is in this group

    • The name "create_config" says "create": a word for a change.
    Description, as the server wrote it
    Create a new AirPipe configuration (config_yaml is base64-encoded YAML) and optionally deploy it to staging or production.
  • create_moduleCreate a reusable module (a typed config fragment referenced by handle) and optionally deploy it to staging or production.No findings

    Why it is in this group

    • The name "create_module" says "create": a word for a change.
    Description, as the server wrote it
    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).
  • deploy_config_revisionDeploy a specific past revision of a configuration to staging or production.No findings

    Why it is in this group

    • The name "deploy_config_revision" says "deploy": a word for a change.
    Description, as the server wrote it
    Deploy a specific past revision of a configuration to staging or production.
  • deploy_module_revisionDeploy a specific past revision of a module to staging or production.No findings

    Why it is in this group

    • The name "deploy_module_revision" says "deploy": a word for a change.
    Description, as the server wrote it
    Deploy a specific past revision of a module to staging or production.
  • edit_configEdit an AirPipe configuration YAML with a natural-language instruction.No findings

    Why it is in this group

    • The name "edit_config" says "edit": a word for a change.
    Description, as the server wrote it
    Edit an AirPipe configuration YAML with a natural-language instruction.
  • toggle_configEnable or disable one or more configurations by config_uuid.No findings

    Why it is in this group

    • The name "toggle_config" says "toggle": a word for a change.
    Description, as the server wrote it
    Enable or disable one or more configurations by config_uuid.
  • undeploy_configUndeploy a configuration from an environment (STAGING or PRODUCTION).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Undeploy a configuration from an environment (STAGING or PRODUCTION).
  • undeploy_moduleUndeploy a reusable module from an environment (STAGING or PRODUCTION).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Undeploy a reusable module from an environment (STAGING or PRODUCTION).
  • update_configUpdate an existing AirPipe configuration by config_uuid (config_yaml is base64-encoded YAML) and optionally redeploy.No findings

    Why it is in this group

    • The name "update_config" says "update": a word for a change.
    Description, as the server wrote it
    Update an existing AirPipe configuration by config_uuid (config_yaml is base64-encoded YAML) and optionally redeploy.
  • update_moduleUpdate an existing reusable module by module_uuid (adds a new revision; spec_yaml is base64-encoded YAML) and optionally redeploy.No findings

    Why it is in this group

    • The name "update_module" says "update": a word for a change.
    Description, as the server wrote it
    Update an existing reusable module by module_uuid (adds a new revision; spec_yaml is base64-encoded YAML) and optionally redeploy.
Only reads 7Show 7 read-only tools
  • get_configGet a single configuration's data by config_uuid, optionally with its revisions.No findings

    Why it is in this group

    • The name "get_config" says "get": a word for reading.
    Description, as the server wrote it
    Get a single configuration's data by config_uuid, optionally with its revisions.
  • get_moduleGet a single reusable module by uuid, including its revision history and spec.No findings

    Why it is in this group

    • The name "get_module" says "get": a word for reading.
    Description, as the server wrote it
    Get a single reusable module by uuid, including its revision history and spec.
  • list_configsList the organization's AirPipe configurations.No findings

    Why it is in this group

    • The name "list_configs" says "list": a word for reading.
    Description, as the server wrote it
    List the organization's AirPipe configurations.
  • list_modulesList the organization's reusable modules (pass revisions=true to include revision history).No findings

    Why it is in this group

    • The name "list_modules" says "list": a word for reading.
    Description, as the server wrote it
    List the organization's reusable modules (pass revisions=true to include revision history).
  • list_organizationsList the organizations you belong to and their organization_uuid.No findings

    Why it is in this group

    • The name "list_organizations" says "list": a word for reading.
    Description, as the server wrote it
    List the organizations you belong to and their organization_uuid. Call this first to get an organization_uuid for the config tools.
  • plan_configGet 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 …No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    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.
  • validate_configSchema-validate an airpipe YAML config.No findings

    Why it is in this group

    • The name "validate_config" says "validate": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:55 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
12
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 12 tools that change things (2 destructive, 10 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.airpipe.io/mcp: tools/list returned 19 tools to an anonymous client, including delete_module (destructive), delete_config (destructive), toggle_config (write), edit_config (write), create_config (write) and 7 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 2026.7.28. Values in angle brackets are yours to fill in.

claude mcp add --transport http airpipe https://api.airpipe.io/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http airpipe https://api.airpipe.io/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__airpipe__list_modules",
      "mcp__airpipe__validate_config",
      "mcp__airpipe__list_configs",
      "mcp__airpipe__plan_config",
      "mcp__airpipe__get_config",
      "mcp__airpipe__list_organizations",
      "mcp__airpipe__get_module"
    ],
    "ask": [
      "mcp__airpipe__toggle_config",
      "mcp__airpipe__edit_config",
      "mcp__airpipe__create_config",
      "mcp__airpipe__deploy_module_revision",
      "mcp__airpipe__deploy_config_revision",
      "mcp__airpipe__create_module",
      "mcp__airpipe__update_config",
      "mcp__airpipe__update_module",
      "mcp__airpipe__undeploy_module",
      "mcp__airpipe__undeploy_config"
    ],
    "deny": [
      "mcp__airpipe__delete_module",
      "mcp__airpipe__delete_config"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as airpipe. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.airpipe/airpipe/verify?hash=19c5a9d538e6eca6e5981dc0ad9b2790da47133117c588ab9bced3c397f00b0b" | jq -e '.changed == false'

Pinned hash 19c5a9d538e6, from Nov 15, 2026, 13:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.airpipe/airpipe/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.airpipe/airpipe
[![Anlyon Radar](https://radar.anlyon.com/badge/io.airpipe/airpipe.svg)](https://radar.anlyon.com/servers/io.airpipe/airpipe)

Source: MCP Registry. Synced Oct 21, 2026, 18:13 UTC.

Air Pipe MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Air Pipe MCP server safe?

No scan can promise that. What its definitions show: 19 tools, 12 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Air Pipe MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: delete_module and delete_config.

Can the Air Pipe MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Air Pipe MCP server have?

19 tools: 2 destructive, 10 write, 7 read. delete_module, delete_config, toggle_config, edit_config, create_config, deploy_module_revision, deploy_config_revision, create_module and 11 more.

Does the Air Pipe MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Air Pipe MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Air Pipe MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.