Inventpay Mcp

io.github.jams24Published by GitHub account jams24v1.0.1Updated Oct 24, 2026

Manage crypto payments, stores, digital products, and orders via InventPay

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

Local MCP server that lets an assistant manage InventPay crypto payments, stores, digital products and orders.

What you can do
  • Manage crypto payments through InventPay
  • Manage stores and digital products
  • Manage and review orders
  • No tool list is published, so the exact operations are not documented.
When to use it
Worth considering if you run an InventPay-based store and want an assistant to help with crypto payments, product listings or order handling from your desktop.
Requirements
Runs as a local stdio process installed from the npm package inventpay-mcp, so a Node.js runtime and desktop MCP client are needed. No environment variables, headers or authentication are declared in the manifest.
Before you install
It handles crypto payments and orders, so expect actions that create or change payment and order data. The manifest declares no authentication or credentials, but the README and tool list are unavailable, so how it authenticates to InventPay and what it sends to that third party cannot be verified before installing.

Installation

In SourceWeft

  1. Open Inventpay Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.