Skip to main content
Glama

Nostr MCP Server

by AustinKelsay

getReceivedZaps

Retrieve zap payments received by a Nostr user’s public key, with options to limit results, specify relays, and validate receipts according to NIP-57 standards.

Instructions

Get zaps received by a public key

Input Schema

NameRequiredDescriptionDefault
debugNoEnable verbose debug logging
limitNoMaximum number of zaps to fetch
pubkeyYesPublic key of the Nostr user (hex format or npub format)
relaysNoOptional list of relays to query
validateReceiptsNoWhether to validate zap receipts according to NIP-57

Input Schema (JSON Schema)

{ "$schema": "http://json-schema.org/draft-07/schema#", "additionalProperties": false, "properties": { "debug": { "default": false, "description": "Enable verbose debug logging", "type": "boolean" }, "limit": { "default": 10, "description": "Maximum number of zaps to fetch", "maximum": 100, "minimum": 1, "type": "number" }, "pubkey": { "description": "Public key of the Nostr user (hex format or npub format)", "type": "string" }, "relays": { "description": "Optional list of relays to query", "items": { "type": "string" }, "type": "array" }, "validateReceipts": { "default": true, "description": "Whether to validate zap receipts according to NIP-57", "type": "boolean" } }, "required": [ "pubkey" ], "type": "object" }

Other Tools from Nostr MCP Server

Related Tools

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AustinKelsay/nostr-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server