APIVerve vs PubFi MCP

A side-by-side look at the APIVerve and PubFi MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

APIVerve logoAPIVerveFinance & Fintech · Local subprocess (stdio)350+ production-ready APIs through one MCP server — weather, geocoding, validation, financial data.57GoodAuth: oauth 2.0PubFi MCP logoPubFi MCPFinance & Fintech · Local subprocess (stdio)Route crypto data needs through PubFi capability and gateway tools.44FairAuth: not declared

Verdict: choose APIVerve for finance & fintech work as a local process; choose PubFi 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?

APIVerve logoChoose APIVerve when

  • You need dedicated capabilities in the Finance & Fintech domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: OAuth 2.0.
  • You want tools like name, description, inputSchema.
Explore APIVerve

PubFi MCP logoChoose PubFi MCP when

  • You need dedicated capabilities in the Finance & Fintech domain.
  • You prefer a local stdio subprocess transport.
Explore PubFi MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAPIVerve logoAPIVervePubFi MCP logoPubFi MCP
CategoryFinance & FintechFinance & Fintech
Quality signal57/100 · Good44/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthOAuth 2.0Not declared
PricingFreemiumNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars30
Directory activity 1 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools3Not listed

Tools & capabilities

APIVerve tools 3

  • nameAPI identifier (e.g., `emailvalidator`)
  • descriptionHuman-readable description with token cost
  • inputSchemaJSON Schema defining required/optional parameters

PubFi 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.

APIVerve

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "apiverve": {
      "command": "npx",
      "args": [
        "-y",
        "@apiverve/mcp-server"
      ]
    }
  }
}

PubFi MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "pubfi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mint@latest"
      ]
    }
  }
}

Frequently asked questions

APIVerve is categorized under Finance & Fintech and uses a local stdio subprocess. PubFi MCP belongs to Finance & Fintech and uses a local stdio subprocess. Pick APIVerve for finance & fintech work and PubFi 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.

APIVerve is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. PubFi MCP has no declared pricing — check the project's own site. 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 apiverve and pubfi-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, APIVerve has a quality signal of 57/100 (Good) with 1 views, 0 installs and 3 GitHub stars. PubFi MCP has 44/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.