MCP surface status
Stele has separate hosted and local MCP surfaces. Runtime inventory and authority do not transfer between them.
The Preview badge covers Stele’s live, deliberately non-economic hosted MCP and the public local exact-three prerelease. It does not imply booking, payment, custody, or transaction execution.
Hosted Stele MCP
Section titled “Hosted Stele MCP”The hosted surface is keyless and OAuth protected. Its deployed stele_search_services tool reads the public catalog, while stele_create_booking_draft records only a short-lived, nonbinding, non-economic booking-approval draft and returns a human-review URL. That operation does not contact a provider, approve a booking, reserve service, accept a quote, sign, submit, broadcast, pay, or lock funds.
The live resource URL is https://stele.monolythium.com/mcp. Its OAuth discovery, wallet-bound consent, authenticated tool discovery, and real Codex and Claude Code search calls have been exercised on the public deployment. The authenticated tools/list response is authoritative for the hosted inventory; this page does not promise a fixed tool count. 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.
Production returned 0 published services during release validation, so the deployed booking-approval draft tool cannot currently produce a successful booking-approval draft; unknown listing IDs fail closed. Private provider-listing drafts from the web Studio are unpublished and do not satisfy that prerequisite. The booking tool also fails closed unless its durable backend and release-readiness gate are healthy. OAuth authorizes access to this bounded application surface; it does not grant wallet custody or transaction authority.
Use the tested commands in Connect an agent. The hosted surface requires a compatible wallet-auth v1 browser wallet for consent.
Local lyth_mcp Stele profile
Section titled “Local lyth_mcp Stele profile”The isolated local profile is available in the v0.1.0 GitHub prerelease with exactly three tools: stele_connection_status, stele_search_services, and stele_agent_wallet_status. The release includes a tarball, checksums, an SPDX SBOM, and cosign bundles. It is not an npm-registry package or a general-availability economic MCP.
All three local tools are read-only. The local profile cannot access or create keys, sign, prepare or submit a transaction, broadcast, book, pay, escrow, dispute, review, or inspect another wallet store. stele_agent_wallet_status reports that the dedicated-wallet boundary is unavailable; it does not open one.
The broad legacy MCP registration count is not a public product or compatibility contract. Do not install or invoke prototype economic tools from old documentation.