Servidor MCP de Cooper Email

• Nome no registrocom.cooperemail/cooper-emailverificado no registro MCP

O nome no registro fica sob cooperemail.com. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.

• Estadorespondeverificado em 2026-10-27
• Ferramentas97
• O servidor se chamacooper-email
• Versão do servidor1.11.0
• Versão do protocolo2025-03-26

Em 2026-10-27 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 113 ms.

• Ainda não avaliamos se as ferramentas fazem o trabalho do produto.
• Verificado em 1 dos 7 dias necessários para julgar a confiabilidade.

Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.

• Nota INITE MCPdepois de uma semanaa nota precisa de 7 verificações diárias: 1 até agora
• Respondeumedindo1 das 7 verificações diárias necessárias para mostrar a porcentagem
• Mediana da primeira resposta417 ms
• Espaço no contexto do agente≈ 35.274 tokensas definições de todas as ferramentas (97), que o agente carrega a cada turno
• Definições das ferramentasA · 98 de 100
• Resultados tipados0 de 97 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez

• Parâmetros sem descrição: em 13 de 97

Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (25%), se faz o trabalho do produto (25%), definições (20%), contexto (10%), uso (10%) e a facilidade de conectar (10%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e números →

• cooper_onboard

  Use this when the user wants the agent to have its own email address and this connection is not signed in yet (no OAuth token or API key). No auth needed. Creates a Cooper account, one inbox <username>@cooperemail.com, and an API key…

• cooper_create_inbox

  Use this when the signed-in account needs an additional email address (for example one per agent, project, or customer). Requires auth. Inputs: username (optional; 1–32 characters; becomes <username>@cooperemail.com; omit it and Cooper…

• cooper_create_inboxes

  Use this when the signed-in account needs several email addresses at once, or addresses that should disappear after a deadline (one inbox per signup, trial, or job). Requires auth. Inputs: count (required; how many inboxes, capped per…

• cooper_list_inboxes

  Use this when you need to know which inboxes exist on the signed-in account, for example to pick an inbox_id before sending or reading mail, or to tell the user their address. Read-only; requires auth. Inputs: status (optional; active or…

• cooper_send_message

  Use this when the user asks the agent to send an email from its Cooper address. Requires auth. Delivers real email on the public Internet and stores a copy. Inputs: inbox_id (required; inbox id, username, or email), to (required; array of…

• cooper_list_messages

  Use this when you need to check an inbox for new or recent mail (sent and received), for example after sending a message and waiting for a reply. Read-only; requires auth. Inputs: inbox_id (optional; inbox id, username, or email — omit to…

• cooper_get_message

  Use this when you need the full content of one message, typically an id from cooper_list_messages or cooper_search. Read-only; requires auth. Inputs: inbox_id (required; inbox id, username, or email), message_id (required). Returns the…

• cooper_search

  Use this when you need to find mail by keyword, sender, recipient, or subject across the account, or inside one inbox. Read-only; requires auth. Inputs: q (required; every word must match subject, body text, from, or to), limit (optional…

• cooper_search_messages

  Use this when you need to find mail inside one inbox by keyword, sender, recipient, or subject, and you want the matching words highlighted. Read-only; requires auth. Inputs: inbox_id (required; inbox id, username, or email), q (required…

• cooper_inject_inbound

  Use this only for testing: when you need to simulate an email arriving in a Cooper inbox without sending real mail (for example to try a webhook or task flow end to end). Requires auth. Stores the message as received mail and fires…

• cooper_register_webhook

  Use this when the agent or app should be notified immediately (HTTP POST) when mail arrives instead of polling cooper_list_messages. Requires auth. Inputs: url (required; public http or https URL; localhost and private addresses are…

• cooper_enable_instant_replies

  Use this when an owner message should wake the agent within seconds. Idempotent. Requires auth. Inputs: inbox_id (required), url (public http or https URL, required unless enabled is false), headers (optional; up to 5 extra headers named…

• cooper_billing_status

  Use this when you need to know the account's plan, how much of its monthly quota is used, or why a send or inbox create returned 402. Read-only; requires auth; no inputs. Returns {plan, plan_name, status, usage:{period, sends, inboxes}…

• cooper_upgrade_link

  Use this when the human wants to upgrade, or a limit was hit and they agree to pay. Requires auth. Creates a Stripe Checkout session; no charge happens until the human completes checkout in their browser. Inputs: plan (required; starter…

• cooper_add_owner

  Use this when a human should receive the agent's progress updates by email and be able to reply with instructions. Requires auth. Sends that person one confirmation email with a link and code; they receive nothing else until they confirm…

• cooper_list_owners

  Use this when you need to check who the human owners of an inbox are and whether they have confirmed, before relying on cooper_notify_owner. Read-only; requires auth. Inputs: inbox_id (required). Returns {data:[{id, email, status…

• cooper_notify_owner

  Use this when the agent should tell its human owner(s) about progress, completion, a blocker, or a question by email. Requires auth. Sends a status email to every verified owner of the inbox (daily-digest owners get it in the next…

• cooper_get_tasks

  Use this when you are waiting for a human's instructions or answer by email: it lists tasks created when a verified owner or allowlisted sender emails the inbox and the mail passes DMARC (or DKIM aligned with From). Read-only; requires…

• cooper_reply_task

  Use this when you have an answer or result for a task from cooper_get_tasks and want to reply to the human in the same email thread. Requires auth. Sends a real email to the task's sender. Inputs: task_id (required), text (required; the…

• cooper_add_domain

  Use this when the user wants mail on their own hostname and the account is on Starter or Pro. Requires auth. One call returns the SPF, DKIM, DMARC, and MX records to publish, plus a verify TXT. Inputs: domain (required hostname, such as…

• cooper_create_workspace

  Use this when the signed-in parent account should give a project or another agent its own API key and a fixed inbox quota. Requires auth. Inputs: name (required; 1–64 characters), inbox_quota (required integer; how many inboxes that…

• cooper_list_workspaces

  Use this when you need the sub-accounts created by the signed-in parent, including each inbox quota and how many inboxes are in use. Read-only; requires auth; no inputs. Returns {data:[{id, name, inbox_quota, account_id, api_key_prefix…

• cooper_get_workspace

  Use this when you need one sub-account created by the signed-in parent, including its inbox quota and how many inboxes are in use. Read-only; requires auth. Inputs: workspace_id (required). Returns {id, name, inbox_quota, inboxes_used…

• cooper_update_workspace

  Use this when a parent should rename a sub-account or change how many live inboxes it may hold. Requires auth. Inputs: workspace_id (required), name (optional; 1–64 characters), inbox_quota (optional integer, at least 1). Returns the…

• cooper_delete_workspace

  Use this when a parent should remove a sub-account, its API key, and its mail. Requires auth. Destructive. Inputs: workspace_id (required), delete_inboxes (optional boolean). Returns {id, deleted:true, inboxes_deleted}. When the workspace…

• cooper_delete_inbox

  Use this when an inbox should be removed so its slot is free on the plan and on a workspace inbox quota. Requires auth. Deletes that inbox and its messages. Inputs: inbox_id (required; inbox id, username, or email). Returns {id…

• cooper_update_inbox

  Use this when an inbox should stop sending and accepting new mail without deleting the address, threads, or history (for example while a human reviews it or during an incident), when it should start again, when you need to set its display…

• cooper_update_message

  Use this when you need to change labels on a stored message, including marking it read. Requires auth. Works on a paused inbox, because this is triage and not a send. Inputs: inbox_id (required; inbox id, username, or email), message_id…

• cooper_update_messages

  Use this when several stored messages should gain or lose the same labels, including marking a batch read. Requires auth. Works on a paused inbox, because this is triage and not a send. Inputs: inbox_id (required; inbox id, username, or…

• cooper_list_domains

  Use this when you need the custom domains on the signed-in account, including DNS status. Read-only; requires auth; no inputs. Returns {object:"list", data:[{id, domain, status, status_detail, mail, records, warnings, dns}]}. Each record…

• cooper_verify_domain

  Use this when DNS for a custom domain may have been published and you should check it now instead of waiting for the daily cron. Requires auth. Inputs: domain_id (required; the dom_… id from cooper_add_domain or cooper_list_domains). Runs…

• cooper_reply_message

  Use this when you need to answer a message already in a Cooper inbox, with recipients and threading filled in for you. Requires auth. Sends real email and stores the copy on the same thread. Inputs: inbox_id (required; inbox id, username…

• cooper_forward_message

  Use this when you need to forward a stored message to someone else, including a forwarded header block and the original attachments, on a new thread. Requires auth. Sends real email. Inputs: inbox_id (required; inbox id, username, or…

• cooper_wait_for_message

  Use this when you are waiting for a reply or a verification code and you have no public URL for a webhook. Read-only; requires auth. Inputs: inbox_id (required; inbox id, username, or email), after (optional cursor or ISO-8601 timestamp…

• cooper_list_events

  Use this when you need the recent event log for this account (message.received, message.held, message.sent, message.blocked, message.bounced, message.complained, task.received, owner.reply, domain.verified, draft.created, draft.approved…

• cooper_list_threads

  Use this when you need whole conversations instead of individual messages, for example to see who is in a thread and when the last reply arrived. Read-only; requires auth. Inputs: inbox_id (optional; inbox id, username, or email — omit to…

• cooper_get_thread

  Use this when you need every message in one conversation, oldest first, including extracted_text. Read-only; requires auth. Inputs: inbox_id (required; inbox id, username, or email), thread_id (required, thr_…), limit (optional, default…

• cooper_search_threads

  Use this when you need the conversations that contain a keyword, sender, recipient, or subject, instead of each matching message. Read-only; requires auth. Inputs: inbox_id (required; inbox id, username, or email), q (required; every word…

• cooper_delete_thread

  Use this when a whole conversation should be removed permanently. Requires auth. Deletes every message in the thread, plus attachment bytes, search rows, the assignment, and the folder row. Owner tasks and updates are left in place. This…

• cooper_update_thread

  Use this when every message in a conversation should gain or lose the same labels, including marking the thread read, or when the thread should move to inbox, archive, spam, or trash. Requires auth. Works on a paused inbox. Inputs…

• cooper_move_threads

  Use this when several conversations should move to the same folder in one call, for example archiving finished work or trashing a batch. Requires auth. Same permission as updating thread labels. Inputs: inbox_id (required; inbox id…

• cooper_assign_thread

  Use this when a triage agent should hand a thread to a named assignee, or a worker should take an exclusive claim so another worker does not reply to the same thread. Requires auth. Same permission as updating thread labels. Inputs…

• cooper_unassign_thread

  Use this when the assignee is done with a thread, or a worker should release its claim. Requires auth. Same permission as updating thread labels. Inputs: inbox_id (required; inbox id, username, or email), thread_id (required), assignee…

• cooper_list_list_entries

  Use this when you need the addresses on an allow or block list. Read-only; requires auth. Inputs: direction (required; send, receive, or reply), type (required; allow or block), inbox_id (optional; inbox id, username, or email; omit for…

• cooper_get_list_entry

  Use this when you need one address or domain on an allow or block list. Read-only; requires auth. Inputs: direction (required; send, receive, or reply), type (required; allow or block), entry (required; email or domain), inbox_id…

• cooper_create_list_entry

  Use this when an agent should only mail approved recipients, or should ignore unwanted senders. Requires auth. Inputs: direction (required; send, receive, or reply), type (required; allow or block), entry (required; email or domain)…

• cooper_delete_list_entry

  Use this when an address or domain should leave an allow or block list. Requires auth. Deletes that one entry. Inputs: direction (required; send, receive, or reply), type (required; allow or block), entry (required; email or domain)…

• cooper_get_inbox

  Use this when you need one inbox's address, display name, metadata, status, client_id, screening, or send_mode and you already have its id, username, or email. Read-only; requires auth. Inputs: inbox_id (required; inbox id, username, or…

• cooper_confirm_owner

  Use this when a human received the 6-digit confirmation code and you need to mark that owner verified so they can receive updates and open tasks. Requires auth. Inputs: inbox_id (required; inbox id, username, or email), owner_id…

• cooper_whoami

  Use this when you need to see which Cooper account this connection is using and whether the API key is limited to one inbox or a permission list. Requires auth. Optional input lifecycle_emails is on or off and sets whether this account…

• cooper_list_webhooks

  Use this when you need the webhooks on this account, including whether each one is enabled and which inboxes it matches. Read-only; requires auth. No inputs. Returns {object:"list", data:[{id, url, events, inbox_id, inbox_ids, client_id…

• cooper_update_webhook

  Use this when a webhook URL, event list, inbox filter, or enabled flag should change. Requires auth. Inputs: webhook_id (required), url (optional http(s) URL), events (optional array), enabled (optional boolean; true re-enables and resets…

• cooper_delete_webhook

  Use this when a webhook should stop receiving events and be removed. Requires auth. Inputs: webhook_id (required). Returns {id, deleted:true}. This removes the hook. Fails with 404 webhook_not_found when the id is missing or belongs to…

• cooper_rotate_webhook_secret

  Use this when a webhook signing secret should change without breaking receivers that still check the old secret. Requires auth. Inputs: webhook_id (required). Mints a new secret (whsec_…), stores it as the current secret, and keeps the…

• cooper_test_webhook

  Use this when you need to confirm a webhook URL accepts a signed POST right now. Requires auth. Inputs: webhook_id (required). Sends {type:"webhook.test", data:{webhook_id}} and waits for the response. Returns {delivery:{id, status…

• cooper_list_suppressions

  Use this when you need the addresses this account will not email after a permanent bounce, a complaint, or a manual add. Read-only; requires auth. Inputs: none. Returns {object:"list", data:[{object:"suppression", address, reason…

• cooper_delete_suppression

  Use this when an address should receive mail again after it was suppressed for a bounce, a complaint, or a manual add. Requires auth. Deletes that one account-wide row. Inputs: address (required; email). Returns the suppression with…

• cooper_release_message

  Use this when inbound screening held a message (label held) and a person has decided it should be delivered to the agent. Requires auth. Removes the held label, then fires message.received and creates a task when the sender is a verified…

• cooper_get_attachment

  Use this when you need the text of one attachment, or its bytes as base64. Read-only; requires auth. Inputs: inbox_id (required; inbox id, username, or email), message_id (required), attachment_id (required), format (optional; text or…

• cooper_get_metrics

  Use this when you need counts of mail over time, current usage, or bounce and complaint rates for this account. Read-only; requires auth and message_read. Inputs: kind (required; events, usage, or rates), inbox_id (optional; inbox id…

As primeiras 60 de 97, na ordem do servidor.