@rivet-dev/mcp

MCPcommunitylive
v2.3.17UnknownSEE LICENSE IN LICENSEUpdated 7d agonpmGitHub

Rivet Code Mode MCP server

Endpoint healthlive
checked 6 days ago · 52ms · auth required
100% of the last 1 check reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
387Downloads/wk
7d agoLast update
Reads these credentials
  • RIVET_CLOUD_TOKENAPI keyoptional

    Rivet Cloud API token. Required when targeting Rivet Cloud rather than a local engine.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorUnknown
LicenseSEE LICENSE IN LICENSE
Version2.3.17
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
Listed in Forge index+10/10
Publisher identity verified+0/20
Publisher: run `forge publish` from the package repo to claim ownership
Ed25519 publish signature+0/5
Included automatically when the publisher runs `forge publish`
Domain verification+0/5
Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
npm Trusted Publishing (Sigstore)+0/5
Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
npm maintainer match+0/5
Earned once your identity is verified above and that login is an npm maintainer of this package
CVE scan · clean+30/30
Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
Dependencies60 resolved · 1 with advisories
Tool surface3 tools · none privileged
Security scan✓ Cleanv2.3.17 · 6d agoHow well does this scan work?
EvalsNone
IndexedSep 17, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

3 tools · none privileged
Statically extracted from the published packagev2.3.17 · 6d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

searchSearch the Rivet Cloud, Engine, actor, and inspector Code Mode API. Returns the call signature and a runnable example for each matching operation, to be pasted into the execute tool. Call this before execute whenever the exact argument shape is not already known. An empty query lists everything.

Search the Rivet Cloud, Engine, actor, and inspector Code Mode API. Returns the call signature and a runnable example for each matching operation, to be pasted into the execute tool. Call this before execute whenever the exact argument shape is not already known. An empty query lists everything.

No input schema was published for this tool.

target_listList the Rivet organizations, projects, and namespaces this session can reach. Returns the next level that still needs a choice, narrowed by whichever levels are already given. Use it before naming a target on another tool when the names are unknown.

List the Rivet organizations, projects, and namespaces this session can reach. Returns the next level that still needs a choice, narrowed by whichever levels are already given. Use it before naming a target on another tool when the names are unknown.

No input schema was published for this tool.

executeNo description published

This tool published no description. Forge does not invent one.

2 of 3 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Rivet Code Mode MCP server

Keywords
mcp
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-17 — observed resolution, not a publisher declaration.

60 packages resolved · 13 direct · 1 carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

103 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+91 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies, optionalDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.