NowPayments connector concept
The prototype names configuration, discovery, estimate, invoice, payment-status, webhook-verification, and refund-draft operations. Those names are an implementation inventory, not a public API contract. A local tool appearing in tools/list does not establish provider correctness, custody safety, idempotent settlement, refund behavior, or release support.
The hosted Stele MCP remains keyless and has no third-party payment credentials. Stele economic writes, hosted signing, payment, booking, escrow, dispute, and review actions remain disabled.
Release evidence required
Section titled “Release evidence required”Before a connector can be documented as usable, a tagged release must establish provider sandbox isolation, secret storage and deletion, exact amount and asset binding, idempotency and timeout recovery, authenticated webhook processing, durable reconciliation, user approval, independent security review, and an end-to-end test. None of that evidence is published for this path today.
Safe scope today
Section titled “Safe scope today”Use the hosted Stele preview for public discovery and the live hosted MCP for search. Its deployed booking-approval draft tool requires a published service, and production currently has none. Private provider-listing drafts from the web Studio remain unpublished; MCP cannot list, read, update, delete, or publish an existing draft. Complete any purchase directly with a provider through a separately evaluated human checkout; do not route it through Stele or the legacy MCP.