Skip to content
Agentmart
Submit a tool

Lightning Memory

Decentralized agent memory for the Lightning economy.

Connector by singularityjason · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)★ 9
Write a review

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/singularityjason-lightning-memory

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Decentralized agent memory for the Lightning economy. Nostr identity, L402 payments.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
12 read · 7 write · 0 delete · 3 not yet classified
Secrets
None asked for
Install scripts
Not scanned yet
Runs as
Python package

Tools by what they do 22

Read from the source code; the running server may list different tools.

Read 12 · Look things up without changing anything.

  • ln_agent_verify
  • ln_anomaly_check
  • ln_auth_lookup
  • ln_budget_check
  • ln_budget_status
  • ln_discover_gateways
  • ln_remote_query
  • ln_spending_summary
  • ln_vendor_reputation
  • ln_vendor_trust
  • memory_list
  • memory_query

Write 7 · Create, change, send or run things.

  • ln_agent_attest
  • ln_auth_session
  • ln_budget_set
  • ln_trust_attest
  • memory_edit
  • memory_store
  • memory_sync

Not yet classified 3 · We could not tell from the name and description.

  • ln_compliance_report
  • ln_preflight
  • memory_export

Files it touches

  • Any path the agent passes to its tools

Tools (22)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • ln_agent_attest

    Store an attestation about an agent's identity and compliance status. Used for Know Your Agent (KYA) — agents self-attesting, operators attesting their agents, or third-party KYA providers. Args: agent_pubkey: The agent's Nostr public key (64 hex chars). owner_id: Owner identifier (email, company name, etc.). jurisdiction: Legal jurisdiction (e.g., "US", "EU", "SG"). compliance_level: One of: unknown, self_declared, kyc_verified, regulated_entity. source: Verification source (e.g., "manual", "sumsub", "trulioo"). Returns: The stored attestation record.

  • ln_agent_verify

    Look up an agent's compliance attestation. Args: agent_pubkey: The agent's Nostr public key to verify. Returns: Attestation details or {status: "unknown"} if not found.

  • ln_anomaly_check

    Check if a proposed payment amount is normal for a vendor. Use this before making a payment to catch price anomalies. Compares the proposed amount against historical averages. Args: vendor: Vendor name or domain. amount_sats: Proposed payment amount in satoshis. Returns: Anomaly report: verdict (normal/high/first_time), context, and historical average.

  • ln_auth_lookup

    Check if an LNURL-auth session exists with a vendor. Args: vendor: Vendor name or domain to check. Returns: Session details if found, or {has_session: false}.

  • ln_auth_session

    Store or update an LNURL-auth session record. Record-keeping for externally-established LNURL-auth sessions. Args: vendor: Vendor name or domain. linking_key: The LNURL-auth linking key for this vendor. session_state: Session state: active, expired, or revoked. Returns: The stored session record.

  • ln_budget_check

    List budget rules and current spending status. Shows all active budget rules, or details for a specific vendor including how much has been spent today and this month. Args: vendor: Optional vendor to check. If omitted, lists all rules. Returns: Budget rules with current spending against limits.

  • ln_budget_set

    Set spending limits for a vendor. Creates budget rules that the pre-flight gate enforces. Any payment exceeding these limits will be rejected. Args: vendor: Vendor name or domain (e.g., "bitrefill.com"). max_sats_per_txn: Maximum sats allowed per single transaction. max_sats_per_day: Maximum total sats per day to this vendor. max_sats_per_month: Maximum total sats per month to this vendor. Returns: The created/updated budget rule.

  • ln_budget_status

    Check L402 gateway earnings and payment stats. Shows total sats earned from L402 gateway payments, broken down by operation. Reads from locally stored payment records (logged by the gateway). Returns: Earnings summary: total sats, payment count, breakdown by operation.

  • ln_compliance_report

    Generate a structured compliance report. Produces a comprehensive report covering agent identity, transactions, budget rules, vendor KYC status, anomaly flags, and trust attestations. Designed for regulatory compliance export. Args: since: Time period for temporal data. Relative: "1h", "24h", "7d", "30d". Current-state data (budget rules, KYC) is always included. format: Output format. Only "json" supported in v1. Returns: Compliance report as a structured dict.

  • ln_discover_gateways

    List known Lightning Memory gateways discovered via Nostr relays. Args: operation: Optional filter — only return gateways offering this operation (e.g., "memory_query", "ln_vendor_reputation"). Returns: List of known gateways with URL, operations, pricing, and last seen time.

  • ln_preflight

    Pre-flight check before making a payment. Runs budget limits, anomaly detection, and trust verification to produce an approve/reject/escalate decision. Use this before every payment to catch overspending, price anomalies, and unverified vendors. Args: vendor: Vendor name or domain. amount_sats: Proposed payment amount in satoshis. Returns: Decision: verdict (approve/reject/escalate), reasons, budget remaining, anomaly status, and trust score.

  • ln_remote_query

    Query a remote Lightning Memory gateway via L402 micropayment. Pays the gateway's Lightning invoice automatically via Phoenixd, then returns the query results. The payment is logged as a transaction memory. Args: gateway_url: URL of the remote gateway (e.g., "https://gw.example.com"). operation: Operation to perform. One of: memory_query, memory_list, ln_vendor_reputation, ln_spending_summary, ln_anomaly_check, ln_preflight, ln_vendor_trust, ln_budget_check, ln_compliance_report. params: JSON string of operation-specific parameters. Returns: Rem…

  • ln_spending_summary

    Get a spending summary for budget awareness. Shows total sats spent, broken down by vendor and protocol. Args: since: Time period. Relative: "1h", "24h", "7d", "30d". Or Unix timestamp. Returns: Spending breakdown with totals by vendor and protocol.

  • ln_trust_attest

    Publish a trust attestation for a vendor. Creates a NIP-85 Trusted Assertion and pushes it to Nostr relays. Other agents can pull these attestations to build community reputation. Args: vendor: Vendor name or domain to attest. score: Trust score 0.0-1.0. If omitted, auto-calculated from local reputation (success_rate * volume factor). basis: Reason for the score (default: "transaction_history"). Returns: Attestation details including score and relay push status.

  • ln_vendor_reputation

    Check a vendor's reputation based on transaction history. Use this before paying a vendor to see if they're reliable. Aggregates all past transactions to build a reputation score. Args: vendor: Vendor name or domain (e.g., "bitrefill.com", "openai"). Returns: Reputation report: total transactions, total sats spent, success rate, average payment size, and tags.

Show 7 more tools
  • ln_vendor_trust

    Get a vendor's full trust profile. Combines KYC verification status, local transaction reputation, and community trust attestations (from Nostr NIP-85) into a unified trust profile. Args: vendor: Vendor name or domain. Returns: Trust profile: KYC status, jurisdiction, community score, attestation count, and local reputation data.

  • memory_edit

    Edit an existing memory's content or metadata. Use this to correct wrong vendor information, update prices, or add context to an existing memory. Tracks edit history. Args: id: The memory ID to edit. content: New content to replace the existing content. If omitted, content is unchanged. metadata: JSON string of metadata fields to merge into existing metadata. Example: '{"vendor": "bitrefill.com", "note": "price updated"}' Returns: The updated memory record with old_content_preview for audit trail.

  • memory_export

    Export memories as Nostr NIP-78 events. Converts local memories into portable Nostr event format. Events are signed if secp256k1 is available. Useful for backup, sharing, or manual relay publishing. Args: limit: Maximum number of memories to export (default 100). Returns: List of NIP-78 events with memory content.

  • memory_list

    List memories, optionally filtered by type and time range. Use this to browse recent memories, check all transactions, or review memories of a specific type. Args: type: Filter by memory type (transaction, vendor, preference, error, decision, general). since: Time filter. Relative: "1h", "24h", "7d", "30d". Or Unix timestamp. limit: Maximum number of results (default 50, max 200). Returns: List of memories in reverse chronological order with stats.

  • memory_query

    Search memories by relevance. Returns the most relevant matches. Use this to recall past transactions, check vendor reputation, retrieve spending patterns, or find any previously stored information. Args: query: Natural language search query. Examples: - "bitrefill payment history" - "which APIs gave rate limit errors?" - "spending decisions this week" limit: Maximum number of results (default 10, max 100). type: Optional filter by memory type (transaction, vendor, preference, error, decision, general). Returns: List of matching memories ranke…

  • memory_store

    Store a memory for later retrieval. Use this to remember transactions, vendor experiences, decisions, spending patterns, API responses, or any information worth recalling. Args: content: The memory content to store. Be descriptive. Examples: - "Paid 500 sats to bitrefill.com for a $5 Amazon gift card via L402. Fast, reliable." - "OpenAI API returned 429 rate limit after 50 requests/min. Backoff to 30/min." - "User prefers to cap spending at 10,000 sats per session." type: Memory category. One of: - general: Default, uncategorized - tran…

  • memory_sync

    Sync memories with Nostr relays. Push local memories to relays and/or pull remote memories to local. When gateway_discovery is enabled, also syncs gateway announcements. Requires secp256k1 for push (signing). Pull works with any identity. Args: direction: Sync direction. One of: - "push": Upload local memories to relays - "pull": Download memories from relays - "both": Push then pull (default) Returns: Sync result with counts of pushed/pulled memories and any errors.

Signals

Stars
9
Forks
5
Open issues
2
Weekly downloads
19
Last commit
Mar 25, 2026 (7 months ago)
Last release
Mar 4, 2026 (7 months ago)
Last package publish
Mar 25, 2026 (7 months ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name
io.github.singularityjason/lightning-memory
Version
0.4.1
Auth
No auth
Packages
pypi lightning-memory
License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Cite this page

Lightning Memory MCP server. Agent Mart. https://agentmart.dev/connectors/singularityjason-lightning-memory (last updated 2026-10-24)