# Applire (oci · ghcr.io/applire/applire-backend)

Self-hosted job applications: vault, truthfulness audit, CVs. Needs a running Applire instance.

- Trust score: 10/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

- oci · `ghcr.io/applire/applire-backend`: 10/100 (this document), [markdown](https://verifymcp.io/servers/applire-applire/ghcr-io-applire-applire-backend.md), [page](https://verifymcp.io/servers/applire-applire/ghcr-io-applire-applire-backend)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/applire/applire-backend`
- Version: `0.46.0-beta`
- 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-22.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (AGPL-3.0).
  - Actively maintained (last published 9 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **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: 6 categories.** Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

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

Applire runs locally as a container image, launched with docker run --rm -i -e APPLIRE_AGENT_TOKEN ghcr.io/applire/applire-backend:0.46.0-beta python -m applire.mcp, plus the required --env-file, which you supply. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add applire-applire -- docker run --rm -i -e APPLIRE_AGENT_TOKEN ghcr.io/applire/applire-backend:0.46.0-beta python -m applire.mcp
```

This image reads APPLIRE_AGENT_TOKEN. Set it in your client's env block for this server; docker run -e passes it through to the container. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks --env-file as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Cursor

```json
{
  "mcpServers": {
    "applire-applire": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "APPLIRE_AGENT_TOKEN",
        "ghcr.io/applire/applire-backend:0.46.0-beta",
        "python",
        "-m",
        "applire.mcp"
      ]
    }
  }
}
```

This image reads APPLIRE_AGENT_TOKEN. Set it in your client's env block for this server; docker run -e passes it through to the container. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks --env-file as required and gives no value we can show, so it is not in this command. Add it before you run it.

### VS Code

```json
{
  "servers": {
    "applire-applire": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "APPLIRE_AGENT_TOKEN",
        "ghcr.io/applire/applire-backend:0.46.0-beta",
        "python",
        "-m",
        "applire.mcp"
      ]
    }
  }
}
```

This image reads APPLIRE_AGENT_TOKEN. Set it in your client's env block for this server; docker run -e passes it through to the container. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks --env-file as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Codex

```bash
codex mcp add applire-applire -- docker run --rm -i -e APPLIRE_AGENT_TOKEN ghcr.io/applire/applire-backend:0.46.0-beta python -m applire.mcp
```

This image reads APPLIRE_AGENT_TOKEN. Set it in your client's env block for this server; docker run -e passes it through to the container. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks --env-file as required and gives no value we can show, so it is not in this command. Add it before you run it.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "applire-applire": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "APPLIRE_AGENT_TOKEN",
        "ghcr.io/applire/applire-backend:0.46.0-beta",
        "python",
        "-m",
        "applire.mcp"
      ],
      "enabled": true
    }
  }
}
```

This image reads APPLIRE_AGENT_TOKEN. Set it in your client's env block for this server; docker run -e passes it through to the container. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks --env-file as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Hermes

```yaml
mcp_servers:
  applire-applire:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "APPLIRE_AGENT_TOKEN", "ghcr.io/applire/applire-backend:0.46.0-beta", "python", "-m", "applire.mcp"]
```

This image reads APPLIRE_AGENT_TOKEN. Set it in your client's env block for this server; docker run -e passes it through to the container. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks --env-file as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Netclaw

```json
{
  "McpServers": {
    "applire-applire": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "APPLIRE_AGENT_TOKEN",
        "ghcr.io/applire/applire-backend:0.46.0-beta",
        "python",
        "-m",
        "applire.mcp"
      ]
    }
  }
}
```

This image reads APPLIRE_AGENT_TOKEN. Set it in your client's env block for this server; docker run -e passes it through to the container. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks --env-file as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Other

```json
{
  "mcpServers": {
    "applire-applire": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "APPLIRE_AGENT_TOKEN",
        "ghcr.io/applire/applire-backend:0.46.0-beta",
        "python",
        "-m",
        "applire.mcp"
      ]
    }
  }
}
```

This image reads APPLIRE_AGENT_TOKEN. Set it in your client's env block for this server; docker run -e passes it through to the container. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks --env-file as required and gives no value we can show, so it is not in this command. Add it before you run it.

## 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-12 (score 10, 0)

- [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] 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] 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] 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.45.0-beta → 0.46.0-beta

### 2026-11-10 (score 10)

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. The full working is on the page: https://verifymcp.io/servers/applire-applire/ghcr-io-applire-applire-backend#diagnostics

## Score history

- 2026-11-22: 10
- 2026-11-21: 10
- 2026-11-20: 10
- 2026-11-19: 10
- 2026-11-18: 10
- 2026-11-17: 10
- 2026-11-16: 10
- 2026-11-15: 10
- 2026-11-14: 10
- 2026-11-13: 10
- 2026-11-12: 10
- 2026-11-11: 10
- 2026-11-10: 10

## Common questions

### What is the Applire MCP server?

Applire is an MCP server listed in the public MCP registry as io.github.Applire/applire. Self-hosted job applications: vault, truthfulness audit, CVs. Needs a running Applire instance. This page covers its container image (ghcr.io/applire/applire-backend).

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

Applire scores 10 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.

### Is the Applire MCP server still maintained?

Applire is still listed as active in the MCP registry. We last reached this channel on 22 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 Applire MCP server under?

Applire declares the AGPL-3.0 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 Applire MCP server?

VerifyMCP ran 5 checks on Applire, covering Source repository, Provenance, License, Maintenance and 1 more. 9 items could not be completed, a gap on our side rather than a finding about Applire: Malware scan, Known CVEs, Install scripts, Dependency health and 5 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- GitHub Container Registry: https://ghcr.io/applire/applire-backend
- Repository: https://github.com/Applire/Applire
- Website: https://applire.de/
- Changelog RSS feed: https://verifymcp.io/servers/applire-applire/ghcr-io-applire-applire-backend.xml
- Changelog JSON feed: https://verifymcp.io/servers/applire-applire/ghcr-io-applire-applire-backend/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/applire-applire/ghcr-io-applire-applire-backend.json
- HTML version of this page: https://verifymcp.io/servers/applire-applire/ghcr-io-applire-applire-backend
