copper

Tools

22 tools: 15 read-only, 0 change data, 7 high risk (delete, pay, send or run code).

No tool name points to sending messages.

read-only

Only reads or looks things up. Safe for an agent to call on its own.

changes data

Creates, edits or sends something. Worth a person's approval the first time.

high risk

Can delete, pay, send on your behalf or run code. Hard or impossible to undo.

Connecting costs an agent about 5,772 tokens of tool definitions and a 558 ms handshake.

• high riskcopper_create_personCreate a new person (contact). Copper REST: POST /people.
• high riskcopper_update_personUpdate fields on an existing person. Only provided fields are changed. Copper REST: PUT /people/{id}.
• high riskcopper_create_companyCreate a new company. Copper REST: POST /companies.
• high riskcopper_create_opportunityCreate a new opportunity (deal). `name` and `primary_contact_id` are required by Copper. Copper REST: POST /opportunities.
• high riskcopper_create_leadCreate a new lead. Copper REST: POST /leads.
• high riskcopper_create_taskCreate a new task. Copper REST: POST /tasks.
• high riskcopper_log_activityLog 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.
• read-onlycopper_get_accountGet details of the authenticated Copper account. Copper REST: GET /account.
• read-onlycopper_list_usersList users in the Copper account (id, name, email) - useful for resolving assignee ids. Copper REST: POST /users/search.
• read-onlycopper_search_peopleSearch/list people (contacts). All filters optional; returns a page of people. Copper REST: POST /people/search.
• read-onlycopper_get_personGet a single person (contact) by id. Copper REST: GET /people/{id}.
• read-onlycopper_search_companiesSearch/list companies. All filters optional; returns a page of companies. Copper REST: POST /companies/search.
• read-onlycopper_get_companyGet a single company by id. Copper REST: GET /companies/{id}.
• read-onlycopper_search_opportunitiesSearch/list opportunities (deals). All filters optional; returns a page of opportunities. Copper REST: POST /opportunities/search.
• read-onlycopper_get_opportunityGet a single opportunity (deal) by id. Copper REST: GET /opportunities/{id}.
• read-onlycopper_search_leadsSearch/list leads. All filters optional; returns a page of leads. Copper REST: POST /leads/search.
• read-onlycopper_get_leadGet a single lead by id. Copper REST: GET /leads/{id}.
• read-onlycopper_search_tasksSearch/list tasks. All filters optional; returns a page of tasks. Copper REST: POST /tasks/search.
• read-onlycopper_get_taskGet a single task by id. Copper REST: GET /tasks/{id}.
• read-onlycopper_list_activitiesList activities (notes, calls, meetings, system events) attached to a record. Copper REST: POST /activities/search.
• read-onlycopper_list_activity_typesList the account's activity types (user + system), needed to log an activity. Copper REST: GET /activity_types.
• read-onlycopper_list_pipelinesList sales pipelines and their stages (ids needed to place opportunities). Copper REST: GET /pipelines.

Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.

Status

Newest check: answered with tools, from the daily check, 2026-10-04, 558 ms.

From one check a day over the last 1 day. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.

Last 30 days

2026-09-052026-10-04

answered with toolssign-in or payment askednot answeringnot checked

Compare: the most reliable servers in CRM and sales, ranked by days answering.

Badge

Live: status, days reachable, the tokens its tool list costs an agent. For a README:

[![7Maps](https://7it.co.il/7maps/badge/copper.usefulapi.io/mcp.svg)](https://7it.co.il/7maps/s/copper.usefulapi.io/mcp)

Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).

Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=copper.usefulapi.io%2Fmcp (add the same &style= for another style).

Own this server? Verify that it is yours.

Status widget

A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.

Script (renders where it is placed, in its own shadow DOM):

<script src="https://7it.co.il/7maps/widget/copper.usefulapi.io/mcp.js" async></script>

Or an iframe:

<iframe src="https://7it.co.il/7maps/widget/copper.usefulapi.io/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>

The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=copper.usefulapi.io%2Fmcp.

Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.

For AI agents

Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.