Is Quinns Conveyance free?

Yes, Quinns Conveyance is free to use.

How do I install Quinns Conveyance?

Quinns Conveyance supports both local and remote installation. For local use, install it via the provided package manager and add the configuration to your AI app. For remote access, add the server URL to your MCP configuration.

Is Quinns Conveyance safe to use?

Quinns Conveyance was flagged by MCP Marketplace's security scan, scoring 1/10 (critical risk). It has 6 high or critical findings to review. Review the security report on this page carefully before installing it.

What AI apps work with Quinns Conveyance?

Quinns Conveyance uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Quinns Conveyance MCP Server

by Jkomalleyjr

Developer ToolsUse Caution1.0MCP RegistryLocalRemote

Free

Server data from the Official MCP Registry

Paid ComfyUI knowledge tools. 5 tools $0.005 USDC/call on Base via x402; ping, list_topics free.

About

Paid ComfyUI knowledge tools. 5 tools $0.005 USDC/call on Base via x402; ping, list_topics free.

Remote endpoints: streamable-http: https://demo.quinnsconveyance.com/mcp

Security Report

1.0

Use Caution1.0Critical Risk

The server sends each buyer's EIP-3009 payment authorization, signature, and transaction hash to an undisclosed third-party endpoint (flow-kg4x.vercel.app) that is not mentioned in the README. It also hardcodes a Postgres password in source and logs payer IPs, user agents, and session IDs, and trust-proxy settings let those IPs and the rate limiter be spoofed via X-Forwarded-For. The core paid-tool logic is otherwise straightforward, but these issues drive the score well below 7.0. Supply chain analysis found 5 known vulnerabilities in dependencies (0 critical, 4 high severity).

5 files analyzed · 14 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

database

Check that this permission is expected for this type of plugin.

env_vars

Check that this permission is expected for this type of plugin.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

How to Install & Connect

Available as Local & Remote

This plugin can run on your machine or connect to a hosted endpoint. during install.

Documentation

View on GitHub

From the project's GitHub README.

Quinn's Conveyance — x402 Pay-Per-Call Reference Implementation

Live demo: https://demo.quinnsconveyance.com

This is the reference implementation behind Quinn's Conveyance — agent payment infrastructure that puts any API behind HTTP 402 so AI agents pay per call in USDC. No API keys, no accounts, no signup.

How it works

An AI agent calls a paid MCP tool.
The server answers with an x402 payment challenge: price ($0.005), wallet address, and chain (Base mainnet).
The agent signs an EIP-3009 authorization — signing costs zero gas; the agent never needs ETH.
A facilitator verifies the signature and settles the USDC transfer on-chain.
The server returns the answer.

Proof of real mainnet settlement: Basescan

Run it

npm install
cp .env.example .env   # set X402_PAY_TO to your Base wallet address
npm start              # serves :4021 — GET /health (free), POST /mcp (StreamableHTTP)

Structure

server.ts — Express + StreamableHTTP MCP server. Free tools (ping, list_topics) and paid tools (one per snippet-library entry, $0.005/call via @x402/mcp payment wrapper). Serves the landing page at / and machine-readable docs at /llms.txt.
snippet-library.json — the knowledge base. Each entry becomes a paid tool. Swap in your own content.
client-test.ts / client-remote.ts — test clients (local and remote).
.env.example — required environment variables.

Key implementation notes

TypeScript, not Python: the per-tool createPaymentWrapper pattern only exists in @x402/mcp (TypeScript). Python's x402 SDK has HTTP middleware only.
Validate args before the payment wrapper: unpaid calls with invalid args must still return the 402 challenge, not a validation error.
Per-connection MCP server instances: the @modelcontextprotocol/sdk singleton crashes on the second SSE/HTTP connection — create one server per connection.
Facilitators: https://x402.org/facilitator is testnet-only. For Base mainnet, use a mainnet-capable facilitator (this demo uses PayAI's — no API key required).

Services

Want this pattern on your API? Fixed-scope implementations:

Starter ($750) — one endpoint behind 402, wallet setup, verified settlement. Live in under a week.
Standard ($1,800) — up to 5 endpoints, MCP wrapper, registry listings.
Care plan ($150/mo) — monitoring, facilitator updates, settlement reconciliation.

Contact: john@quinnsconveyance.com

Reviews

No reviews yet

Be the first to review this server!

4.7

Local

MCP Marketplace

Free

by mcp-marketplace · Developer Tools

Search and install MCP servers from inside your AI client.