# Autopo (npm · @autopo/mcp)

Run your AI-run company from Claude Code, Codex, Cursor or ChatGPT: inbox, tasks, team, Studio.

- Trust score: 34/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `autopoiesis-mcp-267405155162.us-west1.run.app`: 75/100, [markdown](https://verifymcp.io/servers/autopoiesis-ai-mcp/autopoiesis-mcp-267405155162.md), [page](https://verifymcp.io/servers/autopoiesis-ai-mcp/autopoiesis-mcp-267405155162)
- npm · `@autopo/mcp`: 34/100 (this document), [markdown](https://verifymcp.io/servers/autopoiesis-ai-mcp/autopo-mcp.md), [page](https://verifymcp.io/servers/autopoiesis-ai-mcp/autopo-mcp)

## Channel facts

- Registry: `npm`
- Package: `@autopo/mcp`
- Version: `0.6.3`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 3 of 19 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.

**Unverified: 5 categories.** Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you.

## Install

### How do I install the Autopo MCP server?

Autopo runs locally as an npm package, launched with npx -y @autopo/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add autopoiesis-ai-mcp -- npx -y @autopo/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "autopoiesis-ai-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@autopo/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "autopoiesis-ai-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@autopo/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add autopoiesis-ai-mcp -- npx -y @autopo/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "autopoiesis-ai-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@autopo/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add autopoiesis-ai-mcp --command npx --arg -y --arg @autopo/mcp
```

### Hermes

```yaml
mcp_servers:
  autopoiesis-ai-mcp:
    command: "npx"
    args: ["-y", "@autopo/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "autopoiesis-ai-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@autopo/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add autopoiesis-ai-mcp -t stdio -c npx -a -y @autopo/mcp
```

### Other

```json
{
  "mcpServers": {
    "autopoiesis-ai-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@autopo/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 34, 0)

- [security regression] Known CVEs: pass → unverified
- [security] Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Dependency health: 0.96 → unverified
- [functional] Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [functional] Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.
- [functional] Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Package version: 0.6.1 → 0.6.3
- [functional] Package version: 0.6.1 → 0.6.2

### 2026-11-03 (score 34, +11)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.96

### 2026-11-02 (score 23)

First indexed and scored.

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/autopoiesis-ai-mcp/autopo-mcp#diagnostics

## Score history

- 2026-11-05: 34
- 2026-11-04: 34
- 2026-11-03: 34
- 2026-11-02: 23

## Common questions

### What is the Autopo MCP server?

Autopo is an MCP server listed in the public MCP registry as io.github.Autopoiesis-ai/mcp. Run your AI-run company from Claude Code, Codex, Cursor or ChatGPT: inbox, tasks, team, Studio. This page covers its npm package (@autopo/mcp).

### Is the Autopo MCP server safe to use?

Autopo scores 34 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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.

### Is the Autopo MCP server still maintained?

Autopo is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Autopo MCP server under?

Autopo declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Autopo MCP server?

VerifyMCP ran 8 checks on Autopo, covering Malware scan, Known CVEs, Install scripts, Dependency health and 4 more. 6 items could not be completed, a gap on our side rather than a finding about Autopo: Security disclosure, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@autopo/mcp
- Socket report: https://socket.dev/npm/package/@autopo/mcp
- Website: https://autopoiesis.app/
- Changelog RSS feed: https://verifymcp.io/servers/autopoiesis-ai-mcp/autopo-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/autopoiesis-ai-mcp/autopo-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/autopoiesis-ai-mcp/autopo-mcp.json
- HTML version of this page: https://verifymcp.io/servers/autopoiesis-ai-mcp/autopo-mcp