Pay per Call Nostr service for AI Agents MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nostr_sign_eventC | Sign a Nostr event using a sovereign signing daemon. Price: 2 sats. |
| nostr_publish_eventC | Sign and publish a Nostr event to relays. Price: 3 sats. |
| nostr_post_noteA | Post a kind 1 text note to Nostr (sign + publish in one call). Price: 21 sats. |
| nostr_fetch_profileA | Fetch a Nostr profile (kind 0) by npub or hex pubkey. Price: 5 sat. |
| nostr_zapA | Zap a Nostr user via Lightning. Price: 50 sats (tool fee) + zap amount. Max 5000 sats. |
| nostr_get_notesB | Fetch recent kind 1 notes by author or hashtag. Price: 5 sats. |
| lightning_create_invoiceC | Create a Lightning invoice. Price: 5 sat. |
| create_action_receiptB | Create a signed action receipt (kind 1111) attesting an agent's action. Third-party attestation via Jorgenclaw's signing key. Price: 21 sats. |
| verify_receiptC | Verify an action receipt by event ID. Confirms it was signed by Jorgenclaw's key. Price: 5 sat. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools have distinct purposes, such as nostr_fetch_profile for retrieving profiles and nostr_zap for sending payments. However, nostr_post_note and nostr_publish_event have some overlap in publishing Nostr events, which could cause minor confusion, though their descriptions differentiate them slightly (post_note is specifically for kind 1 notes, while publish_event is general).
Tool names follow a consistent snake_case pattern with clear verb_noun structures, such as create_action_receipt and nostr_fetch_profile. All tools adhere to this convention, making them predictable and easy to parse, with no mixing of styles or deviations.
With 9 tools, the count is well-scoped for a server focused on Nostr and Lightning operations. Each tool serves a specific function in this domain, such as fetching data, posting content, or handling payments, without feeling excessive or insufficient for the intended purpose.
The tool set covers key Nostr and Lightning workflows, including profile fetching, note posting, zapping, and receipt handling. A minor gap is the lack of tools for managing relays or handling other Nostr event kinds beyond basics, but agents can work around this with the provided tools for core operations.