MCP Server (deprecated)

Created By
arbuthnot-etha year ago
A Model Context Protocol (MCP) server for PayPal API integration with improved error handling, comprehensive API coverage, and detailed documentation.
Overview

what is MCP Server?

MCP Server is a Model Context Protocol server designed for seamless integration with PayPal's APIs, providing improved error handling and comprehensive API coverage for payment processing, invoicing, and subscription management.

how to use MCP Server?

To use MCP Server, clone the repository, install dependencies, build the project, and configure your PayPal credentials in the settings file.

key features of MCP Server?

  • Comprehensive integration with PayPal APIs
  • Payment processing including order management and dispute handling
  • Business operations like invoicing and product management
  • User management features for identity verification and profile customization

use cases of MCP Server?

  1. Automating payment processing for e-commerce platforms.
  2. Managing subscriptions and recurring billing for services.
  3. Generating and sending professional invoices to clients.

FAQ from MCP Server?

  • What is the license for MCP Server?

MCP Server is licensed under the MIT License.

  • What are the prerequisites for installation?

You need Node.js 16.x or later and a PayPal Developer Account with API credentials.

  • How does MCP Server handle errors?

It implements comprehensive error handling with detailed validation errors and structured error responses.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
arbuthnot-eth
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago