MCP server · registry snapshot 2026-11-03 · last tested 2026-11-03

io.usefulapi/emailchef

Emailchef MCP by usefulapi — the publisher's title

by usefulapi.io · domain (the registry's namespace rule)repository owner on GitHub: m190 (personal account)Source ↗Website ↗

Read lists, contacts, campaign stats; add contacts; draft, schedule and send campaigns and SMS. — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-11-03version 1.4.0JavaScriptstreamable HTTP43 tools

Summary

io.usefulapi/emailchef is a remote MCP server listed in the official MCP registry at version 1.4.0, under the namespace of the domain usefulapi.io. Its linked repository is github.com/m190/usefulapi-mcp; GitHub reports its owner as m190, a personal account. On 2026-11-03 ProtocolProbe connected to it in read-only mode and read its inventory: 43 tools, 0 resources and 6 prompts.

Record checks

4 of 5 record checks met · 4 do not apply

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
not met: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 1 star (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Your own values: none declared (not a guarantee)
Sign-in: none needed to open a session
Repository: public
Tools: 43
Last tested: 2026-11-03

Tool list size

14,650 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (43 tools). Counted with Anthropic's token counter on 2026-11-03, from the tool list we read on 2026-11-03. Median across 25,738 counted servers: 2,858 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-03 (emailchef.usefulapi.io), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.4.0).

Add to your client

Observed fact

This server accepted a session without any credential and lists 18 tools whose name or declaration suggests they change data (emailchef_create_list, emailchef_update_list, emailchef_create_contact, emailchef_update_contact, emailchef_unsubscribe_contact and 13 more). That is our reading of the names; we did not call them. Source: our connection, 2026-11-03.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-11-03

Mode

read-only (no tool calls)

Latest version

1.4.0, published 2026-11-03 (registry, as of the 2026-11-03 snapshot)

First listed version

2026-10-31 (earliest version still in the registry; older removed versions would be earlier)

Version history

6 versions listed, 2026-10-31 to 2026-11-03; 6 in the 90 days before the 2026-11-03 snapshot.

Most recent 6 versions

1.4.0 · 2026-11-03
1.3.1 · 2026-11-03
1.3.0 · 2026-11-02
1.2.0 · 2026-10-31
1.1.0 · 2026-10-31
1.0.0 · 2026-10-31

(versions still listed in the registry only)

Registry data

snapshot 2026-11-03

Package and repository

checked 2026-11-03

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 1.3.0 (published 2026-11-02) → 1.4.0 (published 2026-11-03), between the registry lists of 2026-11-02 and 2026-11-03.

The publisher published no GitHub release note for this version: its repository publishes no GitHub releases.

Source: the official MCP Registry list on 2026-11-02 and on 2026-11-03; release notes from the GitHub Releases API, checked 2026-11-03.

What it is

What does this server offer?

Observed inventory

43tools

0resources

6prompts

None of its 43 tools are described as changing anything. For 43 the reading was uncertain, so no mark is shown.

emailchef_get_account
“The Emailchef account this API key belongs to: id, email, language, status, subscriber total, bounces and complaints.”
Publisher declares: read-only yes · destructive no · open-world yes
Takes no inputs.
emailchef_get_subscription
“The account's current Emailchef plan: plan name, plan expiry, contact and send limits, credits left, active/expired flags.”
Publisher declares: read-only yes · destructive no · open-world yes
Takes no inputs.
emailchef_list_senders
“List the sender identities (name, email, verification status, postal address).”
Publisher declares: read-only yes · destructive no · open-world yes
Takes no inputs.
emailchef_list_timezones
“List Emailchef's timezones (id, name, fixed UTC offset).”
Publisher declares: read-only yes · destructive no · open-world yes
Takes no inputs.
emailchef_list_lists
“List the contact lists with id, name, and counts of active, unsubscribed and bounced contacts and segments.”
Publisher declares: read-only yes · destructive no · open-world yes
4 inputs
- order_bystring“Sort by creation date (default) or name.”
- orderstring“Sort direction (default desc).”
- limitinteger“Results per page, 1-100 (default 25).”
- offsetinteger“Rows to skip (default 0).”
emailchef_get_list
“One contact list: name, description, default sender, creation date.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- list_idstring or integerrequired“Numeric id (as returned by the list tools).”
emailchef_get_list_stats
“Daily growth of a list over a date range: total contacts per day and the daily delta.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 1 required
- list_idstring or integerrequired“Numeric id (as returned by the list tools).”
- start_datestring“First day, yyyy-mm-dd.”
- end_datestring“Last day, yyyy-mm-dd.”
emailchef_get_list_contact_counts
“How many contacts a list has by state: active, unsubscribed, bounced, reported.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- list_idstring or integerrequired“Numeric id (as returned by the list tools).”
emailchef_create_list
“WRITE: create a new, empty contact list.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
2 inputs, 1 required
- namestringrequired“List name.”
- descriptionstring“List description.”
emailchef_update_list
“WRITE: rename a contact list and/or change its description.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
3 inputs, 1 required
- list_idstring or integerrequired“Numeric id (as returned by the list tools).”
- namestring“New list name.”
- descriptionstring“New description.”
emailchef_list_contacts
“List the contacts of one list (id, email, name, added by, subscription date), optionally by state.”
Publisher declares: read-only yes · destructive no · open-world yes
6 inputs, 1 required
- list_idstring or integerrequired“Numeric id (as returned by the list tools).”
- statusstring“Only contacts in this state (default: all).”
- order_bystring“Sort field (default subscription date).”
- orderstring“Sort direction (default desc).”
- limitinteger“Results per page, 1-100 (default 25).”
- offsetinteger“Rows to skip (default 0).”
emailchef_get_contact
“One contact in one list: status, email, name, IP, how it was added, when, and its custom field values.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs, 2 required
- list_idstring or integerrequired“Numeric id (as returned by the list tools).”
- contact_idstring or integerrequired“Numeric id (as returned by the list tools).”

Show 31 more tools

emailchef_create_contact
“WRITE: add a contact (email, name, custom fields) to a list.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
6 inputs, 2 required
- list_idstring or integerrequired“Numeric id (as returned by the list tools).”
- emailstringrequired
- first_namestring
- last_namestring
- statusstring“Initial state (default: the account's default, normally ACTIVE).”
- custom_fieldsobject“Custom field values keyed by the field's place_holder (see emailchef_list_custom_fields): a string, or true/false for boolean fields.”
emailchef_update_contact
“WRITE: change a contact's name, state or custom fields in one list.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
6 inputs, 2 required
- list_idstring or integerrequired“Numeric id (as returned by the list tools).”
- contact_idstring or integerrequired“Numeric id (as returned by the list tools).”
- first_namestring
- last_namestring
- statusstring
- custom_fieldsobject“Custom field values keyed by the field's place_holder (see emailchef_list_custom_fields): a string, or true/false for boolean fields.”
emailchef_unsubscribe_contact
“WRITE: unsubscribe one contact from one list (it stops receiving that list's email).”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
2 inputs, 2 required
- list_idstring or integerrequired“Numeric id (as returned by the list tools).”
- contact_idstring or integerrequired“Numeric id (as returned by the list tools).”
emailchef_import_contacts
“WRITE: bulk-add or update up to 500 contacts in a list in one call (an existing email is updated).”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
2 inputs, 2 required
- list_idstring or integerrequired“Numeric id (as returned by the list tools).”
- contactsarrayrequired“Contacts to import, each keyed by placeholder.”
emailchef_list_import_tasks
“List contact import tasks: list, status (DISPATCHED, COMPLETE, FAILED), progress, imported/updated/failed counts.”
Publisher declares: read-only yes · destructive no · open-world yes
Takes no inputs.
emailchef_get_import_task
“One import task: status, progress, imported/updated/failed counts and any error message.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- task_idstring or integerrequired“Numeric id (as returned by the list tools).”
emailchef_list_predefined_fields
“The built-in contact fields (email, first name, ...) with their placeholders.”
Publisher declares: read-only yes · destructive no · open-world yes
Takes no inputs.
emailchef_list_custom_fields
“The custom contact fields of a list: name, data type, placeholder (the key used when writing contacts), options.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- list_idstring or integerrequired“Numeric id (as returned by the list tools).”
emailchef_list_segments
“List the saved segments of a list with how many contacts match each.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 1 required
- list_idstring or integerrequired“Numeric id (as returned by the list tools).”
- limitinteger“Results per page, 1-100 (default 25).”
- offsetinteger“Rows to skip (default 0).”
emailchef_get_segment
“One segment with its logic and condition groups.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs, 2 required
- list_idstring or integerrequired“Numeric id (as returned by the list tools).”
- segment_idstring or integerrequired“Numeric id (as returned by the list tools).”
emailchef_list_blocked
“List the account's blocklist (emails that never receive email): address and reason (MANUAL, UNSUBSCRIBED, COMPLAINT).”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs
- searchstring“Only addresses containing this text.”
- limitinteger“Results per page, 1-100 (default 25).”
- offsetinteger“Rows to skip (default 0).”
emailchef_block_emails
“WRITE: add up to 100 addresses to the account blocklist so they never receive email from any list.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
1 input, 1 required
- emailsarrayrequired“Addresses to block.”
emailchef_unblock_email
“WRITE: remove one address from the account blocklist so it can receive email again.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
1 input, 1 required
- emailstringrequired
emailchef_get_campaign_counts
“How many campaigns the account has by state: drafts, sent, scheduled, archived, failed.”
Publisher declares: read-only yes · destructive no · open-world yes
Takes no inputs.
emailchef_list_campaigns
“List email campaigns with state, recipients, delivered, unique opens and unique clicks.”
Publisher declares: read-only yes · destructive no · open-world yes
6 inputs
- statusstring“Only campaigns in this state (default: SENT and ARCHIVED).”
- searchstring“Only campaigns whose name contains this text.”
- order_bystring“Sort by date (default) or name.”
- orderstring“Sort direction (default desc).”
- limitinteger“Results per page, 1-100 (default 25).”
- offsetinteger“Rows to skip (default 0).”
emailchef_get_campaign
“One campaign: name, subject, HTML and text body, sender, reply-to, state, schedule, recipient lists/segments and cached sent/open/click counts.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- campaign_idstring or integerrequired“Numeric id (as returned by the list tools).”
emailchef_get_campaign_links
“The links contained in a campaign (id, name, URL).”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- campaign_idstring or integerrequired“Numeric id (as returned by the list tools).”
emailchef_list_campaign_engagement
“Per-contact engagement for a sent campaign: who opened, clicked, was delivered, did not open, unsubscribed, complained, or was sent to, with counts and first/last event time.”
Publisher declares: read-only yes · destructive no · open-world yes
5 inputs, 2 required
- campaign_idstring or integerrequired“Numeric id (as returned by the list tools).”
- eventstringrequired“Which engagement slice to list.”
- searchstring“Only contacts whose email or name contains this text.”
- limitinteger“Results per page, 1-100 (default 25).”
- offsetinteger“Rows to skip (default 0).”
emailchef_create_campaign
“WRITE: create a new campaign as a DRAFT (nothing is sent).”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
8 inputs, 4 required
- namestringrequired“Campaign name (must be unique in the account).”
- subjectstringrequired“Email subject.”
- sender_idstring or integerrequired“A verified sender id from emailchef_list_senders.”
- list_idsarrayrequired“Lists to send to.”
- segment_idstring or integer“Optional segment of the FIRST list to narrow the audience.”
- html_bodystring“HTML body (include the CAN-SPAM placeholders and unsubscribe link).”
- text_bodystring“Plain-text body.”
- reply_to_idstring or integer“Sender id used for replies.”
emailchef_clone_campaign
“WRITE: copy an existing campaign into a new DRAFT (nothing is sent).”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
1 input, 1 required
- campaign_idstring or integerrequired“The campaign to copy.”
emailchef_update_campaign
“WRITE: change a DRAFT campaign's name, subject, body, sender, reply-to or recipient lists.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
9 inputs, 1 required
- campaign_idstring or integerrequired“Numeric id (as returned by the list tools).”
- namestring
- subjectstring
- html_bodystring
- text_bodystring
- sender_idstring or integer“Numeric id (as returned by the list tools).”
- reply_to_idstring or integer“Numeric id (as returned by the list tools).”
- list_idsarray“Replace the recipient lists (any segment is dropped unless segment_id is also passed).”
- segment_idstring or integer“Segment of the first list (only with list_ids).”
emailchef_send_test_campaign
“WRITE: email ONE test copy of a campaign to a single address.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
2 inputs, 2 required
- campaign_idstring or integerrequired“Numeric id (as returned by the list tools).”
- emailstringrequired“Where to send the test copy.”
emailchef_schedule_campaign
“WRITE, SENDS EMAIL TO CUSTOMERS LATER: schedule a DRAFT campaign to go out to all its recipients at a date and time.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
3 inputs, 3 required
- campaign_idstring or integerrequired“Numeric id (as returned by the list tools).”
- scheduled_timestringrequired“Local send time in the chosen timezone, YYYY-MM-DD HH:MM:SS (no UTC offset or Z).”
- timezone_idstring or integerrequired“Timezone id from emailchef_list_timezones.”
emailchef_unschedule_campaign
“WRITE: cancel the schedule of a SCHEDULED campaign and bring it back to DRAFT.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
1 input, 1 required
- campaign_idstring or integerrequired“Numeric id (as returned by the list tools).”
emailchef_send_campaign
“WRITE, SENDS EMAIL TO CUSTOMERS NOW AND CANNOT BE UNDONE: start sending a DRAFT (or FAILED) campaign immediately to ALL its recipients and use up plan sends.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
2 inputs, 2 required
- campaign_idstring or integerrequired“Numeric id (as returned by the list tools).”
- confirmbooleanrequired“Must be true: the user explicitly approved sending this campaign now.”
emailchef_archive_campaign
“WRITE: archive a campaign (hidden from the default list; statistics are kept).”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
1 input, 1 required
- campaign_idstring or integerrequired“Numeric id (as returned by the list tools).”
emailchef_unarchive_campaign
“WRITE: restore an archived campaign.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
1 input, 1 required
- campaign_idstring or integerrequired“Numeric id (as returned by the list tools).”
emailchef_send_email
“WRITE, SENDS AN EMAIL NOW AND CANNOT BE UNDONE: send a single email to one recipient from a verified sender and use up plan sends.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
8 inputs, 4 required
- sender_idstring or integerrequired“A verified sender id from emailchef_list_senders.”
- to_emailstringrequired
- to_namestring
- subjectstringrequired
- text_bodystring
- html_bodystring
- reply_tostring
- confirmbooleanrequired“Must be true: the user explicitly approved sending this email now.”
emailchef_get_sms_balance
“The account's SMS credit balance and currency.”
Publisher declares: read-only yes · destructive no · open-world yes
Takes no inputs.
emailchef_get_sms_status
“Delivery status of one sent SMS by message id: recipient, text, sent/done time, parts, price, state and error.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- message_idstringrequired“Message id returned by emailchef_send_sms.”
emailchef_send_sms
“WRITE, SENDS TEXT MESSAGES NOW, COSTS SMS CREDIT AND CANNOT BE UNDONE: send an SMS to 1-50 phone numbers in international format (e.g.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
4 inputs, 3 required
- toarrayrequired“Recipient phone numbers.”
- textstringrequired“The message text.”
- fromstring“Sender name or number (default: the account's).”
- confirmbooleanrequired“Must be true: the user explicitly approved sending these SMS now.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-03.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description: 84% of 104
Tools with a description: 100% of 43
Typical description length: 177 characters

The tool set

Counted from the listing

Tools: 43
Size of the list: about 9,302 tokens for an agent to load (characters ÷ 4)
Naming: 43 of 43 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 43 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-03 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://emailchef.usefulapi.io/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "emailchef": {
      "url": "https://emailchef.usefulapi.io/mcp"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "emailchef": {
      "type": "http",
      "url": "https://emailchef.usefulapi.io/mcp"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"emailchef","type":"http","url":"https://emailchef.usefulapi.io/mcp"}'

Claude Code

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

Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)

{
  "mcpServers": {
    "emailchef": {
      "type": "streamableHttp",
      "url": "https://emailchef.usefulapi.io/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}

Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project

{
  "mcpServers": {
    "emailchef": {
      "httpUrl": "https://emailchef.usefulapi.io/mcp"
    }
  }
}

OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project

[mcp_servers.emailchef]
url = "https://emailchef.usefulapi.io/mcp"

Zed · Zed settings file (command: zed: open settings file)

{
  "context_servers": {
    "emailchef": {
      "url": "https://emailchef.usefulapi.io/mcp"
    }
  }
}

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://emailchef.usefulapi.io/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint emailchef.usefulapi.io/mcp	Session opened	matches	our test · 2026-11-03
No credential declared as required	Opened a session without any credential	matches	our test · 2026-11-03
Repository github.com/m190/usefulapi-mcp	Opens publicly	matches	api.github.com · 2026-11-03

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.usefulapi · 748 servers
GitHub owner: a personal account (m190)

Repository: github.com/m190/usefulapi-mcp
Stars: 1
Repository age: 91–180 days
Last push: 0–30 days ago
Archived: no
Security policy: none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-11-03; security policy read from GitHub · 2026-11-01.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Tool list changes

Our reads compared · no tool called

Hosted endpoint emailchef.usefulapi.io/mcp

No change in the tool list across 3 reads (2026-11-01 to 2026-11-03; versions 1.2.0 to 1.4.0).

Compared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-11-03 is not known yet. No tool was called. How it is compared

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 1 star (ranked from 10)

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-03 (security policy 2026-11-01). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.usefulapi/emailchef

Answered from the data above

Who publishes io.usefulapi/emailchef?

The registry ties the namespace io.usefulapi to the domain usefulapi.io; only its owner can publish under it. Its linked repository is github.com/m190/usefulapi-mcp; GitHub reports its owner as m190, a personal account. These are facts from the registry and GitHub, not a rating.

Is io.usefulapi/emailchef safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.usefulapi/emailchef need an API key or sign-in?

It opened a session without any credential on 2026-11-03. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.usefulapi/emailchef been security tested?

Partly. 3 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Does io.usefulapi/emailchef publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of io.usefulapi/emailchef?

In github.com/m190/usefulapi-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-03

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not run · an error was returned
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

3 exercised13 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 13

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server returned an error when its prompts were read.not run · an error was returned
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 2

14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-11-03, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
356 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 43 tools, 0 resources, 6 prompts.
1,844 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

pending: added in the weekly update

listed 2026-11-03; not classified yet

Pricing modelAI-classified

pending: added in the weekly update

the website is not read yet

Programming language

JavaScript

api.github.com · 2026-11-03

Hosting type

remote (hosted by the publisher)

registry · 2026-11-03

MCP capability

prompts, tools

our test · 2026-11-03

Transport

streamable HTTP

registry · 2026-11-03

Required credentials

none declared

registry · 2026-11-03 · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-11-03

Lifecycle status

active

registry · 2026-11-03

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

owner: a personal account · repository age: 91–180 days · stars: 0–9

api.github.com · 2026-11-03

Maintenance

active

api.github.com · 2026-11-03

Environment

the publisher's infrastructure

where it runs, from the hosting type · 2026-11-03

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.usefulapi/emailchef: MCP server record.” Data checked 2026-11-03. https://protocolprobe.com/mcp/servers/io.usefulapi/emailchef

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.usefulapi/emailchef)](https://protocolprobe.com/mcp/servers/io.usefulapi/emailchef)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology