Tooling — local lyth_mcp Stele profile
The isolated local lyth_mcp Stele profile is published as a v0.1.0 GitHub prerelease. The release provides the lyth-mcp-0.1.0.tgz archive, SHA256SUMS, an SPDX SBOM, and cosign bundles. It is a prerelease artifact, not an npm-registry package or a general-availability economic MCP.
With Node.js 22 or newer, download, verify, then install: fetch the tarball, SHA256SUMS, SPDX SBOM, and tarball cosign bundle; require both checksum and cosign verification to succeed; then run npm install --global --ignore-scripts ./lyth-mcp-0.1.0.tgz against the verified local file. Do not pass the remote release URL directly to npm install. The exact commands and pinned signing identity are in Connect an agent.
Then configure Codex with codex mcp add stele-local -- lyth-stele-mcp, or configure Claude Desktop to run the lyth-stele-mcp command under the stele-local name. This avoids colliding with the live hosted profile named stele. See Connect an agent for the bounded client examples.
The released profile contains exactly three read/status tools:
| Tool | Release boundary |
|---|---|
stele_connection_status |
Re-read and compare SDK, trusted network identity, and Stele metadata |
stele_search_services |
Read public catalog data only after a fresh identity check |
stele_agent_wallet_status |
Report that the dedicated-agent wallet boundary is unavailable without opening a key |
All three are read-only and declare economic execution unavailable. The profile does not import, inspect, create, reveal, unlock, or hold keys; it cannot sign, prepare, submit, or broadcast transactions; and it does not inspect browser, desktop, or legacy MCP wallet stores.
The broad legacy MCP source tree is not the local Stele authority boundary. Its prototype registrations are not a supported tool catalog and must not be used with funds or credentials.
The live hosted surface at https://stele.monolythium.com/mcp has its own keyless OAuth contract. Its authenticated tools/list response is authoritative for the runtime inventory. The deployed stele_search_services and stele_create_booking_draft operations provide public-catalog search and a fail-closed booking-approval draft. Production currently has 0 published services, so the booking tool cannot return a successful booking-approval draft. Any later booking-approval draft remains non-economic and fails closed unless its durable backend and release-readiness gate are healthy. Only when the authenticated tools/list response includes the exact stele_create_provider_listing_draft name may a client call that tool. Each successful create operation produces exactly one new private, wallet-owned, unpublished provider-listing draft. An idempotent replay returns that same draft without creating another. If the name is absent, the operation is unavailable. It is create-only: it cannot list, read, update, delete, or publish an existing draft, and it cannot sign, submit, or settle a transaction. Hosted OAuth never expands this local profile into wallet, signing, or transaction authority. Use Connect an agent for tested hosted and local setup.
The v0.1.0 release does not change the economic boundary: it has no wallet, key, signing, transaction-preparation, submission, broadcast, booking, or payment authority.