Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldAlpaca Trading MCPShortlist candidatePayPal MCPMCP100 Recommended
Task fit
Best for
  • Alpaca users who need market data, portfolio context and agent-assisted trading workflows, preferably in paper-trading mode.
  • Querying invoices, orders, subscriptions, disputes, and shipment information
  • Sandbox prototyping of merchant workflows
  • Teams able to issue, scope, rotate, and monitor PayPal credentials
Not ideal for
  • Users who only need market data and do not want any possibility of order-placement authority.
  • Unattended production payment, refund, or invoice decisions
  • Users without PayPal developer credential management
  • Assistants that only need public PayPal documentation
Avoid when
  • Do not attach live-trading credentials unless real order placement is intended and a human-confirmation/approval process is in place.
  • Production financial actions would execute without explicit confirmation
  • Access tokens must be embedded in committed configuration
  • Merchant-account activity cannot be monitored and credentials cannot be revoked quickly
Provenance
Provenance details

First-party MCP

github:alpacahq · Publisher source ↗

First-party MCP

PayPal · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Not documented

Repo: Not documented

Package: Not documented

Popularity evidence
GitHub stars

1,032

GitHub stars · checked 2026-10-21

12

GitHub stars · checked 2026-09-24T18:01:37.627000Z

Package downloads / 30 days

42,247

package downloads / 30 days · checked 2026-10-21

2,304

package downloads / 30 days · checked 2026-09-24T18:01:10.803000Z

Client coverage
Client coverage detailsNot documented
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationAlpaca API key and secret.Local mode uses PAYPAL_ACCESS_TOKEN and PAYPAL_ENVIRONMENT. Remote mode supports PayPal login and consent or token authorization; PayPal publishes separate Sandbox and Production endpoints.
CostAlpaca account/data subscription, trading, market-data and model/provider costs can apply.The MCP package is publicly available. Normal PayPal account, transaction, product, API, and merchant-service fees or limits remain applicable.
PermissionsAuthority follows the Alpaca credentials and enabled toolsets. With live mode enabled, the server can place/cancel real orders and modify positions.Capabilities depend on enabled tools and the PayPal credential and can include reads and mutations across invoices, orders, subscriptions, disputes, shipments, transaction details, and related merchant resources.
Data handlingAccount/portfolio/order data and market queries can be exposed to the connected AI client/provider.The local MCP process sends merchant, customer, payment, and task data to PayPal APIs and returns results to the MCP client. The hosted option processes requests through PayPal's remote MCP service.
Limitations
Tradeoffs
  • Promoted after strict re-audit: canonical identity and MCP-native/publisher-backed implementation are sufficiently evidenced, with real workflow value, usable documentation, understandable permissions, plausible maintenance, and no unresolved security veto. Still not strong enough for Recommended.
  • The local npm server is portable and publisher documented, but executes package code on the user's machine.
  • The documented `--tools=all` setup is convenient but exposes a broad commerce surface; narrower tool selection is safer where supported.
  • Sandbox reduces financial impact but does not replace production authorization and operational controls.
Risk contextLive financial execution is high impact; default to paper trading and require deliberate human approval before live actions.Production access can create financial loss or customer-facing changes and can disclose transaction data. Start with Sandbox, keep credentials out of files and history, minimize tools, and require approval for every mutation.
Evidence date
Editorial review2026-10-212026-07-24
Candidate evidence2026-10-21T00:00:00Z2026-09-24T04:25:05.554391Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →