Froglet MCP server

Froglet

The rail-neutral evidence layer for agent transactions.

Whatever rail moves the money, Froglet produces a signed, hash-linked record of what was authorised, under which limits, and what the executing party attested to — verifiable offline by anyone, with no node and no account.

Verify a chain yourself in one command:

cargo run -p froglet-verify -- conformance/kernel_v1.json

Maintained by Armanas Povilionis-Muradian.

Table of Contents

• Overview
• Product Model
• Components
• Quick Start
• Bot Surfaces
• Verification
• Current Scope
• Documentation

Overview

The current product candidate starts with “Make this catalog usable by another agent.” Codex or Claude Code can prepare selected JSON, typed CSV, or SQLite data, or a small Wasm function; run a local example; ask for exact publication approval; and return a provider/service share link. Native setup preserves existing agent settings. Recipients use the same native integration without npm.

See the publishing workflow and the qualification gates. This is an uncommitted candidate: clean-machine agent tests, the real public relay journey, and first-time-user acceptance remain release gates. Supported targets are Apple Silicon macOS and Linux x86_64/arm64. The host must stay online.

Froglet gives one signed economic primitive for three product shapes:

The primary bot-facing integration surfaces are intentionally simple:

froglet-mcp for npx froglet-mcp, plus a dependency-minimal native bridge in froglet-node mcp

• One OpenClaw/NemoClaw plugin id: froglet (at integrations/openclaw/froglet/)
• One MCP server under integrations/mcp/froglet/, published as

the host (Claude Code, Codex, Cursor, Windsurf, etc.). The headline action is two-step marketplacepublish: the first call is a non-mutating plan, and the second must carry the exact approved consenthash. Both native and JavaScript adapters delegate to the same Rust publication module and provider-control contract.

• Both surfaces register a single agent-facing tool named froglet to

and the author CLI (froglet-node init / build / publish / whoami, prepare-service, invoke, doctor, and check-updates). status --open --json returns a short-lived read-only local status URL.

• The froglet-node binary is both the daemon (running as a provider)

Bots should be able to create small scriptable services directly, validate them locally, and publish them without starting from OCI images. OCI containers remain a supported packaging and deployment path.

Product Model

Shortened. The full README is on GitHub.