Canopy logo

Canopy

Creates crypto deposit intents, lists payable chains and tokens, and reads settlement status through a remote MCP server.

Install Canopy

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://www.canopypay.io/api/mcp

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Hosted endpointLive · 3d agoLive Remote EndpointOur automated health check connected to this remote MCP endpoint successfully.Last checked 3d ago · Nov 14, 2026, 05:45 UTC

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint
https://www.canopypay.io/api/mcp

Overview

Canopy MCP server lets agents create crypto deposit intents, inspect which chains and tokens can receive payments, and read settlement status. It exposes these operations through a remote Model Context Protocol endpoint rather than a locally described process. Use it when an agent needs to initiate or monitor crypto deposit flows supported by Canopy.

Use cases

  • Create crypto deposit intents for agent-led payment flows
  • List payable chains before selecting a deposit route
  • List payable tokens for a crypto payment
  • Read settlement status after initiating a deposit

Key features

  • Create crypto deposit intents
  • List payable chains
  • List payable tokens
  • Read settlement status
  • Remote MCP access

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

9/9 checks healthy over the last 46d

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

MaintenanceActively maintainedStatus declared by the project or listing owner.
Availability100%Our rolling endpoint + install checks that succeeded.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Canopy works

What Canopy MCP server does

Canopy MCP server exposes a focused set of crypto payment operations to MCP-compatible agents. It can create deposit intents, return the chains and tokens that are payable, and provide settlement status for deposits. These capabilities suit workflows where an agent needs to begin a crypto deposit process, determine available payment options, or check whether a settlement has progressed.

The available description does not identify additional finance, wallet, exchange, or blockchain operations. It also does not specify whether the server can send funds, estimate fees, generate wallet addresses directly, or handle refunds. Those capabilities should not be assumed from the documented deposit-intent and status functions.

How it works

The Canopy MCP server is described as remote. An MCP client connects to the hosted service and makes the supported operations available to an agent. The documented interaction pattern has three parts: create a deposit intent, list payable chains and tokens, and read settlement status.

A typical agent flow could first request the available chains and tokens, then create a deposit intent using an appropriate payment option, and later query settlement status. The source description does not define the request fields, response schema, status values, authentication method, transport URL, or error behavior, so implementation details must be confirmed from Canopy’s service documentation.

Tools and capabilities

The documented capabilities are:

  • Create crypto deposit intents.
  • List chains that accept payment.
  • List tokens that can be used for payment.
  • Read the settlement status of a deposit.

These operations give an agent visibility into supported payment choices and the state of a deposit flow. The description does not provide formal tool names, parameter definitions, or examples, so this listing cannot establish the exact names an MCP client will display.

Limitations and notes

As a result, there is no grounded information here about installation commands, authentication credentials, environment variables, rate limits, supported MCP clients, pricing, network coverage, or license terms. The source identifies the service as remote, but it does not state whether access is public, requires an account, or depends on a Canopy-specific API key.

Before integrating the Canopy MCP server, verify the connection instructions and authentication requirements at the source URL. Also confirm which chains and tokens are currently payable at runtime rather than treating the listing as a fixed asset or network inventory.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Canopy

Canopy is an MCP server that connects agents to Canopy’s crypto deposit service. Its documented tools create crypto deposit intents, list chains and tokens that can accept payment, and read settlement status.

Canopy is described as a remote MCP server, so you should obtain its connection and authentication details from the source documentation rather than installing a local package based on this listing.

The Canopy MCP server can create crypto deposit intents, list payable chains and tokens, and read settlement status. The available description does not document broader wallet, transfer, fee-estimation, refund, or exchange functions.

It identifies Canopy as a remote MCP server but names no supported clients and provides no client-specific configuration.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewCanopy AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/canopy?style=directory)](https://allmcps.com/mcp/canopy)
HTML Embed
<a href="https://allmcps.com/mcp/canopy"><img src="https://allmcps.com/api/badge/canopy?style=directory" alt="Canopy on AllMCPs" /></a>