Model Context Protocol (MCP) server for Apollo.io API integration
Nothing to run from here
Qampi 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.
96/100
trust score
11
downloads a day
local
runs on your machine
563
downloads in 30d
What it does
LinkedIn outreach from your agent: find prospects, add leads, run campaigns, read results.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'QAMPI_API_KEY=${QAMPI_API_KEY}' --transport stdio qampi-mcp '--' npx -y @qampi/mcp-server
# 2 — ask your agent for something these tools do
# qampi_status, qampi_list_templates, qampi_list_leads and 12 more
It needs QAMPI_API_KEY: this reads it from your environment, so export it first.
Qampi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publisher
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Qampi as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads QAMPI_API_KEY (Qampi API key (Settings → API keys)) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx QAMPI_API_KEY … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'QAMPI_API_KEY=${QAMPI_API_KEY}' --transport stdio qampi-mcp '--' npx -y @qampi/mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: QAMPI_API_KEY — Qampi API key (Settings → API keys).. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
15 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.
Whether the Qampi account is usable right now: LinkedIn connection state, account health, plan, and TODAY'S REMAINING BUDGET for invites/messages/searches. Call this before planning outreach — the invite allowance is not a fixed number, it ramps with account age and acceptance rate.
No parameter schema on file.
Prebuilt outreach sequences. Use a template id with qampi_create_campaign.
No parameter schema on file.
Leads in the Qampi account, newest first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Default 25. |
| offset | integer | no | — |
| status | string | no | Filter by lead status, e.g. IMPORTED, PENDING, CONNECTED, REPLIED. |
One lead with its enrichment and current status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| leadId | string | yes | Qampi lead id. |
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
Campaign configuration and progress.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaignId | string | yes | — |
Per-lead progress within a campaign — who is pending, connected, replied, or parked.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaignId | string | yes | — |
| limit | integer | no | — |
Search LinkedIn through the connected account. COSTS one search from the monthly budget (LinkedIn's commercial-use limit), so prefer one well-built query over several exploratory ones. Returns up to 10 per page.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keywords | string | yes | Plain keywords, e.g. "head of growth fintech". Boolean operators are not supported. |
| title | string | no | — |
| location | string | no | — |
| degrees | array | no | Connection degrees to include, e.g. [2,3]. |
| page | integer | no | — |
Add leads to Qampi. Does NOT contact anyone — it only puts them in the database.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| leads | array | yes | — |
Set tags or a free-text note on a lead. Only tags and notes are writable — enrichment fields are written by Qampi's profile visits, and lead status is derived by the engine.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| leadId | string | yes | — |
| tags | array | no | Replaces the existing tag set. |
| info | string | no | Free-text note. |
Creates a campaign in DRAFT. Nothing is sent until qampi_launch_campaign is called.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| templateId | string | yes | From qampi_list_templates. |
| name | string | yes | — |
Adds existing leads to a campaign. Still sends nothing — launching is a separate step.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaignId | string | yes | — |
| leadIds | array | yes | — |
STARTS REAL OUTREACH to real people from the connected LinkedIn account: profile visits, invitations, messages, as configured in the campaign. This is not reversible — a sent invitation cannot be unsent, and a withdrawn one cannot be resent for three weeks. Confirm with the human first, then pass…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaignId | string | yes | — |
| confirm | boolean | yes | Must be true, and should reflect an explicit human go-ahead. |
Finds and verifies a work email. Consumes one email-finder credit per lookup.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| firstName | string | yes | — |
| lastName | string | yes | — |
| company | string | no | — |
| companyDomain | string | no | — |
| jobTitle | string | no | — |
Subscribe a URL to Qampi lifecycle events (lead.connected, lead.replied, …) so a pipeline can react to outreach outcomes instead of polling.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | HTTPS endpoint that will receive POSTs. |
| events | array | yes | Event names; list them with qampi_status → see docs. |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- 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 Qampi 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: —
ATrust score 96 / 100
Release 0.1.2 · scanned 15 Oct 2026
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 score96
Findings0 threat · 2 capability
Capabilitymoderate
Coveragesource
Verificationrepo
Surface digest1cca01f0a20773e0bcb1e74cf10d2207b8bc458cfb7337faaa56862968131870
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (15 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
7 of the 15 recovered tools are registered only when WRITES_ENABLED holds (dist/index.js:138) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 8.
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.
8 tools are registered unconditionally · 7 more only when WRITES_ENABLED holds (dist/index.js:138) — typically when a key or option is configured. All 15 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| qampi_status | no tags | |
| qampi_list_templates | no tags | |
| qampi_list_leads | no tags | |
| qampi_get_lead | no tags | |
| qampi_list_campaigns | no tags | |
| qampi_get_campaign | no tags | |
| qampi_campaign_leads | no tags | |
| qampi_search_people | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| qampi_add_leads conditional | state-write | state-write: declares readOnlyHint: false |
| qampi_annotate_lead conditional | state-write | state-write: declares readOnlyHint: false |
| qampi_create_campaign conditional | state-write | state-write: declares readOnlyHint: false |
| qampi_enroll_leads conditional | state-write | state-write: declares readOnlyHint: false |
| qampi_launch_campaign conditional | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| qampi_find_email conditional | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| qampi_register_webhook conditional | external-sinkstate-write | external-sink: keyword "webhook"; state-write: declares readOnlyHint: false |
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 digest1cca01f0a20773e0
Scanned2026-10-15
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.2. Pin a release below and the command asks for exactly that one.
0.1.2
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 Qampi 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.