Side-by-Side Model Context Protocol Comparison
Referral Codes vs Spawnpay
In-depth architectural comparison of the Referral Codes and Spawnpay MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Referral Codes
Finance & Fintech · Remote HTTP/SSE
Quality: 30/100 (Emerging) | Auth: No auth required
Spawnpay
Finance & Fintech · Local stdio
Quality: 27/100 (Emerging) | Auth: No auth required
Verdict Summary: Choose Referral Codes if you need specialized Finance & Fintech tools running via a hosted cloud SSE transport. Choose Spawnpay if your workspace requires Finance & Fintech integration with local subprocess execution. Both servers can be configured concurrently in your client's
mcpServers manifest.Which MCP Server Should You Choose?
R
Choose Referral Codes when:
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer remote streaming HTTP/SSE transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
S
Choose Spawnpay when:
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
Feature & Specification Comparison
Tools & Capabilities Breakdown
Referral Codes Tools (0)
No explicit tool names declared in metadata yet. Check project README on main listing page.
Spawnpay Tools (0)
No explicit tool names declared in metadata yet. Check project README on main listing page.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Referral Codes Configuration
Spawnpay Configuration