Skip to main content
Glama
Abhijay007

btcpayserver-mcp

by Abhijay007

Related Servers

Alternatives to btcpayserver-mcp

  • A
    license
    B
    quality
    F
    maintenance
    A server that enables interaction with Square's API via Goose, supporting queries for locations, customers, and more with context preservation and MCP-compliant responses.
    12
    4
    MIT

Related Servers

  • A
    license
    A
    quality
    D
    maintenance
    An MCP server that enables AI agents to manage merchant payment processing through the BTCPay Server Greenfield REST API. It supports tools for creating invoices, managing stores, tracking payments, and performing Lightning Network operations.
    21
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Model Context Protocol (MCP) server for Polar Lightning that enables AI assistants to manage Bitcoin Lightning Network test environments, including network creation, node management, Bitcoin operations, Lightning channel management, and Taproot Assets.
    10 npm
    7
    MIT
  • A
    license
    D
    quality
    Not graded
    maintenance
    A comprehensive MCP server that provides sophisticated tools for interacting with PocketBase databases. This server enables advanced database operations, schema management, and data manipulation through the Model Context Protocol (MCP).
    14
    643 npm
    70
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    A comprehensive Model Context Protocol (MCP) server providing 50+ tools for Algorand blockchain development, including account management, asset operations, smart contracts, API integration, swap functionality, and advanced transaction capabilities.
    18 npm
    MIT
  • F
    license
    Not graded
    quality
    D
    maintenance
    A server implementation of the Model Context Protocol (MCP) that provides REST API endpoints for managing and interacting with MCP resources.
    -

TDQS

B3.1/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: btcpay_request executes API operations, get_method_info provides parameter details for specific methods, and get_service_info discovers available services. There is no overlap in functionality, and an agent can easily distinguish between them based on their descriptions.

Naming Consistency5/5

The tool names follow a consistent verb_noun pattern throughout: btcpay_request, get_method_info, and get_service_info. All use snake_case with clear action-object naming, making them predictable and easy to understand.

Tool Count3/5

With only 3 tools, the server feels thin for a BTCPayServer integration, which typically involves multiple operations like creating invoices, managing stores, or handling payments. While the tools provide a foundation for exploration and execution, the count is borderline low for the apparent scope of interacting with a payment processing platform.

Completeness2/5

The tool surface is significantly incomplete for a BTCPayServer domain. It lacks core operations such as creating invoices, retrieving payment details, managing stores, or handling webhooks. The tools focus on discovery and generic execution, but without direct methods for common workflows, agents will likely encounter dead ends or inefficiencies.

Maintenance

ActivityInactive
ResponsivenessUnresponsive