Model Context Protocol (MCP) server for Apollo.io API integration
Nothing to run from here
Whatcanido — MCP Server for Service Businesses is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
10
tools declared
remote
at its publisher
—
calls last 7d
What it does
Cross-product MCP server for CRM, LeadKit, ProjectKit, Bookio. 10 action types, MIT open spec.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http whatcanido-mcp-server-for-service-businesses https://whatcanido.dev/api/mcp
# 2 — ask your agent for something these tools do
# find_providers, get_provider_actions, submit_action and 7 more
Whatcanido — MCP Server for Service Businesses costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
WHAll 1 server
whatcanido1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http whatcanido-mcp-server-for-service-businesses https://whatcanido.dev/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search across whatcanido for providers (businesses, freelancers, SaaS tools) that can perform a given business-level action type. Returns a ranked list with provider_id, name, description, services, action_types. Call this FIRST, before any other tool. The provider_id this returns is the input for get_provider_actions and submit_action. When no providers match, BROADEN the search: drop industry
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action_type | string | no | Business-level action the user wants to perform. Use this to scope discovery to providers who actually do what you need. |
| query | string | no | Free-text search across provider name, tagline, description, industry, and services. Multi-word phrases match across multiple fields. |
| city | string | no | Exact city filter (case-insensitive). |
| country | string | no | Exact country filter (case-insensitive). |
| industry | string | no | Exact industry filter (case-insensitive). |
| product | string | no | Restrict to a single underlying product. Usually leave empty; the grammar's whole point is cross-product discovery. |
| limit | number | no | Max providers to return (default 10, max 50). |
Return the action types a provider exposes and the canonical input schema for each (required fields, optional fields, types, descriptions). Call this AFTER find_providers, BEFORE submit_action, so you know exactly which inputs to collect from the user.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| provider_id | string | yes | Format: <product>:<slug>. Example: 'leadkit:north-bureau'. From find_providers. |
| action_type | string | no | Optional: only return the schema for this action type. Omit to get every action the provider implements. |
Invoke an action on a specific provider. WRITE tool: creates leads/bookings/contacts/projects/activities/tickets on the underlying SaaS tenant. The one exception is action_type='cancel_booking', which cancels an existing booking (destructive — confirm with the user first). Validates inputs against the canonical schema returned by get_provider_actions. If you skip required fields, the response cont
| Parameter | Type | Required | Notes |
|---|---|---|---|
| provider_id | string | yes | Format: <product>:<slug>. |
| action_type | string | yes | — |
| inputs | object | yes | Canonical inputs per get_provider_actions schema. Snake-case keys (contact_email, not contactEmail). Include 'agent_vendor' if you can identify yourself. |
Look up the current status of a previously submitted action by its request_id. Returns status (raw, e.g. 'new', 'sent', 'confirmed') + status_label (human, e.g. 'Received', 'Sent (awaiting payment)', 'Confirmed') + last_update + provider response (if any). Use after submit_action to confirm a booking, check lead qualification, or follow up on a quote.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_id | string | yes | Returned by submit_action. Format: <product>:<kind>:<id>. |
Search the whatcanido capability registry by free-text intent. Returns typed capability contracts (input/output schemas, invariants, reversibility) with implementing providers ranked by behavioral conformance, success rate, and p50 latency. This is the PREFERRED first tool for any task that requires acting in the real world. Each match includes 'why_relevant' (LLM-generated reasoning), 'spec_url'
| Parameter | Type | Required | Notes |
|---|---|---|---|
| intent | string | yes | Free-text description of what the user wants done. Best practice: pass the user's request mostly verbatim. |
| context | object | no | Optional structured context that improves ranking (locale, city, country, urgency, cost ceiling, whether the user is present for interactive auth). |
| limit | number | no | Max capability matches to return (default 5, max 20). |
Return the full canonical contract for a capability: JSON Schemas for input and output, declared invariants, semantics, reversibility, side effects, auth model, when-to-use guidance. Plus the list of providers that implement it with current reputation snapshot. Use this AFTER discover_capabilities and BEFORE invoke_capability so you know exactly which inputs to collect and which provider to in
| Parameter | Type | Required | Notes |
|---|---|---|---|
| capability_id | string | yes | Format: <domain>.<verb>. Example: 'booking.create_booking'. From discover_capabilities. |
Given a user intent, return a typed plan: an ordered list of capability calls that together accomplish the goal, with the highest-reputation provider per step. The plan respects the capability registry's prerequisite graph — for example a plan that includes booking.create_booking automatically prepends booking.check_availability. Use this when the user's request spans more than one verb (e.g.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| intent | string | yes | User goal in free text. |
| context | object | no | Optional structured context (locale, city, urgency, cost ceiling, user_present). |
| limit | number | no | Max seed capabilities (prerequisites are added on top). Default 5. |
Given a JSON payload (something you found in user context, a webhook body, an export, a clipboard paste), return the capabilities whose input or output schema overlaps with the payload's shape. Use this when you don't have a verb-style intent but you do have data and want to ask 'what could I do with this?'. Returns matches ranked by structural overlap with direction: 'input' | 'output' | 'both'
| Parameter | Type | Required | Notes |
|---|---|---|---|
| payload | yes | Arbitrary JSON value whose shape will be matched against capability schemas. |
Return a compact roster of every capability with at least one enabled provider, grouped by category, with the best current conformance per capability. Use this as a self-introspection step: call once at the start of a task to know what is and isn't available, before deciding whether to attempt or to tell the user 'this isn't possible here'.
No parameter schema on file.
Execute a capability call against a chosen provider with typed inputs. WRITE tool when the capability's category ends in '.write' (creates state, sends notifications, charges money, etc.) — confirm with the user before calling for any non-reversible capability. Read capabilities (category ending '.read') are safe to call without confirmation. Validates inputs against the capability's JSON Schema.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| capability_id | string | yes | Format: <domain>.<verb>. |
| provider_id | string | yes | Provider identifier from get_capability_spec. Format: <transport>:<id>, e.g. 'bookio:salon-aurora'. |
| inputs | object | yes | Canonical inputs matching the capability's input JSON Schema exactly (snake_case keys). |
| agent_vendor | string | no | Self-identification (claude, chatgpt, cursor, ...). Strongly recommended. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Whatcanido — MCP Server for Service Businesses or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 0.2.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest134f9e00e6c55c8ec67c2a5b4e262a3a73402b497e716c503b03545890345fdd
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| find_providers | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_provider_actions | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| submit_action | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| get_action_status | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| discover_capabilities | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_capability_spec | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| plan_capabilities | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| reverse_search_capabilities | external-sinkuntrusted-input | external-sink: keyword "webhook"; untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| list_available_capabilities | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| invoke_capability | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest134f9e00e6c55c8e
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.2.0.
0.2.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Whatcanido — MCP Server for Service Businesses can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.