Orchestrator payment repo. It assembles payment rails, business flows, and support services into a single Nuxt-based workspace.
This is not an MCP server. The repository is a Nuxt-based payment orchestration framework with multiple microservices (BTCPay, Masspay, RoboSats, etc.) built on Nitro/Nuxt. Only one tool ('server-info') is claimed, but no MCP tool registration, schema definitions, or protocol implementation are visible in the provided source. The .vscode/mcp.json references an external Nuxt MCP server, not this repo's own implementation. No tool definitions, input schemas, parameter descriptions, or output schemas are present in the codebase excerpt.
Retrieves server information from BTCPay
No MCP tool registration visible. Tool 'server-info' is claimed but no explicit MCP tool definition (name, description, inputSchema, handler) is present in source code.
No input schema defined for server-info. Cannot verify parameter types, constraints, or descriptions.
Tool description 'Retrieves server information from BTCPay' is 47 characters, minimal context. Does not explain WHEN to use it, WHAT fields are returned, or any prerequisites. Baseline for A+ tools: 194 chars average.
No output schema documented. LLM cannot know what fields to expect from server-info response, preventing downstream tool chaining and field extraction.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 25 | 2026-07-28+ | v2 |
Repository is a Nuxt/Nitro monorepo, not an MCP server. No MCP protocol implementation (initialize, tools/list, tools/call, resources, prompts) is evident. This appears to be a web framework, not an agent tool server.