Installing Clean Vector, start to finish

This guide follows one release, Clean Vector 0.1.0, along the path its check record names. Everything here comes from the public listing; the exact commands open on the Vibe page once it is in your library.

The public check record for this release: “Checked on 2026-11-12 on Windows_NT 10.0.26300 x64: installed from the release file into an empty npm project and run through its module, command-line and MCP entry points (Node.js, MCP over stdio). Not tested with any coding agent.”

1. Check the listing

On the Clean Vector page you can see the demo, the outcome, what is included, the requirements and the license before you add anything.

• Runtime: Node.js 20 or later
• Works on: windows, macos, linux
• External costs: none
• License: UNLICENSED, pending the owner’s decision

2. Sign in

Vibefield signs you in with a link sent to your email address. There is no password. Open the link, then press the button on the page it opens. That is the only approval the account needs.

3. Add it to your library

It is free: press Add to library on its page. No credits are spent.

Prices are test pricing, and no real payment is taken.

Once it is in your library, the technical side of its page opens: the package file, the install steps and commands, the settings, the entry points and the verification records.

4. Install it from the download

1. Open Your library and press Download. You get the release file; its sha256 checksum is shown on the Vibe page.
2. Open a project folder with Node.js 20 or later and npm.
3. Follow the install steps on the Vibe page. They install the release file into the project with npm.
4. Run the check under “Check it works” on the same page to confirm the install.

5. Or fetch it through the Vibefield MCP connection

1. Open Account and create an access token with the read and deliver scopes. Add acquire only if your MCP client should spend credits; it can then buy only at the exact quoted price.
2. Copy the token when it appears. It is shown once.
3. Add the connection to your MCP client: endpoint https://services-production-9285e3e4.up.railway.app/mcp, transport Streamable HTTP, header Authorization: Bearer <your token>.
4. For a Vibe you own, get_vibe returns its technical side and get_delivery returns a short-lived download link for the same release file. Install it as in step 4.

This route hands over the same file and the same instructions. The release check installed from the file directly.

6. What was tested for this release

• Checked: 2026-11-12, status verified.
• Installation path tested: from the release file into an empty npm project, then its module, command-line and MCP entry points.
• Coding agents tested: none. The check did not use a coding agent, so this guide names none.