Turn a client conversation into a priced proposal draft and track whether clients open or accept it.
myPhoner 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.
What it does
Work myPhoner calling lists and leads: search, log call outcomes, add, update and assign leads.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http myphoner-mcp-by-usefulapi https://myphoner.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# myphoner_list_lists, myphoner_get_list, myphoner_list_columns and 15 more
myPhoner 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.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 myphoner-mcp-by-usefulapi https://myphoner.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
18 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.
All calling lists (campaigns) in the account: id, name, creation date, number of leads and whether the list guarantees the default fields. Start here to find a list id. GET /lists.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| locked_on_defaults | boolean | no | true = only lists that guarantee the default fields. |
One calling list with its lead count and its call back / winner / loser / archive / skip categories. GET /lists/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | integer | yes | List id from myphoner_list_lists. |
The fields (columns) of a list. The key of each is the name to use when creating, updating or finding leads. GET /lists/{id}/columns.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | integer | yes | List id. |
Lead counts of a list by state (new, call back, won, lost, archived) and by category within each state. Use it for campaign progress and conversion questions. GET /lists/{id}/stats.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | integer | yes | List id. |
Create a new, empty calling list with its fields. Creates data in the account (nothing is sent to anyone). Field kinds: none (text), phone, email, url, boolean, integer, date, text (multi-line), options, address. POST /lists.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Name of the list. |
| columns | array | no | Fields in order. Omit to let myPhoner use its defaults. |
| description | string | no | Call script shown to agents while working the list. |
| call_back_categories | string | no | Comma-separated sub-categories for call backs. |
| winner_categories | string | no | Comma-separated sub-categories for winners. |
| loser_categories | string | no | Comma-separated sub-categories for losers. |
| archive_categories | string | no | Comma-separated sub-categories for archived leads. |
| skip_categories | string | no | Comma-separated sub-categories for skips. |
Leads of one list, newest first by creation date (or most recently updated first with order=last_updated_first). Each lead has its state (new, call_back, won, lost, archived), category, scheduled call back, who claimed it and its lead_data fields. GET /lists/{id}/leads.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | integer | yes | List id. |
| order | string | no | last_updated_first = by last change, newest first; default newest created first. |
| page | integer | no | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | no | Leads per page, 1-100 (default 50). |
One lead with its state, category, claim, duplicates and all lead_data fields. GET /leads/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lead_id | integer | yes | Lead id. |
Exact match on one or more fields of a list, for example a phone number or an email address (to check whether a lead already exists). All fields must match unless match_all is false. GET /lists/{id}/leads/find.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | integer | yes | List id. |
| fields | object | yes | Column key → non-empty value to match exactly, e.g. {"mobile_phone":"15324083898652"}. Keys from myphoner_list_columns. |
| match_all | boolean | no | true (default) = every field must match; false = any one is enough. |
Free-text search across lead data and activity logs (comments, events), like the search box in myPhoner; optionally limited to some lists. Returns the total hit count and one page of leads. GET /leads/search.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | The search text, e.g. a company name, city or phone number. |
| list_ids | array | no | Limit the search to these list ids. |
| page | integer | no | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | no | Leads per page, 1-100 (default 50). |
Add a new lead to a list. Keys of fields are the list's column keys (myphoner_list_columns). Creates data only; nothing is sent to the lead. Duplicate detection runs in the background a few minutes later (check detected_duplicates on the lead afterwards). POST /lists/{id}/leads.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | integer | yes | List the lead is added to. |
| fields | object | yes | Lead data keyed by the list's column keys (see myphoner_list_columns), e.g. {"first_name":"Ada","mobile_phone":"+4512345678"}. |
Change field values of an existing lead (only the fields you pass change). Keys of fields are the list's column keys (myphoner_list_columns). Overwrites the old values; use null to clear one. PATCH /leads/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lead_id | integer | yes | Lead id. |
| fields | object | yes | Lead data keyed by the list's column keys (see myphoner_list_columns), e.g. {"first_name":"Ada","mobile_phone":"+4512345678"}. |
Mark a lead as a winner (a won deal). The lead moves to that state and an event is logged on it; nothing is sent to the lead. Optionally add a comment and an existing winner category. POST /leads/{id}/winner.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lead_id | integer | yes | Lead id. |
| call_back_in | integer | no | Minutes until a scheduled call back (max one year). |
| scheduled_for | string | no | When the call back is due: ISO 8601 date-time with a timezone, e.g. 2026-11-02T09:30:00Z. Takes precedence over call_back_in. |
| comment | string | no | Text added as a comment on the lead's event. |
| category | string | no | A category of the list; must match an existing one exactly, including case. |
Mark a lead as a loser (not interested / lost). The lead moves to that state and an event is logged on it; nothing is sent to the lead. Optionally add a comment and an existing loser category. POST /leads/{id}/loser.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lead_id | integer | yes | Lead id. |
| call_back_in | integer | no | Minutes until a scheduled call back (max one year). |
| scheduled_for | string | no | When the call back is due: ISO 8601 date-time with a timezone, e.g. 2026-11-02T09:30:00Z. Takes precedence over call_back_in. |
| comment | string | no | Text added as a comment on the lead's event. |
| category | string | no | A category of the list; must match an existing one exactly, including case. |
Schedule a lead for a call back. The lead moves to that state and an event is logged on it; nothing is sent to the lead. Set when with call_back_in (minutes) or scheduled_for; optionally a comment and an existing call back category. POST /leads/{id}/call_back.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lead_id | integer | yes | Lead id. |
| call_back_in | integer | no | Minutes until a scheduled call back (max one year). |
| scheduled_for | string | no | When the call back is due: ISO 8601 date-time with a timezone, e.g. 2026-11-02T09:30:00Z. Takes precedence over call_back_in. |
| comment | string | no | Text added as a comment on the lead's event. |
| category | string | no | A category of the list; must match an existing one exactly, including case. |
Archive a lead (it leaves the calling queue). The lead moves to that state and an event is logged on it; nothing is sent to the lead. Optionally add a comment and an existing archive category. POST /leads/{id}/archive.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lead_id | integer | yes | Lead id. |
| call_back_in | integer | no | Minutes until a scheduled call back (max one year). |
| scheduled_for | string | no | When the call back is due: ISO 8601 date-time with a timezone, e.g. 2026-11-02T09:30:00Z. Takes precedence over call_back_in. |
| comment | string | no | Text added as a comment on the lead's event. |
| category | string | no | A category of the list; must match an existing one exactly, including case. |
Give the claim on a lead to a user (the lead then shows up in that agent's queue), identified by user id or email. PATCH /leads/{id}/delegate.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lead_id | integer | yes | Lead id. |
| delegate_to | yes | User id or the user's email address. |
Move a lead to another list. The destination may be the lead's current list, which with release_claim=true just releases a claimed lead. PATCH /leads/{id}/migrate.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lead_id | integer | yes | Lead id. |
| to_list_id | integer | yes | Destination list id. |
| release_claim | boolean | no | true = also release the lead if an agent has claimed it. |
One call made from myPhoner: who called, the number dialed, duration (0 = unanswered), direction, disposition (normal, voicemail, no_answer, busy ...), state, the lead and list it belongs to, and recording links. GET /calls/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| call_id | integer | yes | Call id (the number at the end of a call's location path). |
- 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 myPhoner MCP by usefulapi or to call it, at any volume.
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.
| 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 |
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.
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 |
|---|---|---|
| myphoner_list_lists | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| myphoner_get_list | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| myphoner_list_columns | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| myphoner_get_list_stats | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| myphoner_create_list | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| myphoner_list_leads | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| myphoner_get_lead | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| myphoner_find_leads | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| myphoner_search_leads | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| myphoner_create_lead | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| myphoner_update_lead | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| myphoner_mark_lead_winner | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| myphoner_mark_lead_loser | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| myphoner_mark_lead_call_back | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| myphoner_archive_lead | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| myphoner_delegate_lead | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| myphoner_move_lead | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| myphoner_get_call | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
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.
Supply chain and provenance
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.14.0.
No release note was published with this version.
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.
Any signed-in account that does not publish myPhoner 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.
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.