H-Series MCP Server
XR-Utilities/h-series-mcp
Gateway MCP passthrough para registry, receipts e credenciais com suporte a pagamento x402
Ver no GitHubServidor Model Context Protocol que funciona como gateway stateless para os backends da família H-Series (H-Index, H-Seal, H-Grant, H-Relay). Mapeia chamadas de ferramentas MCP para endpoints HTTPS, gerencia pagamentos via x402 e valida argumentos sem manter estado, wallet ou segredos.
Instalação
npx convez-ai XR-Utilities/h-series-mcp1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Expor registros de capacidades (H-Index) como ferramentas MCP
- Integrar verificação de receipts e ancoragem de dados (H-Seal)
- Gerenciar fluxos de pagamento por chamada via x402
- Conectar agentes a vaults de credenciais (H-Grant) e entrega de mensagens (H-Relay)
Veredito

Ferramenta especializada e bem arquitetada para integrar protocolos descentralizados com MCP. Exige profundidade técnica em Web3/pagamentos x402 e adequa-se a projetos que precisam de gateway robusto com validação e suporte a múltiplos backends.
README
A tradução para o português deste README ainda está na fila.
@xr-utilities/h-series-mcp
Model Context Protocol (MCP) server that is the public front door to the H-Series backends. It exposes each backend's endpoints as MCP tools and forwards calls to the live HTTPS services:
- H-Index: capability registry (search, listings, register, renew, revoke, config)
- H-Seal: receipt anchoring and verification
- H-Grant: credential vaults and authorized capability release
- H-Relay: agent message delivery, inbox, heartbeat
What it is
A stateless passthrough. The server holds no database, no wallet, and no secrets. It maps an inbound MCP tool call to the owning backend, substitutes path parameters, forwards declared headers (including the caller-supplied x402 payment envelope), and relays the response. The backends are the authoritative validators and the source of truth; this server adds a defense-in-depth check on inbound arguments and does not enforce auth or payment itself.
Payment is per call where a tool is priced: the caller supplies an x402
payment envelope as payment_signature, which the dispatcher forwards as the
x-payment header. Tools marked free never carry a payment header. When a
paid tool is called without payment, the request is still forwarded so the
caller receives the real 402 challenge from the backend.
Run
Build first, then start a transport.
npm install
npm run build
# stdio transport (for example a desktop MCP client config)
npm run start:stdio
# HTTP transport (for a hosted deploy; PORT defaults to 8080)
npm run start:http
The published binary defaults to the stdio transport:
npx h-series-mcp --transport stdio
Transport can also be selected with the MCP_TRANSPORT environment variable
(stdio or http).
Startup schema-discipline check
On start the server fetches each backend's live config/manifest and checks
that the reported schema version is known and that each tool's path is still
advertised. Set MCP_SKIP_VALIDATE=1 to skip it (useful when networking is
flaky in development); set MCP_FAIL_ON_DRIFT=1 to exit non-zero on drift.
Development
npm run typecheck # tsc --noEmit
npm test # compile, then run the node:test unit tests
npm run dev # tsc --watch
Logging is structured JSON to stderr only, so the stdio JSON-RPC channel on
stdout stays clean. LOG_LEVEL (debug/info/warn/error) sets the threshold.
License
MIT