Sealed

io.github.edwardyen724-gPublished by GitHub account edwardyen724-gv0.1.0Updated Oct 24, 2026

Per-call paid skills for AI agents, run server-side: inputs in, outputs back. The body never ships.

VerifiedSTDIODesktop onlyBusiness & CommerceAI & ML

Overview

AI-generated overview

A local stdio proxy that connects an AI assistant to the Sealed skill marketplace, letting it list paid skills and run them server-side per call.

What you can do
List the public skill catalog with names, descriptions, input schemas and per-call prices, and run a chosen skill server-side, returning only its output plus price and mode metadata. Skill bodies stay on Sealed's infrastructure; the client only carries inputs up and outputs back. Errors come back as fixed strings such as unauthorized, insufficient funds or unknown skill.
When to use it
Use it when you want an assistant to call ready-made, metered skills hosted remotely instead of running them locally, and you accept paying per call from a Sealed wallet balance.
Requirements
Runs locally as an npm package (sealed-mcp) via npx on Node 18 or later, with no other runtime dependencies. Requires the SEALED_API_URL environment variable (the client exits if unset) and network access to that API. SEALED_API_KEY is optional but most paid runs are rejected without it.
Before you install
Each run_skill call spends wallet balance at the listed per-call price, so costs accumulate with use. SEALED_API_KEY is a bearer token for a metered account and should be kept secret. Inputs are sent to the remote Sealed server, and skill execution happens there rather than on your machine.

Installation

In SourceWeft

  1. Open Sealed in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

sealed-mcp

Thin MCP stdio client for Sealed — the skill marketplace where your skill runs sealed.

This package is a pure proxy. It connects your MCP-capable agent to a remote Sealed server and exposes two tools:

ToolWhat it doesAnnotations
list_skillsLists the public skill catalog (name, description, input schema, price per call)readOnlyHint: true
run_skillRuns a skill server-side and returns only its output + price/mode meta. Each call spends wallet balance at the listed per-call price.readOnlyHint: false, destructiveHint: false

Skill bodies never reach this process. Skills execute on Sealed's infrastructure; this client only carries your inputs up and the output back. There is no local execution mode — SEALED_API_URL is required.

Zero runtime dependencies. Plain Node 18+ (uses the global fetch).

npm naming: this package targets the unscoped name sealed-mcp and carries mcpName: io.github.edwardyen724-g/sealed for the official MCP registry. If that npm name is unavailable at publish time, the fallbacks are the scoped names @sealed/mcp or @sealedrun/mcp — update package.json, registry drafts, and install snippets together.

Install / configure

Claude Code

sh
claude mcp add sealed --env SEALED_API_URL=https://sealed.run --env SEALED_API_KEY=sealed_sk_… -- npx -y sealed-mcp

Cursor / Windsurf

Add to ~/.cursor/mcp.json (Cursor) or ~/.codeium/windsurf/mcp_config.json (Windsurf):

json
{  "mcpServers": {    "sealed": {      "command": "npx",      "args": ["-y", "sealed-mcp"],      "env": {        "SEALED_API_URL": "https://sealed.run",        "SEALED_API_KEY": "sealed_sk_…"      }    }  }}

Generic stdio MCP client

Spawn the binary and speak newline-delimited JSON-RPC 2.0 over stdin/stdout (initialize, tools/list, tools/call):

sh
SEALED_API_URL=https://sealed.run SEALED_API_KEY=sealed_sk_… npx -y sealed-mcp

Environment variables

VariableRequiredPurpose
SEALED_API_URLYesBase URL of the Sealed API (e.g. https://sealed.run). The client exits with an error if unset.
SEALED_API_KEYNoYour Sealed API key (sealed_sk_…), sent as the bearer token. Without it, calls run unauthenticated and most servers will reject paid runs.

Errors you may see

Fixed, non-leaking error strings: unauthorized (bad/missing key), insufficient funds (top up your wallet), output blocked by leak gate, unknown skill: <id>, cannot reach the Sealed API. Server error bodies are never echoed.

Links

  • Website: https://sealed.run
  • Get an API key: sign up at your Sealed server's /signup endpoint (production emails you a single-use sign-in link that shows the key once)

Source: README.md at commit 8d1385a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts