# Conecto Newsletters (remote · api.conecto.chat)

Newsletters with double opt-in, an archive and click counts. Pay per action.

- Trust score: 62/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.conecto.chat`: 62/100 (this document), [markdown](https://verifymcp.io/servers/chat-conecto-newsletters/mcp-newsletters.md), [page](https://verifymcp.io/servers/chat-conecto-newsletters/mcp-newsletters)

## Channel facts

- Endpoint: `https://api.conecto.chat/mcp/newsletters`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (newsletters_remove_service).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 5717 tokens (~132/item across 43 items; 43 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 57% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 44 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Conecto Newsletters MCP server?

Conecto Newsletters is a hosted endpoint at https://api.conecto.chat/mcp/newsletters, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http chat-conecto-newsletters 'https://api.conecto.chat/mcp/newsletters'
```

### Cursor

```json
{
  "mcpServers": {
    "chat-conecto-newsletters": {
      "url": "https://api.conecto.chat/mcp/newsletters"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "chat-conecto-newsletters": {
      "type": "http",
      "url": "https://api.conecto.chat/mcp/newsletters"
    }
  }
}
```

### Codex

```toml
[mcp_servers.chat-conecto-newsletters]
url = "https://api.conecto.chat/mcp/newsletters"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "chat-conecto-newsletters": {
      "type": "remote",
      "url": "https://api.conecto.chat/mcp/newsletters",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add chat-conecto-newsletters --url 'https://api.conecto.chat/mcp/newsletters' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  chat-conecto-newsletters:
    url: "https://api.conecto.chat/mcp/newsletters"
```

### Netclaw

```json
{
  "McpServers": {
    "chat-conecto-newsletters": {
      "Transport": "http",
      "Url": "https://api.conecto.chat/mcp/newsletters"
    }
  }
}
```

### Vellum

```bash
assistant mcp add chat-conecto-newsletters -t streamable-http -u 'https://api.conecto.chat/mcp/newsletters'
```

### Other

```json
{
  "mcpServers": {
    "chat-conecto-newsletters": {
      "type": "http",
      "url": "https://api.conecto.chat/mcp/newsletters"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-02 (score 61)

First indexed and scored.

## MCP tools (43)

### `newsletters_connect_service` (~419 tokens)

Connect the business's email service

Newsletters go out through the business's own email service, from an address on its own domain: any service that takes mail over SMTP, such as Brevo, Amazon SES, Mailgun, Postmark, SendGrid, Mailchimp Transactional or the web host. Give its SMTP server, login and the from address. Called without password, it answers with a link for the owner, who types the SMTP password or key on a Conecto page, so it never passes through the chat (from_a_terminal does the same from a terminal); account.credential_added says when it is connected. Conecto logs in to check them and keeps the password encrypted, never shown again. Calling it again replaces them, and issues waiting for the service go out on the next round. With test_to, a short email also goes out, which shows the service takes mail from that address. Free. Free.

Input parameters:

- `from_email` (string, required): The address issues come from, on a domain the service lets the business send from, e.g. news@halversoncycle.com.
- `host` (string, required): The SMTP server, e.g. smtp-relay.brevo.com or email-smtp.eu-west-1.amazonaws.com.
- `password` (string): The SMTP password or key (for Brevo an SMTP key, not the account password). Leave it out to get the link instead.
- `per_day` (integer): The service's own daily limit, if it has one (Brevo's free plan: 300). Issues then go out over several days.
- `port` (integer): 587 (STARTTLS) or 465 (SSL/TLS). Port 25 is blocked on Conecto's servers.
- `security` (string): starttls or ssl. Left out: ssl on port 465, starttls otherwise.
- `test_to` (string): Also send a short test email to this address.
- `username` (string, required): The SMTP login (for Brevo the SMTP login, for SendGrid "apikey").

### `newsletters_remove_service` (~42 tokens)

Disconnect the email service

Forget the business's email service and its password. Until another is connected, newsletters take no sign-ups, send no invitations, and issues going out wait. Free.

### `newsletters_create` (~158 tokens)

Create a newsletter

A newsletter people join on its own page (cncto.co/n/<name>) by confirming their address, like Buttondown or listmonk. Issues go out through the business's own email service (connect it first with newsletters_connect_service); every issue carries postal_address (the law in the US and the EU asks for one) and a one-click unsubscribe. Free. Free.

Input parameters:

- `description` (string): One or two lines on its page: what it is and how often it comes.
- `name` (string, required): e.g. "Halverson Ride Notes".
- `postal_address` (string, required): The business's postal address, shown at the foot of every issue.
- `public_archive` (boolean): Show past issues on its page.

### `newsletters_update` (~78 tokens)

Change a newsletter

Rename it, or change its description, postal address or archive. Give only what changes. Free.

Input parameters:

- `description` (string)
- `name` (string)
- `newsletter` (string, required): The newsletter's slug (from newsletters_list) or its exact name.
- `postal_address` (string)
- `public_archive` (boolean)

### `newsletters_list` (~30 tokens)

List newsletters

This account's newsletters with their pages and subscriber counts, and the email service they go out through. Free.

### `newsletters_invite` (~168 tokens)

Invite people to a newsletter

Email each person a request to confirm their subscription: only those who press Confirm ever get an issue. For people who asked to hear from the business. Skips anyone already in, invited in the last day, unsubscribed or undeliverable. At most 20 invitations a day per account. Free: they go out through the business's own email service. Free.

Input parameters:

- `how_they_asked` (string, required): How these people asked to hear from the business, like "they signed up at the counter" or "they asked for it by email". The invitations are checked first: people who never asked are cold outreach, an…
- `newsletter` (string, required): The newsletter's slug (from newsletters_list) or its exact name.
- `people` (array, required)

### `newsletters_subscribers` (~85 tokens)

List subscribers

Who is on a newsletter, newest first: active (confirmed), pending (not yet confirmed), unsubscribed, bounced or complained. Free.

Input parameters:

- `limit` (integer)
- `newsletter` (string, required): The newsletter's slug (from newsletters_list) or its exact name.
- `offset` (integer)
- `query` (string)
- `status` (string)

### `newsletters_remove_subscriber` (~70 tokens)

Remove a subscriber

Delete someone from a newsletter for good, with their history (for example when they ask to be forgotten). To only stop their issues, they unsubscribe themselves. Free.

Input parameters:

- `email` (string, required)
- `newsletter` (string, required): The newsletter's slug (from newsletters_list) or its exact name.

### `newsletters_write_issue` (~99 tokens)

Write an issue

A draft issue in Markdown. Look at it with newsletters_send_test, then send it with newsletters_send_issue. Free.

Input parameters:

- `body` (string, required): Markdown: headings, lists, links, bold, quotes, tables and https images.
- `newsletter` (string, required): The newsletter's slug (from newsletters_list) or its exact name.
- `preheader` (string): The line mail apps show after the subject.
- `subject` (string, required)

### `newsletters_update_issue` (~80 tokens)

Change a draft issue

Change a draft's subject, body or preheader. Give only what changes. Free.

Input parameters:

- `body` (string): Markdown: headings, lists, links, bold, quotes, tables and https images.
- `issue_id` (string, required): The issue_id newsletters_write_issue returned.
- `preheader` (string)
- `subject` (string)

### `newsletters_send_test` (~79 tokens)

Send a test of an issue

Email an issue as subscribers will see it to up to 5 addresses (the owner, a colleague), with "[Test]" before the subject, through the business's own email service. Links are not counted and nothing is numbered. Free.

Input parameters:

- `issue_id` (string, required): The issue_id newsletters_write_issue returned.
- `to` (array, required)

### `newsletters_send_issue` (~135 tokens)

Send an issue

Send a draft to everyone who confirmed, now or at send_at, through the business's own email service. It goes out in batches, within the service's daily limit when one is set; newsletters_get_issue shows how far it got. It is checked first: one that looks like cold outreach isn't sent. Free. Free.

Input parameters:

- `issue_id` (string, required): The issue_id newsletters_write_issue returned.
- `send_at` (string): When, as ISO 8601 with a time zone, e.g. 2026-10-20T09:00:00+02:00. Now if left out.

### `newsletters_cancel_issue` (~44 tokens)

Cancel an issue

Stop a scheduled issue, or one still going out. Whatever went out already stays sent. Free.

Input parameters:

- `issue_id` (string, required): The issue_id newsletters_write_issue returned.

### `newsletters_get_issue` (~64 tokens)

Get an issue

One issue: its text, where it stands (with what holds it up, if anything), and once sent how many it reached, bounced, unsubscribed and clicked, link by link. Free.

Input parameters:

- `issue_id` (string, required): The issue_id newsletters_write_issue returned.

### `newsletters_list_issues` (~47 tokens)

List issues

A newsletter's issues, newest first. Free.

Input parameters:

- `newsletter` (string, required): The newsletter's slug (from newsletters_list) or its exact name.
- `status` (string)

### `account_balance` (~71 tokens)

Check balance

The account balance, how much of it is credit bought (AI visibility and the phone run only on that) and how much free and bonus credit, what running calls are holding, this key's daily budget, the auto-reload state, and how much of this month's free reads and downloads is used. Free.

### `account_get_call` (~50 tokens)

Get a call

One call by id: its status (queued, running, succeeded, failed), cost and result. Use it to poll a background call until it finishes. Free.

Input parameters:

- `call_id` (string, required)

### `account_list_calls` (~52 tokens)

List calls

Recent calls on this account, newest first, optionally only failed or succeeded ones, or one area's. Free.

Input parameters:

- `area` (string)
- `limit` (integer)
- `status` (string)

### `account_refund_topup` (~97 tokens)

Refund a top-up

Refund a top-up paid in the last 24 hours that none of has been used yet: its credit, with the first top-up's bonus, leaves the balance, and the card gets the credit back with its tax. The service fee is kept. Without topup_id, the newest top-up (GET /v1/topups lists them with their ids). Free. Free.

Input parameters:

- `topup_id` (integer)

### `account_set_owner_email` (~72 tokens)

Name the business's owner

When the account was made without the owner's email: send that person a link to confirm they own it. Once they confirm, the owner gets the account's warnings and approval requests, and only the owner raises limits. Nothing changes until they open the link. Free. Free.

Input parameters:

- `email` (string, required)

### `account_owner_link` (~100 tokens)

Get a sign-in link for the owner

A link that signs the business owner into their Conecto page, with no password: the balance, adding credit, auto-reload, limits, what the bots did, people, rentals and keys. page opens it where the owner is needed, like people for a role only the owner gives, or settings for joining by email domain. It works once, within 30 minutes; hand it to the owner. Free.

Input parameters:

- `page` (string)

### `account_dashboard_link` (~148 tokens)

Get a link to an area at a glance

A one-time link to a page showing one area as it is when the page opens, for when the person you work for asks to see it themselves: a recruiter looks at the applicants, a bookkeeper at what is due. Do the work and answer with the area's own tools first; a link never replaces that. When an answer would be a long list they would rather look through, offer a link and make it once they say yes. The page is made from the area's own reads as this key, so it shows only what this key may see. It opens once and keeps for an hour; an unopened link ends after 7 days. Free.

Input parameters:

- `area` (string, required)

### `account_get_limits` (~61 tokens)

Read the limits

The limits a business can ask Conecto to raise (calls a minute, new email addresses a day, phone numbers and more): each one's standard and current value and the most that can be asked for, and the business's requests with their answers. Free.

### `account_request_limit` (~198 tokens)

Ask for a higher limit

Ask Conecto to raise one of the business's limits: which one (or other, saying which), the number it needs, and why, in 40 to 2,000 characters. Conecto reviews it and approves (maybe with less) or declines; the answer comes as the account.limit_request_answered event and by email to the owner, who is also told now. For an account that has topped up; one request per limit at a time, five in 30 days. Free. Free.

Input parameters:

- `amount` (integer, required): The number the business needs, in the limit's unit (5000 calls a minute).
- `limit` (string, required): The limit, as account_get_limits names it, or other.
- `other` (string): With limit other: which limit, like "rows in one table".
- `reason` (string, required): What the business does that needs it, and why the current limit is too low.

### `account_events` (~113 tokens)

Read recent events

What happened in this account that someone outside the bot did, oldest first: applications, bookings, form responses, signatures, replies, emails received, goals reached on the website; and the custom events bots sent with account_emit_event. Kept 30 days. Poll with after = the last event_id you saw. Free.

Input parameters:

- `after` (integer): Only events after this event_id.
- `kinds` (array): Event names or areas ("hiring.*"); all when left out.
- `limit` (integer)

### `account_emit_event` (~197 tokens)

Send an event of your own

Send an event you name, custom.<name> (custom.lead_qualified, custom.order_shipped), to every channel subscribed to it (notify_subscribe with "custom.*" or its name: Slack, Teams, a webhook to Zapier, Make, n8n or the business's own systems) and to account_events, where another team's bot can pick it up. data is any JSON object (up to 10 KB); sent_by is added with this bot's name and team. $0.005 for each channel it goes to; free when no channel is subscribed. Costs $0.005 per channel it goes to; nothing if none are found.

Input parameters:

- `data` (object)
- `kind` (string, required): custom. and a name of lowercase letters, digits, dots, dashes and _.
- `link` (string)
- `text` (string)
- `title` (string, required)

### `account_search` (~116 tokens)

Search everything

One search over what this account holds: what its files say (PDFs, Word, Excel, PowerPoint, text), table rows, help center articles, CRM contacts, companies and deals, emails, tickets, quotes and invoices, book entries, stock items and project tasks. Every word must appear (any case); titles rank first, then the newest. Each result says which tool opens it. Narrow it with areas. Free.

Input parameters:

- `areas` (array)
- `limit` (integer)
- `query` (string, required)

### `account_get_brand` (~29 tokens)

See the business's look

The name, logo, colour and footer line the business's emails and published pages carry. Free.

### `account_set_brand` (~177 tokens)

Set the business's look

The business's name as the sender, its logo (a PNG, JPEG, WebP or GIF from the file store), its colour and a footer line (an address, a legal line), on every email to its customers (bookings, applications, tests, signatures, invoices, newsletters, replies) and on its published pages (forms, booking, careers, newsletters, status, views). Only what you pass changes; an empty string clears it. Mail from Conecto to you keeps Conecto's look. Costs $0.001 per call; nothing if it fails.

Input parameters:

- `colour` (string): Hex, like #1a73e8; empty for none.
- `footer` (string)
- `logo_file_id` (string)
- `remove_logo` (boolean)
- `sender_name` (string)

### `account_list_email_templates` (~69 tokens)

See what the business's emails say

Every email Conecto sends to the business's customers (bookings, applications, interviews, tests, signatures, invoices and quotes, newsletter sign-ups), with when it goes out and its subject, headline and opening words as they are now, and the {variables} each can use. Free.

### `account_set_email_template` (~139 tokens)

Rewrite one of the business's emails

Change an email's subject, headline or opening words in the business's own voice, with {variables} from account_list_email_templates (like {name} or {when}). The facts under them (times, places, amounts, links and buttons) stay as they are. Only what you pass changes; an empty string brings back the original words. Plain text; a blank line starts a new paragraph. Costs $0.001 per call; nothing if it fails.

Input parameters:

- `email` (string, required): Like booking_booked or invoice_sent.
- `headline` (string)
- `opening` (string)
- `subject` (string)

### `account_export_all` (~176 tokens)

Export everything

Everything this account holds, in ZIP files of up to 24 MB saved to its file store: every record of every area as JSON Lines, and the stored files themselves, with a README saying what is where. Credentials are left out. Runs in the background: poll the call with account_get_call; the result has a download link for each part. The parts open only for this key and for the owner's and admins' own keys that neither only read nor only draft. A key of a team other than the company-wide one gets owner_required. Free (EU Data Act). One at a time, three a day; the owner is emailed when an export is made. Free. Runs in the background: the reply has a call_id; poll it with the account_get_call tool or GET /v1/calls/<id>.

### `account_audit_log` (~129 tokens)

Read the audit log

The account's admin and security actions, newest first: keys made and revoked, limits and auto-reload, the owner's sign-ins, connectors, exports, vault reads and writes, credentials set and everything deleted. Ordinary work is in the call log (account_list_calls). verify: true also checks the hash chain, which breaks where an entry was changed or removed. Free.

Input parameters:

- `action` (string): Only actions starting with this, like "key." or "tool.vault_".
- `limit` (integer)
- `since` (string)
- `verify` (boolean)

### `account_save_team` (~561 tokens)

Create or change a team

A department, location or project group of the account, like Support, Finance or the Hamburg shop. Its keys (POST /v1/keys with "team") can only work in its areas, only read when read_only is on, and spend against its budget (monthly_budget_usd per budget_period: a month, a fiscal quarter or year, or a project total): a hard budget refuses the call that would pass it, a soft one only warns. At alert_percent you get the event account.budget_alert and the owner an email, once a period. erp_code is the team's cost center in the company's ERP, for statements. drafts_only makes every write of its keys wait for one of its managers (or the owner), for a new bot that should only draft. mailboxes are the Microsoft 365 or Google mailboxes its keys may act as. You may make a team and narrow one; widening its areas, letting it write, ending drafts only, switching a hard budget to soft, and raising or removing a budget are the owner's, on their account page, when the account has an owner email. The company-wide team holds every key no other team does and is never limited to areas. $0.001. Costs $0.001 per call; nothing if it fails.

Input parameters:

- `alert_percent` (integer)
- `areas` (array|null): The areas its keys may work in (account tools always); null for every area.
- `budget` (string): hard refuses calls past the budget; soft only warns.
- `budget_ends_on` (string|null): The last day of a project budget, like 2026-12-31.
- `budget_period` (string): What the budget is for: a month, a quarter or a year of the account's fiscal calendar, or a project total until budget_ends_on.
- `drafts_only` (boolean): Every write of its keys waits for a person, and they get links that act for whoever opens them as "[redacted]".
- `erp_code` (string|null)
- `mailboxes` (array|null): The Microsoft 365 or Google mailboxes its keys may act as; null for every mailbox the connection lists.
- `monthly_budget_usd` (number|null): null counts the spend without a cap.
- `name` (string, required)
- `new_name` (string): Renames the team; its keys, spend and budget stay with it.
- `read_only` (boolean): Its keys only read, and get links that act for whoever opens them as "[redacted]".
- `sees_sensitive` (boolean): false hides suppliers' bank details and HR notes and contracts from its keys; only the owner turns it on.

### `account_list_teams` (~82 tokens)

List teams

The account's teams, the company-wide one first: each with its areas, whether it only reads, its budget (hard or soft, and its period) and alert line, this period's spend, its ERP code, whether it is paused, its keys, and its people with who manages it. A person's own assistant works within their teams. Free.

### `account_pause_team` (~69 tokens)

Pause a team

Stops every key of a team at once, this one too if it is the team's: their calls are refused until the owner starts the team again on their account page. For a bot that misbehaves or a team that spends too fast. Free. Free.

Input parameters:

- `team` (string, required)

### `account_assign_team` (~166 tokens)

Give something to a team

Move a form, a meeting type, a job, an inbox, a phone number, a newsletter, the website chat, a rental, a pipeline, a table or a website to a team. What happens through it is charged to that team from now on (a form's responses, a number's calls, an inbox's tickets), and its rental moves with it. Something a bot makes already belongs to the bot's team. Only a key of the company-wide team without limits moves things between teams. $0.001. Costs $0.001 per call; nothing if it fails.

Input parameters:

- `id` (string): Its id, slug, name, address or number; not needed for the chat.
- `kind` (string, required)
- `team` (string, required)

### `account_add_approval_rule` (~394 tokens)

Hold a tool for approval

Make a tool wait for a person: every call of it, those whose argument is over a number (like invoices_create_credit_note when amount is over 500), or those whose argument is one of some values (like connect_call when method is POST, PUT, PATCH or DELETE). A held call answers approval_required with an approval_id and asks the approver; when they approve, call again with the same arguments, once (a call no person answers for adds the approval: header X-Conecto-Approval, or _meta.approvalId over MCP). The approver is an email, a saved channel, or a team (its managers, or everyone in it); each approver gets a link of their own, and the person whose call it is never approves it. With two_people_over, calls whose argument is over it need two people. Bills like Xero's bill approval: purchasing_create_bill with argument total holds bills over an amount, tax included; a rule on purchasing_pay_bill also holds batches with such a payment. Removing a rule is the owner's, on their account page, when the account has an owner email. $0.001. Costs $0.001 per call; nothing if it fails.

Input parameters:

- `approver_channel` (string): A saved notify channel.
- `approver_email` (string)
- `approver_team` (string): A team (account_list_teams).
- `approvers` (string): Who in approver_team approves.
- `argument` (string): An argument of the tool (or total, for purchasing_create_bill).
- `over` (number): Calls with argument over this are held.
- `tool` (string, required)
- `two_people_over` (number): Calls whose argument is over this need two people; higher than over.
- `values` (array): Calls with argument equal to one of these (any case) are held.

### `account_list_approval_rules` (~29 tokens)

List approval rules

The tools that wait for a person's approval, with their thresholds and approvers. Free.

### `account_find_person` (~148 tokens)

Find a person's data

Every record this account holds about one person, by their email address or phone number, across every area: CRM, chats, emails, tickets, forms, bookings, calls, applications, invoices, orders, newsletters, HR and the call log, with their chats and CRM history. For a person who asks what the business keeps about them (GDPR Art. 15). Shows each kind with its count and ids; account_export_person gives them a copy, account_erase_person erases what may go. Free.

Input parameters:

- `email` (string): The person's email address.
- `phone` (string): Their phone number in international format, like +1 503 555 0145.

### `account_export_person` (~170 tokens)

Export a person's data

Everything account_find_person finds about one person in one ZIP in the file store: their records as JSON Lines (credentials left out) and the files those records point to, like a CV. Give the person the download link when they ask for a copy of their data (GDPR Art. 15 and 20), once you know it is them. The ZIP opens only for this key and for the owner's and admins' own keys that neither only read nor only draft. A key of a team other than the company-wide one gets owner_required: pass the request to the owner. Free; 20 a day. Free.

Input parameters:

- `email` (string): The person's email address.
- `phone` (string): Their phone number in international format, like +1 503 555 0145.

### `account_erase_person` (~278 tokens)

Erase a person's data

Erases one person across every area when they ask (GDPR Art. 17), once you know it is them (they wrote from that address, or confirmed it). Their CRM contact, chat visitor, past meetings and calls are anonymised, so deals stay without them, and a meeting they were only a guest at drops them; their chats, CRM history, form and routing form answers, job applications with the CV, newsletter subscriptions and events are deleted, and the call log's contents that name them are cleared. Kept, each with its reason in the result: accounting records, employment records, signed documents, the audit log, the account's own settings, upcoming meetings, and emails and tickets (outreach emails and replies too) unless correspondence is true. Their address goes on the suppression lists, so it is never mailed again: outreach campaigns stop for them at once. Can't be undone; the owner is emailed. A key of a team other than the company-wide one gets owner_required: pass the request to the owner. Free. Free.

Input parameters:

- `correspondence` (boolean): Also delete their emails and tickets, when no law requires keeping them.
- `email` (string): The person's email address.
- `phone` (string): Their phone number in international format, like +1 503 555 0145.

### `account_data_locations` (~113 tokens)

See where the data is

Where each area's data is stored and processed: the company that runs each place, the country or region, and what it holds. Every area keeps its records in the database and runs on Conecto's servers; some also use a service named here (email, phone, PDFs, search). For the business's records of processing and its transfer assessments (GDPR Art. 30 and 44). Free.

Input parameters:

- `areas` (array): Areas to show, like ["email", "phone"]; all when left out.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/chat-conecto-newsletters/mcp-newsletters#diagnostics

## Score history

- 2026-11-05: 62
- 2026-11-04: 62
- 2026-11-03: 61
- 2026-11-02: 61

## Common questions

### What is the Conecto Newsletters MCP server?

Conecto Newsletters is an MCP server listed in the public MCP registry as chat.conecto/newsletters. Newsletters with double opt-in, an archive and click counts. Pay per action. This page covers its hosted endpoint (https://api.conecto.chat/mcp/newsletters).

### Is the Conecto Newsletters MCP server safe to use?

Conecto Newsletters scores 62 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Conecto Newsletters MCP server expose?

Conecto Newsletters exposes 43 tools: newsletters_connect_service, newsletters_remove_service, newsletters_create, newsletters_update, newsletters_list, and 38 more. Their descriptions and schemas cost roughly 5,602 tokens of context every time the server is loaded.

### Does the Conecto Newsletters MCP server require authentication?

No. We connected to Conecto Newsletters without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Conecto Newsletters MCP server still maintained?

Conecto Newsletters is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Conecto Newsletters MCP server?

VerifyMCP ran 13 checks on Conecto Newsletters, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.conecto.chat/mcp/newsletters
- Authorisation metadata: https://api.conecto.chat/.well-known/oauth-protected-resource/mcp/newsletters
- Website: https://conecto.chat/tools/newsletters
- Changelog RSS feed: https://verifymcp.io/servers/chat-conecto-newsletters/mcp-newsletters.xml
- Changelog JSON feed: https://verifymcp.io/servers/chat-conecto-newsletters/mcp-newsletters/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/chat-conecto-newsletters/mcp-newsletters.json
- HTML version of this page: https://verifymcp.io/servers/chat-conecto-newsletters/mcp-newsletters