cypher_request_credential_channel

Active

declared in 3.4.2

Open a Secure Courier channel for credential delivery. This is the CREDENTIAL-DELIVERY flow — use it to hand over a service secret (API keys, tokens). To merely prove you control an npub (the usual answer to a ``proof_required`` error), use ``request_npub_proof`` instead. Note: dynamic/OAuth2 services (e.g. Schwab) need NO couriered secret — check ``service_status`` first. Sends a welcome DM with a credential template. The recipient must read the DM in their Nostr client, fill in the fields, and reply manually. **This is a human-in-the-loop flow.** After calling this tool, STOP and tell the user what to do. Wait for the user to confirm they have replied before calling ``receive_credentials``. Do NOT poll or retry — each ``receive_credentials`` call destructively drains the relay mailbox.

Parameters schema

{
  "type": "object",
  "properties": {
    "service": {
      "type": "string",
      "default": "",
      "description": "Required. The credential service name (e.g.,\nfrom get_operator_onboarding_status or get_patron_onboarding_status)."
    },
    "sender_npub": {
      "type": "string",
      "default": "",
      "description": "Required. The npub to send the template to."
    }
  },
  "additionalProperties": false
}

What this tool wraps· 0 endpoints

min confidence0.70 0.50

No endpoints wrapped at confidence ≥ 0.50.

Parent server

cypher-mcp

https://github.com/lonniev/cypher-mcp

2/7 registries

View full server →