PubFi MCP vs Clawpay MCP
A side-by-side look at the PubFi MCP and Clawpay MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose PubFi MCP for finance & fintech work as a local process; choose Clawpay MCP for finance & fintech as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose PubFi MCP when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
Choose Clawpay MCP when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
AGENT_PRIVATE_KEY, AGENT_WALLET_ADDRESS.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 44/100 · Fair | 42/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | other |
| Pricing | Not declared | Free |
| Required env vars | None listed | AGENT_PRIVATE_KEYAGENT_WALLET_ADDRESS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 8 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View PubFi MCP | View Clawpay MCP |
Tools & capabilities
PubFi MCP tools
No tool names declared yet. Check the project README from the listing page.
Clawpay MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
PubFi MCP
{
"mcpServers": {
"pubfi-mcp": {
"command": "npx",
"args": [
"-y",
"mint@latest"
]
}
}
}
Clawpay MCP
{
"mcpServers": {
"up2itnow0822-clawpay-mcp": {
"command": "npx",
"args": [
"-y",
"agentpay-mcp"
],
"env": {
"AGENT_PRIVATE_KEY": "YOUR_AGENT_PRIVATE_KEY_HERE",
"AGENT_WALLET_ADDRESS": "YOUR_AGENT_WALLET_ADDRESS_HERE"
}
}
}
}
Frequently asked questions
PubFi MCP is categorized under Finance & Fintech and uses a local stdio subprocess. Clawpay MCP belongs to Finance & Fintech and uses a local stdio subprocess. Pick PubFi MCP for finance & fintech work and Clawpay MCP for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
PubFi MCP has no declared pricing — check the project's own site. Clawpay MCP is listed as free. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add pubfi-mcp and up2itnow0822-clawpay-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, PubFi MCP has a quality signal of 44/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Clawpay MCP has 42/100 (Fair) with 5 views, 0 installs and 8 GitHub stars.