MCP reference status
The local exact-three Stele profile is available in the v0.1.0 GitHub prerelease. The hosted OAuth resource is live at https://stele.monolythium.com/mcp and has passed authenticated tool discovery plus real Codex and Claude Code calls.
The Preview badge covers both bounded, non-economic surfaces. It does not imply general-availability economic execution.
- The hosted Stele MCP is a live keyless OAuth surface whose authenticated
tools/listresponse is authoritative for the runtime inventory. Its deployedstele_search_servicesand non-economicstele_create_booking_draftoperations 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; unknown listing IDs fail closed. Once a listing exists, its booking-approval draft returns a human-review URL and still fails closed unless its durable backend and release-readiness gate are healthy. The hosted surface cannot access keys, approve, contact a provider, sign, submit, broadcast, pay, reserve service, or lock funds. - The local
lyth_mcpStele profile is released as thev0.1.0GitHub prerelease and limited to exactlystele_connection_status,stele_search_services, andstele_agent_wallet_status. These are read/status tools only. They cannot access keys, sign, prepare or submit transactions, move value, create bookings, or execute payments.
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.