io.github.init-computer/init
NPM · @INIT-COMPUTER/MCP
Init is the backend engineer for your coding agent.
Available components
Last scanned (14 hours ago)
Scores higher than 41% of npm servers
Category Developer Tools
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 1 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 799 tokens (~88/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 +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.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 1 Nov 26 +1
- Security disclosure: unverified → pass ▲ functional
- 31 Oct 26 +1
- Security disclosure: fail → unverified ▼ functional
- Dependency health: 0.75 → 1.00 ▲ functional
- Package version: 0.1.7 → 0.1.8 functional
- 29 Oct 26 +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.
- 28 Oct 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Analysed npm/@init-computer/mcp@0.1.8
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 1 package
| Packages resolved | 1 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
init_apply_project_file ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute or working-directory-relative init.json path. |
| prompt | string | yes | Project change request. |
No output schema declared.
No examples provided.
init_apply_project_manifest ~65
Create a project from init.json, or apply an edit to the project identified by its init.json and return its updated canonical contract.
| Name | Type | Req | Description |
|---|---|---|---|
| manifest | object | yes | The parsed init.json document. |
| prompt | string | – | Change request when the manifest belongs to an existing project. |
No output schema declared.
No examples provided.
init_edit_project ~42
Add endpoints or create new versions of endpoints in an Init project.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | Project id. |
| prompt | string | yes | Project change request. |
No output schema declared.
No examples provided.
init_generate ~227
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.
| Name | Type | Req | Description |
|---|---|---|---|
| projects | array | – | Project names to attach if they already exist. |
| prompt | string | yes | API to generate or edit. |
| resource_id | string | – | Existing resource id when editing. |
No output schema declared.
No examples provided.
init_generate_project ~57
Create an Init project and a cohesive suite of one to seven generated endpoints.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional project description. |
| name | string | – | Optional project name. |
| prompt | string | yes | Project and endpoint suite to generate. |
No output schema declared.
No examples provided.
init_get_resource ~26
Get full details for one generated resource.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Resource id. |
No output schema declared.
No examples provided.
init_list_packages ~20
List package catalog entries and packages enabled for the user.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
init_list_resources ~21
List generated Init API resources owned by the API key user.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
init_run ~78
Call a generated Init API route.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | – | Request body to send to the generated endpoint. |
| requestFormat | string | – | json or multipart/form-data. |
| route | string | yes | Route id, /vN/route path, or full URL. |
| version | number | – | Version number when route is a bare id. |
No output schema declared.
No examples provided.
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.
npm · @init-computer/mcp
claude mcp add init-computer-init -- npx -y @init-computer/mcp
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.