Fuse MCP vs Gojiberry

Fuse MCP

The server documents 290 tools with read-only and destructive annotations, OAuth with PKCE and dynamic client registration, and published limits of 60 requests a minute. The single mcp:tools scope grants everything the user can do, sends happen at once with no undo, and no status page, changelog or security contact was found.

Gojiberry

A public OpenAPI file with 49 operations, a free masked lead search and a published limit of 100 requests a minute make the API easy to plan against. Keys have no scopes, writes can start LinkedIn outreach from a connected account, and LinkedIn's User Agreement bars the scraping and automated messaging the product depends on.

Fuse MCP

1. Keep the client's approval prompt on for every tool that is not read-only. Sends, CRM pushes and Slack posts run at once with no undo
2. Launch a campaign only on an explicit request. Creating one makes a draft, and update_campaign_status_tool starts real outreach
3. Call get_credits_balance and get_credit_prices first. Every call needs at least 100 credits, and searches cost 2 credits a result
4. Resolve filter values with lookup_filter_values or get_company_search_enums before search_people or search_companies
5. Start long work with deep_research_start, then poll deep_research_status. A tool call has 60 seconds, and runs take 5 to 20 minutes

Gojiberry

1. Send Authorization: Bearer <key> to https://mcp.gojiberry.ai. The value must start with the word Bearer or the connection fails
2. Create resources in the order list, source agent, campaign. A source agent with no campaign only finds leads
3. Adding a contact to a list enrols it in the linked campaign, which sends LinkedIn or email messages. Ask the user before list writes
4. Search with POST /v1/directory/leads/search for free, then reveal only the ids you need at 0.5 credit each, up to 100 a request
5. Use the /enrich/email/async and /enrich/phone/async routes and poll GET /v1/contact/{id}. The synchronous routes can take minutes