Copper MCP by usefulapi
io.usefulapi/copperusefulapi.iostreamable-httpv1.41.4Scanned
Read and write Copper CRM people, companies, opportunities and activities.
22 tools: 7 can delete or cancel things and 15 only read.
- Reads private data · 4
- Reads text others write · 1
- Can send data out · 0
- 1 finding
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
7 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 Copper MCP by usefulapi can do
The Copper MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 22 tools. It can delete or cancel things (7 tools: copper_create_person, copper_update_person, copper_create_company, copper_create_opportunity and 3 more). 15 tools only read.
4 tools read private data (copper_list_users, copper_search_people, copper_get_person and 1 more); 1 tool brings in text other people can write (copper_list_users).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Last scanned Oct 25, 2026, version 1.41.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.
22 tools
Deletes or cancels 7Claude Code: deny
copper_create_companyCreate a new company.No findings
Why it is in this group
- The name "copper_create_company" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Create a new company. Copper REST: POST /companies.
Annotations the server declares
- title: Create company
- destructiveHint: true
copper_create_leadCreate a new lead.No findings
Why it is in this group
- The name "copper_create_lead" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Create a new lead. Copper REST: POST /leads.
Annotations the server declares
- title: Create lead
- destructiveHint: true
copper_create_opportunityCreate a new opportunity (deal).No findings
Why it is in this group
- The name "copper_create_opportunity" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Create a new opportunity (deal). `name` and `primary_contact_id` are required by Copper. Copper REST: POST /opportunities.
Annotations the server declares
- title: Create opportunity
- destructiveHint: true
copper_create_personCreate a new person (contact).No findings
Why it is in this group
- The name "copper_create_person" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Create a new person (contact). Copper REST: POST /people.
Annotations the server declares
- title: Create person
- destructiveHint: true
copper_create_taskCreate a new task.No findings
Why it is in this group
- The name "copper_create_task" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Create a new task. Copper REST: POST /tasks.
Annotations the server declares
- title: Create task
- destructiveHint: true
copper_log_activityLog a user activity (e.g.1 finding
Why it is in this group
- The name "copper_log_activity" says "log": a word for reading.
- The server marks it destructive (destructiveHint: true).
Findings
- Warn
The server marks "copper_log_activity" destructive (destructiveHint: true), and its name says "log", a word for reading.
What this check looks forMatched text
annotations: {"destructiveHint":true}; The name "copper_log_activity" says "log": a word for reading.
Description, as the server wrote it Log a user activity (e.g. a note or call) on a record. Get the activity_type_id from copper_list_activity_types. Copper REST: POST /activities.
Annotations the server declares
- title: Log activity
- destructiveHint: true
copper_update_personUpdate fields on an existing person.No findings
Why it is in this group
- The name "copper_update_person" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Update fields on an existing person. Only provided fields are changed. Copper REST: PUT /people/{id}.
Annotations the server declares
- title: Update person
- destructiveHint: true
Only reads 15Show 15 read-only tools
copper_get_accountGet details of the authenticated Copper account.No findings
Why it is in this group
- The name "copper_get_account" says "get": a word for reading.
Description, as the server wrote it Get details of the authenticated Copper account. Copper REST: GET /account.
Annotations the server declares
- title: Get account
- readOnlyHint: true
copper_get_companyGet a single company by id.No findings
Why it is in this group
- The name "copper_get_company" says "get": a word for reading.
Description, as the server wrote it Get a single company by id. Copper REST: GET /companies/{id}.
Annotations the server declares
- title: Get company
- readOnlyHint: true
copper_get_leadGet a single lead by id.No findings
Why it is in this group
- The name "copper_get_lead" says "get": a word for reading.
Description, as the server wrote it Get a single lead by id. Copper REST: GET /leads/{id}.
Annotations the server declares
- title: Get lead
- readOnlyHint: true
copper_get_opportunityGet a single opportunity (deal) by id.No findings
Why it is in this group
- The name "copper_get_opportunity" says "get": a word for reading.
Description, as the server wrote it Get a single opportunity (deal) by id. Copper REST: GET /opportunities/{id}.
Annotations the server declares
- title: Get opportunity
- readOnlyHint: true
copper_get_personGet a single person (contact) by id.Reads private dataNo findings
Why it is in this group
- The name "copper_get_person" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "contact": it reads contacts.
Description, as the server wrote it Get a single person (contact) by id. Copper REST: GET /people/{id}.
Annotations the server declares
- title: Get person
- readOnlyHint: true
copper_get_taskGet a single task by id.No findings
Why it is in this group
- The name "copper_get_task" says "get": a word for reading.
Description, as the server wrote it Get a single task by id. Copper REST: GET /tasks/{id}.
Annotations the server declares
- title: Get task
- readOnlyHint: true
copper_list_activitiesList activities (notes, calls, meetings, system events) attached to a record.Reads private dataNo findings
Why it is in this group
- The name "copper_list_activities" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "note": it reads notes.
Description, as the server wrote it List activities (notes, calls, meetings, system events) attached to a record. Copper REST: POST /activities/search.
Annotations the server declares
- title: List activities
- readOnlyHint: true
copper_list_activity_typesList the account's activity types (user + system), needed to log an activity.No findings
Why it is in this group
- The name "copper_list_activity_types" says "list": a word for reading.
Description, as the server wrote it List the account's activity types (user + system), needed to log an activity. Copper REST: GET /activity_types.
Annotations the server declares
- title: List activity types
- readOnlyHint: true
copper_list_pipelinesList sales pipelines and their stages (ids needed to place opportunities).No findings
Why it is in this group
- The name "copper_list_pipelines" says "list": a word for reading.
Description, as the server wrote it List sales pipelines and their stages (ids needed to place opportunities). Copper REST: GET /pipelines.
Annotations the server declares
- title: List pipelines
- readOnlyHint: true
copper_list_usersList users in the Copper account (id, name, email) — useful for resolving assignee ids.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "copper_list_users" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "email": it reads mail.
- untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it List users in the Copper account (id, name, email) — useful for resolving assignee ids. Copper REST: POST /users/search.
Annotations the server declares
- title: List users
- readOnlyHint: true
copper_search_companiesSearch/list companies.No findings
Why it is in this group
- The name "copper_search_companies" says "search": a word for reading.
Description, as the server wrote it Search/list companies. All filters optional; returns a page of companies. Copper REST: POST /companies/search.
Annotations the server declares
- title: Search companies
- readOnlyHint: true
copper_search_leadsSearch/list leads.No findings
Why it is in this group
- The name "copper_search_leads" says "search": a word for reading.
Description, as the server wrote it Search/list leads. All filters optional; returns a page of leads. Copper REST: POST /leads/search.
Annotations the server declares
- title: Search leads
- readOnlyHint: true
copper_search_opportunitiesSearch/list opportunities (deals).No findings
Why it is in this group
- The name "copper_search_opportunities" says "search": a word for reading.
Description, as the server wrote it Search/list opportunities (deals). All filters optional; returns a page of opportunities. Copper REST: POST /opportunities/search.
Annotations the server declares
- title: Search opportunities
- readOnlyHint: true
copper_search_peopleSearch/list people (contacts).Reads private dataNo findings
Why it is in this group
- The name "copper_search_people" says "search": a word for reading.
What it can reach
- private-dataThe description's first sentence says "search" and "contact": it reads contacts.
Description, as the server wrote it Search/list people (contacts). All filters optional; returns a page of people. Copper REST: POST /people/search.
Annotations the server declares
- title: Search people
- readOnlyHint: true
copper_search_tasksSearch/list tasks.No findings
Why it is in this group
- The name "copper_search_tasks" says "search": a word for reading.
Description, as the server wrote it Search/list tasks. All filters optional; returns a page of tasks. Copper REST: POST /tasks/search.
Annotations the server declares
- title: Search tasks
- readOnlyHint: 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 data4
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- 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.
Looked at Nov 20, 2026, 19:34 UTC, unchanged since Oct 29, 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
- Oct 29, 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: 7 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://copper.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://copper.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.
The server marks "copper_log_activity" destructive (destructiveHint: true), and its name says "log", a word for reading.
What this check looks forMatched text
annotations: {"destructiveHint":true}; The name "copper_log_activity" says "log": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
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: 7 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://copper.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://copper.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.41.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http copper https://copper.usefulapi.io/mcpclaude mcp add --transport http copper https://copper.usefulapi.io/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__copper__copper_get_account",
"mcp__copper__copper_list_users",
"mcp__copper__copper_search_people",
"mcp__copper__copper_get_person",
"mcp__copper__copper_search_companies",
"mcp__copper__copper_get_company",
"mcp__copper__copper_search_opportunities",
"mcp__copper__copper_get_opportunity",
"mcp__copper__copper_search_leads",
"mcp__copper__copper_get_lead",
"mcp__copper__copper_search_tasks",
"mcp__copper__copper_get_task",
"mcp__copper__copper_list_activities",
"mcp__copper__copper_list_activity_types",
"mcp__copper__copper_list_pipelines"
],
"ask": [],
"deny": [
"mcp__copper__copper_create_person",
"mcp__copper__copper_update_person",
"mcp__copper__copper_create_company",
"mcp__copper__copper_create_opportunity",
"mcp__copper__copper_create_lead",
"mcp__copper__copper_create_task",
"mcp__copper__copper_log_activity"
]
}
}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 copper. Review it before you use it.
Capability tags behind 4 rules
- mcp__copper__copper_list_users private-data, untrusted-input
- mcp__copper__copper_search_people private-data
- mcp__copper__copper_get_person private-data
- mcp__copper__copper_list_activities private-data
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/copper/verify?hash=4c139acba4ba2b78d4a6e9ba0dafbd3798e571b83b0d38c7982f404045d4bb99" | jq -e '.changed == false'Pinned hash 4c139acba4ba, 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/copper/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/copper)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.
Copper MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Copper MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 22 tools, 7 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Copper MCP by usefulapi delete data?
- Yes. 7 tools can delete, cancel or revoke something: copper_create_person, copper_update_person, copper_create_company, copper_create_opportunity, copper_create_lead, copper_create_task and 1 more.
Can the Copper 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 Copper MCP by usefulapi have?
- 22 tools: 7 destructive, 15 read. copper_create_person, copper_update_person, copper_create_company, copper_create_opportunity, copper_create_lead, copper_create_task, copper_log_activity, copper_get_account and 14 more.
Does the Copper MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Copper 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 Copper MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.