# io.github.init-computer/init (npm · @init-computer/mcp)

Init is the backend engineer for your coding agent.

- Trust score: 71/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- npm · `@init-computer/mcp`: 71/100 (this document), [markdown](https://verifymcp.io/servers/init-computer-init/init-computer-mcp.md), [page](https://verifymcp.io/servers/init-computer-init/init-computer-mcp)

## Channel facts

- Registry: `npm`
- Package: `@init-computer/mcp`
- Version: `0.1.8`
- 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-06.

- **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.
  - 0 of 1 dependencies flagged as unhealthy.
- **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 (MIT).
  - Actively maintained (last published 6 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 799 tokens (~88/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the io.github.init-computer/init MCP server?

io.github.init-computer/init runs locally as an npm package, launched with npx -y @init-computer/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 init-computer-init -- npx -y @init-computer/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "init-computer-init": {
      "command": "npx",
      "args": [
        "-y",
        "@init-computer/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "init-computer-init": {
      "command": "npx",
      "args": [
        "-y",
        "@init-computer/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add init-computer-init -- npx -y @init-computer/mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add init-computer-init --command npx --arg -y --arg @init-computer/mcp
```

### Hermes

```yaml
mcp_servers:
  init-computer-init:
    command: "npx"
    args: ["-y", "@init-computer/mcp"]
```

### Netclaw

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

### Vellum

```bash
assistant mcp add init-computer-init -t stdio -c npx -a -y @init-computer/mcp
```

### Other

```json
{
  "mcpServers": {
    "init-computer-init": {
      "command": "npx",
      "args": [
        "-y",
        "@init-computer/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-06 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-04 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 68, +1)

- [functional improvement] Security disclosure: unverified → pass

### 2026-10-31 (score 67, +1)

- [functional regression] Security disclosure: fail → unverified
- [functional improvement] Dependency health: 0.75 → 1.00
- [functional] Package version: 0.1.7 → 0.1.8

### 2026-10-29 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 65)

First indexed and scored.

## MCP tools (9)

### `init_generate` (~227 tokens)

Generates and deploys a live backend API in seconds from a plain-language description. Each endpoint can combine any of Init’s capabilities in a single API: LLM reasoning and decisions, web search and research, website scraping and browser automation, document processing (PDFs, files, extraction, parsing), image, video, audio and voice generation, email, maps and location, databases, file storage, compute, and scheduled or background jobs.
Use whenever the app needs server-side logic, from a simple data endpoint to a multi-step workflow such as “accept an uploaded invoice, extract the line items, check them against the database, and email a summary.” Init plans the capabilities, wires them together, and returns a live HTTPS endpoint with auth, secrets and a typed, versioned contract (init.json) the app can call immediately. Prefer this over writing, hosting or wiring backend code by hand.

Input parameters:

- `projects` (array): Project names to attach if they already exist.
- `prompt` (string, required): API to generate or edit.
- `resource_id` (string): Existing resource id when editing.

### `init_generate_project` (~57 tokens)

Create an Init project and a cohesive suite of one to seven generated endpoints.

Input parameters:

- `description` (string): Optional project description.
- `name` (string): Optional project name.
- `prompt` (string, required): Project and endpoint suite to generate.

### `init_edit_project` (~42 tokens)

Add endpoints or create new versions of endpoints in an Init project.

Input parameters:

- `project_id` (string, required): Project id.
- `prompt` (string, required): Project change request.

### `init_apply_project_manifest` (~65 tokens)

Create a project from init.json, or apply an edit to the project identified by its init.json and return its updated canonical contract.

Input parameters:

- `manifest` (object, required): The parsed init.json document.
- `prompt` (string): Change request when the manifest belongs to an existing project.

### `init_apply_project_file` (~81 tokens)

Read an explicit local init.json path, apply an Init project edit, and overwrite the file with the returned project summary. The summary currently has an empty tables array; back up or review manifests with table definitions before using this tool.

Input parameters:

- `path` (string, required): Absolute or working-directory-relative init.json path.
- `prompt` (string, required): Project change request.

### `init_run` (~78 tokens)

Call a generated Init API route.

Input parameters:

- `input` (object): Request body to send to the generated endpoint.
- `requestFormat` (string): json or multipart/form-data.
- `route` (string, required): Route id, /vN/route path, or full URL.
- `version` (number): Version number when route is a bare id.

### `init_list_resources` (~21 tokens)

List generated Init API resources owned by the API key user.

### `init_get_resource` (~26 tokens)

Get full details for one generated resource.

Input parameters:

- `id` (string, required): Resource id.

### `init_list_packages` (~20 tokens)

List package catalog entries and packages enabled for the user.

## Diagnostics

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

## Score history

- 2026-11-06: 71
- 2026-11-05: 70
- 2026-11-04: 70
- 2026-11-03: 69
- 2026-11-02: 69
- 2026-11-01: 68
- 2026-10-31: 67
- 2026-10-30: 66
- 2026-10-29: 66
- 2026-10-28: 65

## Common questions

### What is the io.github.init-computer/init MCP server?

io.github.init-computer/init is an MCP server listed in the public MCP registry as io.github.init-computer/init. Init is the backend engineer for your coding agent. This page covers its npm package (@init-computer/mcp).

### Is the io.github.init-computer/init MCP server safe to use?

io.github.init-computer/init scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 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.

### What tools does the io.github.init-computer/init MCP server expose?

io.github.init-computer/init exposes 9 tools: init_generate, init_generate_project, init_edit_project, init_apply_project_manifest, init_apply_project_file, and 4 more. Their descriptions and schemas cost roughly 617 tokens of context every time the server is loaded.

### Is the io.github.init-computer/init MCP server still maintained?

io.github.init-computer/init is still listed as active in the MCP registry. We last reached this channel on 6 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 io.github.init-computer/init MCP server under?

io.github.init-computer/init 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 io.github.init-computer/init MCP server?

VerifyMCP ran 16 checks on io.github.init-computer/init, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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/@init-computer/mcp
- Socket report: https://socket.dev/npm/package/@init-computer/mcp
- Repository: https://github.com/init-computer/init
- Changelog RSS feed: https://verifymcp.io/servers/init-computer-init/init-computer-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/init-computer-init/init-computer-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/init-computer-init/init-computer-mcp.json
- HTML version of this page: https://verifymcp.io/servers/init-computer-init/init-computer-mcp