Skip to content

myPhoner MCP by usefulapi

io.usefulapi/myphonerusefulapi.iostreamable-httpv1.20.4Scanned

Work myPhoner calling lists and leads: search, log call outcomes, add, update and assign leads.

18 tools: 7 can delete or cancel things, 2 change things and 9 only read.

Tools: 7 delete, 0 irreversible, 2 write, 9 read.
  • Reads private data · 1
  • Reads text others write · 18
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

9 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the myPhoner MCP by usefulapi can do

The myPhoner MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 18 tools. It can delete or cancel things (7 tools: myphoner_update_lead, myphoner_mark_lead_winner, myphoner_mark_lead_loser, myphoner_mark_lead_call_back and 3 more) and create or change data (2 tools: myphoner_create_list and myphoner_create_lead). 9 tools only read.

1 tool reads private data (myphoner_find_leads); 18 tools bring in text other people can write (myphoner_list_lists, myphoner_get_list, myphoner_list_columns and 15 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.20.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

18 tools

Deletes or cancels 7Claude Code: deny
  • myphoner_archive_leadArchive a lead (it leaves the calling queue).Reads text others writeNo findings

    Why it is in this group

    • The name "myphoner_archive_lead" says "archive": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Archive a lead
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • myphoner_delegate_leadGive the claim on a lead to a user (the lead then shows up in that agent's queue), identified by user id or email.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Delegate or claim a lead
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • myphoner_mark_lead_call_backSchedule a lead for a call back.Reads text others writeNo findings

    Why it is in this group

    • The name "myphoner_mark_lead_call_back" says "mark": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Mark a lead for call back
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • myphoner_mark_lead_loserMark a lead as a loser (not interested / lost).Reads text others writeNo findings

    Why it is in this group

    • The name "myphoner_mark_lead_loser" says "mark": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Mark a lead as loser
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • myphoner_mark_lead_winnerMark a lead as a winner (a won deal).Reads text others writeNo findings

    Why it is in this group

    • The name "myphoner_mark_lead_winner" says "mark": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Mark a lead as winner
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • myphoner_move_leadMove a lead to another list.Reads text others writeNo findings

    Why it is in this group

    • The name "myphoner_move_lead" says "move": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Move a lead to another list
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • myphoner_update_leadChange field values of an existing lead (only the fields you pass change).Reads text others writeNo findings

    Why it is in this group

    • The name "myphoner_update_lead" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Update lead data
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
Changes things 2Claude Code: ask
  • myphoner_create_leadAdd a new lead to a list.Reads text others writeNo findings

    Why it is in this group

    • The name "myphoner_create_lead" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create a lead
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • myphoner_create_listCreate a new, empty calling list with its fields.Reads text others writeNo findings

    Why it is in this group

    • The name "myphoner_create_list" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create a calling list
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 9Show 9 read-only tools
  • myphoner_find_leadsExact 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).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "myphoner_find_leads" says "find": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find leads by field
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • myphoner_get_callOne 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 …Reads text others writeNo findings

    Why it is in this group

    • The name "myphoner_get_call" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote 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}.

    Annotations the server declares

    • title: Get a call
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • myphoner_get_leadOne lead with its state, category, claim, duplicates and all lead_data fields.Reads text others writeNo findings

    Why it is in this group

    • The name "myphoner_get_lead" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    One lead with its state, category, claim, duplicates and all lead_data fields. GET /leads/{id}.

    Annotations the server declares

    • title: Get a lead
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • myphoner_get_listOne calling list with its lead count and its call back / winner / loser / archive / skip categories.Reads text others writeNo findings

    Why it is in this group

    • The name "myphoner_get_list" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    One calling list with its lead count and its call back / winner / loser / archive / skip categories. GET /lists/{id}.

    Annotations the server declares

    • title: Get a calling list
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • myphoner_get_list_statsLead counts of a list by state (new, call back, won, lost, archived) and by category within each state.Reads text others writeNo findings

    Why it is in this group

    • The name "myphoner_get_list_stats" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get list statistics
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • myphoner_list_columnsThe fields (columns) of a list.Reads text others writeNo findings

    Why it is in this group

    • The name "myphoner_list_columns" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List the fields of a list
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • myphoner_list_leadsLeads of one list, newest first by creation date (or most recently updated first with order=last_updated_first).Reads text others writeNo findings

    Why it is in this group

    • The name "myphoner_list_leads" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List the leads in a list
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • myphoner_list_listsAll calling lists (campaigns) in the account: id, name, creation date, number of leads and whether the list guarantees the default fields.Reads text others writeNo findings

    Why it is in this group

    • The name "myphoner_list_lists" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List calling lists
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • myphoner_search_leadsFree-text search across lead data and activity logs (comments, events), like the search box in myPhoner; optionally limited to some lists.Reads text others writeNo findings

    Why it is in this group

    • The name "myphoner_search_leads" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "comment": it reads comments, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Search leads
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 15, 2026, 13:31 UTC, unchanged since Oct 31, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 31, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 9 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://myphoner.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://myphoner.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 9 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://myphoner.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://myphoner.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.20.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http myphoner https://myphoner.usefulapi.io/mcp
claude mcp add --transport http myphoner https://myphoner.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__myphoner__myphoner_list_lists",
      "mcp__myphoner__myphoner_get_list",
      "mcp__myphoner__myphoner_list_columns",
      "mcp__myphoner__myphoner_get_list_stats",
      "mcp__myphoner__myphoner_list_leads",
      "mcp__myphoner__myphoner_get_lead",
      "mcp__myphoner__myphoner_find_leads",
      "mcp__myphoner__myphoner_search_leads",
      "mcp__myphoner__myphoner_get_call"
    ],
    "ask": [
      "mcp__myphoner__myphoner_create_list",
      "mcp__myphoner__myphoner_create_lead"
    ],
    "deny": [
      "mcp__myphoner__myphoner_update_lead",
      "mcp__myphoner__myphoner_mark_lead_winner",
      "mcp__myphoner__myphoner_mark_lead_loser",
      "mcp__myphoner__myphoner_mark_lead_call_back",
      "mcp__myphoner__myphoner_archive_lead",
      "mcp__myphoner__myphoner_delegate_lead",
      "mcp__myphoner__myphoner_move_lead"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as myphoner. Review it before you use it.

Capability tags behind 18 rules
  • mcp__myphoner__myphoner_list_lists untrusted-input
  • mcp__myphoner__myphoner_get_list untrusted-input
  • mcp__myphoner__myphoner_list_columns untrusted-input
  • mcp__myphoner__myphoner_get_list_stats untrusted-input
  • mcp__myphoner__myphoner_create_list untrusted-input
  • mcp__myphoner__myphoner_list_leads untrusted-input
  • mcp__myphoner__myphoner_get_lead untrusted-input
  • mcp__myphoner__myphoner_find_leads private-data, untrusted-input
  • mcp__myphoner__myphoner_search_leads untrusted-input
  • mcp__myphoner__myphoner_create_lead untrusted-input
  • mcp__myphoner__myphoner_update_lead untrusted-input
  • mcp__myphoner__myphoner_mark_lead_winner untrusted-input
  • mcp__myphoner__myphoner_mark_lead_loser untrusted-input
  • mcp__myphoner__myphoner_mark_lead_call_back untrusted-input
  • mcp__myphoner__myphoner_archive_lead untrusted-input
  • mcp__myphoner__myphoner_delegate_lead untrusted-input
  • mcp__myphoner__myphoner_move_lead untrusted-input
  • mcp__myphoner__myphoner_get_call untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/myphoner/verify?hash=ce45e53e34d90ea5ee7304dce41efd19e37b40308bebcce593b85bd55209f38d" | jq -e '.changed == false'

Pinned hash ce45e53e34d9, from Oct 25, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/myphoner/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/myphoner
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/myphoner.svg)](https://radar.anlyon.com/servers/io.usefulapi/myphoner)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

myPhoner MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the myPhoner MCP by usefulapi safe?

No scan can promise that. What its definitions show: 18 tools, 9 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the myPhoner MCP by usefulapi delete data?

Yes. 7 tools can delete, cancel or revoke something: myphoner_update_lead, myphoner_mark_lead_winner, myphoner_mark_lead_loser, myphoner_mark_lead_call_back, myphoner_archive_lead, myphoner_delegate_lead and 1 more.

Can the myPhoner MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the myPhoner MCP by usefulapi have?

18 tools: 7 destructive, 2 write, 9 read. myphoner_update_lead, myphoner_mark_lead_winner, myphoner_mark_lead_loser, myphoner_mark_lead_call_back, myphoner_archive_lead, myphoner_delegate_lead, myphoner_move_lead, myphoner_create_list and 10 more.

Does the myPhoner MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the myPhoner MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the myPhoner MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.