Pay per Call Nostr service for AI Agents MCP
Related Servers
Alternatives to Pay per Call Nostr service for AI Agents MCP
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenance23 tools for AI agents working with Nostr Open source. No API key. No account. NIP-46 remote signing Publish notes, reply, react, repost Encrypted DMs (NIP-04 + NIP-44) Fetch events, profiles, social graph235 npm1MIT
- AlicenseNot gradedqualityFmaintenanceProvides a trust layer for AI agents with identity, reputation, payments, and discovery via 92 API endpoints as MCP tools, leveraging Nostr-native infrastructure.MIT
- AlicenseNot gradedqualityAmaintenanceTrust-aware Nostr MCP server. 236 tools for identity, social, DMs, trust scoring, AI-to-AI dispatch, Lightning payments, privacy proofs, and encrypted vaults. NIP-46 bunker auth; keys never leave the signing device.93 npm1MIT
- AlicenseAqualityBmaintenanceAuthentication, pay-per-call metering, and signed receipts for AI agents and MCP tools using Bitcoin and Lightning Network.771 npm1MIT
- AlicenseAqualityDmaintenanceEnables AI agents to perform Bitcoin and Lightning Network payments using a non-custodial, zero-trust architecture. It provides 13 tools for wallet management, invoice creation, and payment processing while keeping node credentials local to the user's machine.139 npmMIT
- AlicenseAqualityCmaintenanceCryptographic accountability for AI agents. Ed25519-signed receipts for every MCP tool call. Constraints, chains, AI judgment, invoicing, and local dashboard included.243 npm1MIT
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.