Bragproof

← Reports

run402-mcp

Starts with no setup4.154.0npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Returns a result when called with no setup: 2 of 3 tools tried
Contacts while installing and starting: nothing

8tools listed
0hosts contacted
1file written
0.2 sto start
88dependencies

Its tool definitions changed since version 4.151.0. If you approved the earlier ones, read them again.

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y run402-mcp@4.154.0

Installing a package runs its code. Use a sandbox for anything you have not read.

Calling its tools

3 tools that take no input and look read-only were called once with nothing. 2 returned a result.

statusReturned a result under 0.1 s · 323 characters
whoamiNo usable answer tool reported an error: Error resolving principal identity: This route accepts a control-plane session bearer (Authorization: Bearer <token>), a SIWX wallet pro
docsReturned a result under 0.1 s · 14,804 characters

During the calls (not necessarily because of them) it first contacted: api.run402.com.

Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

up source, name, project_id, manifest, dir, tier, dry_run, yes, allow_prune, max_spend_usd, build_mode, allow_shell_build, idempotency_key, no_rehearse, display_name
Plan or run the canonical app-aware `run402 up` workflow from a local path or repo URL: any missing setup (wallet, tier, project, workspace link), then the deploy. Delegates to the SDK and returns the shared up result envelope with graph steps, resources, diagnostics, and next_actions. `deploy` only deploys.
deploy project_id, base, database, secrets, functions, site, assets, subdomains, routes, i18n, idempotency_key, allow_warnings, allow_warning_codes
Unified apply primitive. Accepts a structured ReleaseSpec — database (migrations + expose), value-free secrets.require/delete declarations, functions, site, site.public_paths, site.embedding (framing opt-in by catalog key, e.g. { frame_ancestors: ['localhost'] }; null = deny), site.sign_in_path (the app's own same-origin sign-in page for MCP authorization, e.g. '/join'; null = hosted page), site.noindex (true = X-Robots-Tag: noindex, nofollow, nosnippet on every response of the host; false or null = indexable), subdomains, and routes.replace web routes — with explicit replace vs patch semantics per resource. Migration entries use id for immutable versioned SQL or name for generated/idempotent content-tracked SQL; name compiles client-side to <name>_<sha256(sql)[0:16]>. Use site.public_paths for clean static URLs such as /events backed by release asset events.html; explicit mode does not expose /events.html unless separately declared, while mode: 'implicit' restores filename-derived reachability and can widen access. Route entries map exact/final-wildcard browser paths like /admin and /admin/* to Node 22 Fetch Request -> Response functions, or exact GET/HEAD method-aware static aliases such as /events to { type: 'static', file: 'events.html' }; acknowledge an intentionally read-only GET/HEAD wildcard function route with allow_warning_codes: ['WILDCARD_ROUTE_EXCLUDES_MUTATION_METHODS']. Direct /functions/v1/:name remains API-key protected. Secret values are set first with `r.secrets.set` (a `run` snippet) or `run402 secrets set`, never placed in deploy specs. All bytes ride through CAS (no inline-body cap). Returns release_id, URLs, warnings, and a structured progress-event log. Stops before upload/commit on confirmation-required warnings unless reviewed codes are passed with allow_warning_codes or allow_warnings is true.
status
The organization's state as this server's wallet sees it (r.status()): the wallet's local_label, server_label, and address, the tier and its lease, the allowance, the projects, and the active project. Never key material. Any other operation is a `run` snippet against `r`, the Node SDK client; `docs` is its reference.
whoami
The remote identity (r.orgs.whoami()): the control-plane principal this server's wallet resolves to, its active authenticator and linked identities, its org memberships, and the sign-in session grade (none for a wallet). For the local wallet use status. Any other operation is a `run` snippet against `r`, the Node SDK client; `docs` is its reference.
doctor project_id
Local health and configuration diagnostics (r.doctor()): { ok, blocking[], warnings[], checks[] }, the same report as `run402 doctor`. ok is false only on a blocking finding. Any other operation is a `run` snippet against `r`, the Node SDK client; `docs` is its reference.
docs topic, search
The SDK reference for `run` snippets, from the copy shipped in this package, so it matches the SDK the snippet runs against. No arguments: the run primer, the r namespace table, and the topics. topic: one namespace or section (assets, project.apply, rooms, local-state) or sdk for all of it; search: sections containing every word. Long answers are a window plus a ref for expand_result. Any other operation is a `run` snippet against `r`, the Node SDK client; `docs` is its reference.
run code, timeout_seconds
Run a TypeScript snippet against the SDK in a sandbox. `r` is the Node SDK client (@run402/sdk/node); call `docs` for its reference. The code is the body of an async function: await r chains, and the value of the last expression (or a return) is the result, e.g. `(await r.projects.list()).projects.map((p) => p.id)`. It is type-checked against the SDK before anything runs: a type error comes back with its line and TypeScript's message, and makes no call. No filesystem, process, fetch, timers, or imports; console is captured. Returns { status, value, value_ref, shown, total, logs, logs_ref, calls, duration_ms, wallet, error? }; a large value is stored whole and expand_result pages it. Operations that return or consume a one-time secret (grant keys, Handoff and Invite Keys, project credentials, wallet keys) refuse with SECRET_REQUIRES_CLI naming the exact CLI command to hand the person. Any other operation is a run snippet against r.
expand_result ref, offset, limit
Fetch more of a result a previous tool showed you only a window of. Tools on this surface truncate the VIEW, never the DATA: when one prints a ref together with shown and total, the full result is held behind that ref and this is how you read the rest of it. Pass the ref plus offset and limit to page through it. Refs live in this server process only — they expire after 30 minutes and only the most recent handful are kept, so re-run the producing tool rather than storing a ref across sessions. A result that carried a secret is never retained and never has a ref, so nothing here can hand one back.

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Files it wrote

Paths inside its sandbox, where its home folder is /tmp and its own folder cannot be written to.

Install facts

LicenseMIT
Needsnode >=22.13.0
Sourcegithub.com/kychee-com/run402
Install scriptsNone declared by it or anything installed with it.
Tarballsha512-Q6QSunjU1NbjoVHhCvEH90M5xOkh1f0jRH4tgc79ppTwdXQi3zOq1rZBA2s+6w06kSOgc2iSxVIlePw4/VlwYA==

Proven calls

Versions reported

VersionRunResultTools
4.154.02026-11-16Starts with no setup8
4.151.02026-11-12Starts with no setup8
4.150.02026-11-12Starts with no setup8

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/run402-mcp.svg)](https://bragproof.smaverk.com/r/run402-mcp)

New version out? Ask for a fresh report.