nwc-mcp

nwc_pay_keysend

Send sats directly to a node pubkey via keysend, enabling spontaneous payments without an invoice.

Instructions

Send sats directly to a node pubkey via keysend (spontaneous payment, no invoice). Default-off — must be opt-in via NWC_KEYSEND_ENABLED=true. Power-user feature: no payment hash receipt, weaker safety surface than bolt11. Use bolt11 invoices when available. Runs the full safety pipeline (read-only gate, allowlist on pubkey, budget cap, optional two-step confirmation).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pubkey": "<pubkey>",
      "amount_sats": "<amount_sats>"
    },
    "name": "nwc_pay_keysend"
  }
}

Input Schema

Name	Required	Description
`pubkey`	Yes	Destination node's public key (33 bytes hex).
`amount_sats`	Yes	Amount to send in satoshis.
`tlv_records`	No	Optional TLV records (e.g., podcasting 2.0 metadata, LNURL-pay sender data). Empty/omitted is fine for most uses.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It discloses no payment hash receipt, weaker safety surface, and the full safety pipeline (read-only gate, allowlist, budget cap, optional two-step confirmation). This is rich behavioral context beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the core purpose, then caveats and safety details. Every sentence adds unique value without waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a payment tool with no annotations and no output schema, the description covers the essential aspects: default-off toggle, safety pipeline, invoice comparison, and what to expect (no payment hash). It is sufficiently complete for an agent to decide and invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the description need not elaborate on parameters. It does add minor value by mentioning TLV records usage examples (e.g., podcasting 2.0 metadata), but the schema already documents all fields well. This meets the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Send sats directly to a node pubkey via keysend (spontaneous payment, no invoice),' which specifies the exact action, resource, and method. It distinguishes from siblings like nwc_pay_invoice and nwc_pay_lightning_address by emphasizing pubkey-based, no-invoice payments.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly provides usage context: 'Default-off — must be opt-in via NWC_KEYSEND_ENABLED=true' and 'Use bolt11 invoices when available.' This tells when to use the tool and when to prefer alternatives, plus notes it's a power-user feature.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server