Model Context Protocol (MCP) server for Apollo.io API integration
Nothing to run from here
noCRM.io MCP by usefulapi 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
24
tools declared
remote
at its publisher
—
calls last 7d
What it does
Read noCRM.io leads, pipeline steps, comments and client folders; create, update and assign leads.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http nocrm-io-mcp-by-usefulapi https://nocrm-io.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# nocrm_list_leads, nocrm_list_unassigned_leads, nocrm_get_lead and 21 more
noCRM.io MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 664 servers
usefulapi664 servers
25 categories
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 nocrm-io-mcp-by-usefulapi https://nocrm-io.usefulapi.io/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
24 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.
List or search sales leads (noCRM.io's opportunities), newest first by default, with title, pipeline step, status, amount, probability, tags, owner, next reminder and the contact details in the description. Filter by status, step (names or ids, not mixed), owner, tags, email, starred or a date range. Unassigned leads are excluded unless include_unassigned is true. GET /leads.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | array | no | Only leads in these statuses (todo = to do, standby = waiting for a reminder date). |
| steps | no | Only leads in these pipeline steps: exact step names OR step ids (not mixed). See nocrm_list_steps. | |
| user_id | no | Only leads owned by this user (id or email). | |
| tags | array | no | Only leads carrying ALL of these tags. |
| string | no | Only leads whose description or comments contain this email address. | |
| starred | boolean | no | true = only starred leads. |
| include_unassigned | boolean | no | Also return leads that have no owner (default false). |
| order | string | no | Sort attribute (default id). |
| direction | string | no | Sort direction (default desc). |
| date_range_type | string | no | Which date start_date/end_date apply to (default creation). |
| start_date | string | no | From this date (yyyy-mm-dd), by date_range_type. |
| end_date | string | no | Until this date (yyyy-mm-dd), by date_range_type. |
| updated_after | string | no | Only leads updated on or after this date (yyyy-mm-dd). Do not combine with date_range_type. |
| limit | integer | no | Results per call, 1-100 (default 25). |
| offset | integer | no | Skip this many results (default 0). Pass the previous reply's next_offset. |
Leads that have no owner yet (for example web-form or API leads waiting to be handed to a salesperson). GET /leads/unassigned.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Results per call, 1-100 (default 25). |
One lead by id: title, step, status, amount, probability, tags, owner, client folder, team, reminder, and the full description with the contact's details. GET /leads/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lead_id | integer | yes | noCRM.io lead id. |
The comments (notes, logged calls/meetings/emails) on a lead, newest first by default. GET /leads/{id}/comments.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lead_id | integer | yes | noCRM.io lead id. |
| direction | string | no | Sort by date (default desc). |
The timeline of a lead: creation, assignments, step and status changes, amount changes, comments and emails sent, with who did it and when. Filter by date range, action type or user. GET /leads/{id}/action_histories.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lead_id | integer | yes | noCRM.io lead id. |
| from | string | no | From this date (yyyy-mm-dd). |
| to | string | no | Until this date (yyyy-mm-dd). |
| action_type | string | no | Only this kind of action. |
| direction | string | no | Sort by id (default asc). |
| limit | integer | no | Results per call, 1-100 (default 25). |
| offset | integer | no | Skip this many results (default 0). Pass the previous reply's next_offset. |
Leads that noCRM.io detects as possible duplicates of this lead (same email or key field). GET /leads/{id}/duplicates.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lead_id | integer | yes | noCRM.io lead id. |
File attachments on a lead (names, ids, sizes, links). GET /leads/{id}/attachments.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lead_id | integer | yes | noCRM.io lead id. |
Post-sales processes (task checklists created from a template) of one lead OR of one user. Needs lead_id or user_id. Post-sales is a higher-edition feature (HTTP 403 otherwise). GET /follow_ups.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lead_id | integer | no | Follow-ups of this lead. |
| user_id | no | Follow-ups of this user (id or email). | |
| status | array | no | Only these statuses. |
The sales pipelines of the account (one unless the multiple-pipelines feature is on). GET /pipelines.
No parameter schema on file.
The steps (stages) of the sales pipeline in order, with ids, positions and their pipeline. Use the ids or names when filtering leads or moving a lead. GET /steps.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| direction | string | no | Order by position (default asc). |
The users (salespeople) of the account with name, email, phone, role (admin or not) and whether they are active or deactivated. Deleted users are included, flagged is_disabled. GET /users.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | no | Only the user with this email. | |
| firstname | string | no | — |
| lastname | string | no | — |
| status | string | no | Default all. |
| role | string | no | Default all. |
| teams | array | no | Only users in these teams (ids or names). |
One user by id or email address. GET /users/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| user | yes | A user id or the user's email address (see nocrm_list_users). |
Sales teams with their members and who manages each. The Teams feature must be on in the account (HTTP 403 otherwise). GET /teams.
No parameter schema on file.
Client folders (accounts that group several leads), ordered by name by default. GET /clients.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order | string | no | Order by name (default) or id. |
| direction | string | no | Default asc. |
One client folder by id, with its contact fields and owner. GET /clients/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_id | integer | yes | Client folder id. |
The activity types (call, email, meeting and their outcomes) that can be set on a comment or reminder. GET /activities.
No parameter schema on file.
The account's predefined tags (admin keys only; an HTTP 401 unauthorized_non_admin means the key lacks rights). GET /predefined_tags.
No parameter schema on file.
The custom fields defined for leads or client folders. GET /fields.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | no | Only fields of this type. |
WRITE: create a new lead. The description holds the contact's details, one 'Label: value' per line (for example 'Firstname: Ada', 'Email: ada@example.com', 'Phone: ...'); noCRM.io reads those lines. Without user_id the lead is created unassigned; a pipeline step can only be set when the lead is assigned. Not idempotent: calling twice creates two leads. POST /leads.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | Lead title, usually the company name. |
| description | string | yes | Contact details and notes, one 'Label: value' per line. |
| user_id | no | Owner (id or email). Omit for an unassigned lead. | |
| tags | array | no | Tags (created if new). |
| step | no | Pipeline step id or exact name. Needs user_id. |
WRITE: change a lead: title, status (won, lost, cancelled, todo or standby), pipeline step, amount, probability, star, estimated closing date, tags (replaces the lead's tag list), or append text to the description (existing description text is never replaced). Moving to standby needs remind_date. Only the fields you pass change. PUT /leads/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lead_id | integer | yes | noCRM.io lead id. |
| title | string | no | — |
| status | string | no | New status. standby needs remind_date. |
| step | no | Move to this step (id or exact name; prefer the id when pipelines share names). | |
| amount | number | no | Deal amount in the account currency. |
| probability | integer | no | Win probability, percent. |
| starred | boolean | no | — |
| estimated_closing_date | string | no | yyyy-mm-dd, in the account's time zone. |
| remind_date | string | no | Reminder date yyyy-mm-dd (required for standby). |
| remind_time | string | no | Reminder time HH:MM, 24 h, in 15-minute steps. |
| reminder_note | string | no | Note stored with the reminder. |
| tags | array | no | The lead's tags after the update (replaces the current list; new tags are created). |
| append_description | string | no | Text added at the end of the description. |
WRITE: assign a lead to a user (id or email), replacing its current owner. The owner may get a notification from noCRM.io. POST /leads/{id}/assign.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lead_id | integer | yes | noCRM.io lead id. |
| user_id | yes | The new owner (id or email). |
WRITE: add a comment (an internal note) to a lead, optionally typed as an activity such as a call or meeting. It is visible to the lead's team in noCRM.io and sends nothing to the customer. Not idempotent. POST /leads/{id}/comments.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lead_id | integer | yes | noCRM.io lead id. |
| content | string | yes | The comment text. |
| activity_id | integer | no | Activity type id (see nocrm_list_activities), for example the id of 'Call'. |
WRITE: create a client folder (an account that groups leads). Not idempotent. POST /clients.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Folder name, usually the company. |
| description | string | no | For example the address. |
| user_id | no | Owner (id or email). |
WRITE: file a lead under a client folder. POST /leads/{id}/add_to_client.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lead_id | integer | yes | noCRM.io lead id. |
| client_id | integer | yes | Client folder id (see nocrm_list_client_folders). |
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 noCRM.io MCP by usefulapi 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 1.17.5 · scanned 8 Nov 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 digest6c17345a456b6147fe137f5c94856742263d5473b17ddd28f32b574209ba5800
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 |
|---|---|---|
| nocrm_list_leads | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| nocrm_list_unassigned_leads | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| nocrm_get_lead | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| nocrm_list_lead_comments | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| nocrm_list_lead_history | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| nocrm_get_lead_duplicates | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| nocrm_list_lead_attachments | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| nocrm_list_follow_ups | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| nocrm_list_pipelines | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| nocrm_list_steps | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| nocrm_list_users | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| nocrm_get_user | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| nocrm_list_teams | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| nocrm_list_client_folders | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| nocrm_get_client_folder | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| nocrm_list_activities | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| nocrm_list_predefined_tags | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| nocrm_list_fields | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| nocrm_create_lead | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| nocrm_update_lead | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| nocrm_assign_lead | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| nocrm_add_lead_comment | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| nocrm_create_client_folder | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| nocrm_add_lead_to_client_folder | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, 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 digest6c17345a456b6147
Scanned2026-11-08
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 1.17.5.
1.17.5
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 noCRM.io MCP by usefulapi 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.