Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Emailchef MCP by usefulapi

REMOTE · EMAILCHEF.USEFULAPI.IO

Read lists, contacts, campaign stats; add contacts; draft, schedule and send campaigns and SMS.

18 Trust /100

Last scanned (5 hours ago)

Scores higher than 4% of remote servers

Reachable. Last reached 6 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (4)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (7)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 2 Nov 26 −48
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Stability: 0.03 → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 1 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 31 Oct 26 65

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 6 Nov 2026 · Probed https://emailchef.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=usefulapi.io CN=WE1,O=Google Trust Services,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 d9be3287b0fde9630e825ba1f79bff3f
SANs: usefulapi.io, *.usefulapi.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of emailchef.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
usefulapi.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 302

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://emailchef.usefulapi.io/mcp Redirected 302 https://usefulapi.io/emailchef/
http (plaintext) http://emailchef.usefulapi.io/mcp Inconclusive 302 http://emailchef.usefulapi.io/mcp
MCP tools · 43 exposed · ~3,749 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
emailchef_archive_campaign ~60

WRITE: archive a campaign (hidden from the default list; statistics are kept). Reversible with emailchef_unarchive_campaign. PUT /campaigns/{id}/archivecampaign.

NameTypeReqDescription
campaign_id–yesNumeric id (as returned by the list tools).

No output schema declared.

No examples provided.

emailchef_block_emails ~62

WRITE: add up to 100 addresses to the account blocklist so they never receive email from any list. Reversible with emailchef_unblock_email. POST /blockings?type=MANUAL.

NameTypeReqDescription
emailsarrayyesAddresses to block.

No output schema declared.

No examples provided.

emailchef_clone_campaign ~65

WRITE: copy an existing campaign into a new DRAFT (nothing is sent). A SENT campaign cannot be cloned (Emailchef answers HTTP 500). Returns the new campaign id. POST /newsletters?clone=1.

NameTypeReqDescription
campaign_id–yesThe campaign to copy.

No output schema declared.

No examples provided.

emailchef_create_campaign ~227

WRITE: create a new campaign as a DRAFT (nothing is sent). Needs a verified sender (emailchef_list_senders) and at least one list. To be sendable the HTML body must contain the CAN-SPAM placeholders [[account:business]], [[account:address_1]], [[account:city]], [[account:postal_code]], [[account:country]] and an unsubscribe link <a href="[[unsubscribe_link]]">, otherwise the send ends FAILED. Schedule or send it afterwards. POST /newsletters.

NameTypeReqDescription
html_bodystring–HTML body (include the CAN-SPAM placeholders and unsubscribe link).
list_idsarrayyesLists to send to.
namestringyesCampaign name (must be unique in the account).
reply_to_id––Sender id used for replies.
segment_id––Optional segment of the FIRST list to narrow the audience.
sender_id–yesA verified sender id from emailchef_list_senders.
subjectstringyesEmail subject.
text_bodystring–Plain-text body.

No output schema declared.

No examples provided.

emailchef_create_contact ~153

WRITE: add a contact (email, name, custom fields) to a list. Only add people who agreed to receive email: an ACTIVE contact will receive the account's campaigns and automations. Returns the contact id and status. POST /contacts.

NameTypeReqDescription
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.
emailstringyes–
first_namestring––
last_namestring––
list_id–yesNumeric id (as returned by the list tools).
statusstring–Initial state (default: the account's default, normally ACTIVE).

No output schema declared.

No examples provided.

emailchef_create_list ~48

WRITE: create a new, empty contact list. Returns the new list id. POST /lists.

NameTypeReqDescription
descriptionstring–List description.
namestringyesList name.

No output schema declared.

No examples provided.

emailchef_get_account ~41

The Emailchef account this API key belongs to: id, email, language, status, subscriber total, bounces and complaints. GET /accounts/current.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

emailchef_get_campaign ~65

One campaign: name, subject, HTML and text body, sender, reply-to, state, schedule, recipient lists/segments and cached sent/open/click counts. GET /campaigns/{id}.

NameTypeReqDescription
campaign_id–yesNumeric id (as returned by the list tools).

No output schema declared.

No examples provided.

emailchef_get_campaign_counts ~36

How many campaigns the account has by state: drafts, sent, scheduled, archived, failed. GET /campaigns/count.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

emailchef_get_campaign_links ~48

The links contained in a campaign (id, name, URL). GET /newsletters/{id}/links.

NameTypeReqDescription
campaign_id–yesNumeric id (as returned by the list tools).

No output schema declared.

No examples provided.

emailchef_get_contact ~78

One contact in one list: status, email, name, IP, how it was added, when, and its custom field values. GET /contacts/{contact_id}?list_id=...

NameTypeReqDescription
contact_id–yesNumeric id (as returned by the list tools).
list_id–yesNumeric id (as returned by the list tools).

No output schema declared.

No examples provided.

emailchef_get_import_task ~53

One import task: status, progress, imported/updated/failed counts and any error message. GET /importtasks/{task_id}.

NameTypeReqDescription
task_id–yesNumeric id (as returned by the list tools).

No output schema declared.

No examples provided.

emailchef_get_list ~46

One contact list: name, description, default sender, creation date. GET /lists/{list_id}.

NameTypeReqDescription
list_id–yesNumeric id (as returned by the list tools).

No output schema declared.

No examples provided.

emailchef_get_list_contact_counts ~55

How many contacts a list has by state: active, unsubscribed, bounced, reported. GET /lists/{list_id}/stats/count.

NameTypeReqDescription
list_id–yesNumeric id (as returned by the list tools).

No output schema declared.

No examples provided.

emailchef_get_list_stats ~91

Daily growth of a list over a date range: total contacts per day and the daily delta. Omit the dates for the whole history. GET /lists/{list_id}/stats.

NameTypeReqDescription
end_datestring–Last day, yyyy-mm-dd.
list_id–yesNumeric id (as returned by the list tools).
start_datestring–First day, yyyy-mm-dd.

No output schema declared.

No examples provided.

emailchef_get_segment ~61

One segment with its logic and condition groups. GET /lists/{list_id}/segments/{segment_id}.

NameTypeReqDescription
list_id–yesNumeric id (as returned by the list tools).
segment_id–yesNumeric id (as returned by the list tools).

No output schema declared.

No examples provided.

emailchef_get_sms_balance ~26

The account's SMS credit balance and currency. GET /sms/balance.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

emailchef_get_sms_status ~62

Delivery status of one sent SMS by message id: recipient, text, sent/done time, parts, price, state and error. GET /sms/status/{messageId}.

NameTypeReqDescription
message_idstringyesMessage id returned by emailchef_send_sms.

No output schema declared.

No examples provided.

emailchef_get_subscription ~49

The account's current Emailchef plan: plan name, plan expiry, contact and send limits, credits left, active/expired flags. Check this before a big send. GET /subscriptions/current.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

emailchef_import_contacts ~141

WRITE: bulk-add or update up to 500 contacts in a list in one call (an existing email is updated). Each contact is an object keyed by field placeholder, e.g. {"email":"a@b.com","firstname":"Ada"}: get the placeholders from emailchef_list_predefined_fields and emailchef_list_custom_fields. Import only people who agreed to receive email. Runs in the background: poll emailchef_get_import_task with the returned id. POST /lists/{list_id}/import.

NameTypeReqDescription
contactsarrayyesContacts to import, each keyed by placeholder.
list_id–yesNumeric id (as returned by the list tools).

No output schema declared.

No examples provided.

emailchef_list_blocked ~99

List the account's blocklist (emails that never receive email): address and reason (MANUAL, UNSUBSCRIBED, COMPLAINT). GET /blockings.

NameTypeReqDescription
limitinteger–Results per page, 1-100 (default 25).
offsetinteger–Rows to skip (default 0). Pass the previous reply's next_offset.
searchstring–Only addresses containing this text.

No output schema declared.

No examples provided.

emailchef_list_campaign_engagement ~149

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. Pick exactly one event. GET /newsletters/{id}/contacts.

NameTypeReqDescription
campaign_id–yesNumeric id (as returned by the list tools).
eventstringyesWhich engagement slice to list.
limitinteger–Results per page, 1-100 (default 25).
offsetinteger–Rows to skip (default 0). Pass the previous reply's next_offset.
searchstring–Only contacts whose email or name contains this text.

No output schema declared.

No examples provided.

emailchef_list_campaigns ~166

List email campaigns with state, recipients, delivered, unique opens and unique clicks. Without a status filter Emailchef returns only SENT and ARCHIVED campaigns; pass a status to see DRAFT, SCHEDULED, SENDING or FAILED ones. GET /campaigns.

NameTypeReqDescription
limitinteger–Results per page, 1-100 (default 25).
offsetinteger–Rows to skip (default 0). Pass the previous reply's next_offset.
orderstring–Sort direction (default desc).
order_bystring–Sort by date (default) or name.
searchstring–Only campaigns whose name contains this text.
statusstring–Only campaigns in this state (default: SENT and ARCHIVED).

No output schema declared.

No examples provided.

emailchef_list_contacts ~139

List the contacts of one list (id, email, name, added by, subscription date), optionally by state. GET /contacts?list_id=...

NameTypeReqDescription
limitinteger–Results per page, 1-100 (default 25).
list_id–yesNumeric id (as returned by the list tools).
offsetinteger–Rows to skip (default 0). Pass the previous reply's next_offset.
orderstring–Sort direction (default desc).
order_bystring–Sort field (default subscription date).
statusstring–Only contacts in this state (default: all).

No output schema declared.

No examples provided.

emailchef_list_custom_fields ~60

The custom contact fields of a list: name, data type, placeholder (the key used when writing contacts), options. GET /lists/{list_id}/customfields.

NameTypeReqDescription
list_id–yesNumeric id (as returned by the list tools).

No output schema declared.

No examples provided.

emailchef_list_import_tasks ~42

List contact import tasks: list, status (DISPATCHED, COMPLETE, FAILED), progress, imported/updated/failed counts. GET /importtasks.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

emailchef_list_lists ~112

List the contact lists with id, name, and counts of active, unsubscribed and bounced contacts and segments. Newest first by default. GET /lists.

NameTypeReqDescription
limitinteger–Results per page, 1-100 (default 25).
offsetinteger–Rows to skip (default 0). Pass the previous reply's next_offset.
orderstring–Sort direction (default desc).
order_bystring–Sort by creation date (default) or name.

No output schema declared.

No examples provided.

emailchef_list_predefined_fields ~34

The built-in contact fields (email, first name, ...) with their placeholders. GET /predefinedfields.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

emailchef_list_segments ~89

List the saved segments of a list with how many contacts match each. GET /lists/{list_id}/segments.

NameTypeReqDescription
limitinteger–Results per page, 1-100 (default 25).
list_id–yesNumeric id (as returned by the list tools).
offsetinteger–Rows to skip (default 0). Pass the previous reply's next_offset.

No output schema declared.

No examples provided.

emailchef_list_senders ~41

List the sender identities (name, email, verification status, postal address). Campaigns and emails need a verified sender id. GET /senders.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

emailchef_list_timezones ~41

List Emailchef's timezones (id, name, fixed UTC offset). The id is required to schedule a campaign. GET /meta/timezones.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

emailchef_schedule_campaign ~147

WRITE, SENDS EMAIL TO CUSTOMERS LATER: schedule a DRAFT campaign to go out to all its recipients at a date and time. Emailchef timezones are fixed offsets without daylight saving: pick the id (emailchef_list_timezones) whose offset matches the send date. Undo before it starts with emailchef_unschedule_campaign. PUT /campaigns/{id}/schedule.

NameTypeReqDescription
campaign_id–yesNumeric id (as returned by the list tools).
scheduled_timestringyesLocal send time in the chosen timezone, YYYY-MM-DD HH:MM:SS (no UTC offset or Z).
timezone_id–yesTimezone id from emailchef_list_timezones.

No output schema declared.

No examples provided.

emailchef_send_campaign ~144

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. Check the recipients (emailchef_get_campaign), the sender and the subscription first, ideally after emailchef_send_test_campaign, and send only with the user's explicit go-ahead (confirm must be true). Queued asynchronously: poll emailchef_get_campaign for the final state. PUT /campaigns/{id}/send.

NameTypeReqDescription
campaign_id–yesNumeric id (as returned by the list tools).
confirmbooleanyesMust be true: the user explicitly approved sending this campaign now.

No output schema declared.

No examples provided.

emailchef_send_email ~161

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. Pass text_body and/or html_body. The recipient does not need to be a contact. Send only with the user's explicit go-ahead (confirm must be true). POST /sendmail.

NameTypeReqDescription
confirmbooleanyesMust be true: the user explicitly approved sending this email now.
html_bodystring––
reply_tostring––
sender_id–yesA verified sender id from emailchef_list_senders.
subjectstringyes–
text_bodystring––
to_emailstringyes–
to_namestring––

No output schema declared.

No examples provided.

emailchef_send_sms ~148

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. +393331234567). Check emailchef_get_sms_balance first and send only with the user's explicit go-ahead (confirm must be true). Returns a message id per recipient and the remaining balance. POST /sms/send.

NameTypeReqDescription
confirmbooleanyesMust be true: the user explicitly approved sending these SMS now.
fromstring–Sender name or number (default: the account's).
textstringyesThe message text.
toarrayyesRecipient phone numbers.

No output schema declared.

No examples provided.

emailchef_send_test_campaign ~76

WRITE: email ONE test copy of a campaign to a single address. The campaign state does not change. The sender must be verified. PUT /campaigns/{id}/sendtest.

NameTypeReqDescription
campaign_id–yesNumeric id (as returned by the list tools).
emailstringyesWhere to send the test copy.

No output schema declared.

No examples provided.

emailchef_unarchive_campaign ~44

WRITE: restore an archived campaign. PUT /campaigns/{id}/unarchivecampaign.

NameTypeReqDescription
campaign_id–yesNumeric id (as returned by the list tools).

No output schema declared.

No examples provided.

emailchef_unblock_email ~54

WRITE: remove one address from the account blocklist so it can receive email again. Only do this for an address whose owner asked for it. DELETE /blockings/{email}.

NameTypeReqDescription
emailstringyes–

No output schema declared.

No examples provided.

emailchef_unschedule_campaign ~55

WRITE: cancel the schedule of a SCHEDULED campaign and bring it back to DRAFT. PUT /campaigns/{id}/unschedule.

NameTypeReqDescription
campaign_id–yesNumeric id (as returned by the list tools).

No output schema declared.

No examples provided.

emailchef_unsubscribe_contact ~71

WRITE: unsubscribe one contact from one list (it stops receiving that list's email). POST /lists/{list_id}/unsubscribe?contact_id=...

NameTypeReqDescription
contact_id–yesNumeric id (as returned by the list tools).
list_id–yesNumeric id (as returned by the list tools).

No output schema declared.

No examples provided.

emailchef_update_campaign ~193

WRITE: change a DRAFT campaign's name, subject, body, sender, reply-to or recipient lists. Only the fields you pass change: the tool reads the campaign first and sends the complete record back, because Emailchef blanks any omitted field. Refuses a campaign that is not a DRAFT. PUT /newsletters/{id}.

NameTypeReqDescription
campaign_id–yesNumeric id (as returned by the list tools).
html_bodystring––
list_idsarray–Replace the recipient lists (any segment is dropped unless segment_id is also passed).
namestring––
reply_to_id––Numeric id (as returned by the list tools).
segment_id––Segment of the first list (only with list_ids).
sender_id––Numeric id (as returned by the list tools).
subjectstring––
text_bodystring––

No output schema declared.

No examples provided.

emailchef_update_contact ~147

WRITE: change a contact's name, state or custom fields in one list. Only the fields you pass change. Setting the status to ACTIVE re-subscribes someone: only do so with their consent. PUT /contacts/{contact_id}.

NameTypeReqDescription
contact_id–yesNumeric id (as returned by the list tools).
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.
first_namestring––
last_namestring––
list_id–yesNumeric id (as returned by the list tools).
statusstring––

No output schema declared.

No examples provided.

emailchef_update_list ~70

WRITE: rename a contact list and/or change its description. Only the fields you pass change. PUT /lists/{list_id}.

NameTypeReqDescription
descriptionstring–New description.
list_id–yesNumeric id (as returned by the list tools).
namestring–New list name.

No output schema declared.

No examples provided.

Install

How do I install the Emailchef MCP by usefulapi server?

Emailchef MCP by usefulapi is a hosted endpoint at https://emailchef.usefulapi.io/mcp, 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.

remote · emailchef.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-emailchef 'https://emailchef.usefulapi.io/mcp'
Common questions

What is the Emailchef MCP by usefulapi server?

Emailchef MCP by usefulapi is listed in the public MCP registry as io.usefulapi/emailchef. Read lists, contacts, campaign stats; add contacts; draft, schedule and send campaigns and SMS. This page covers its hosted endpoint (https://emailchef.usefulapi.io/mcp).

Is the Emailchef MCP by usefulapi server safe to use?

Emailchef MCP by usefulapi scores 18 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 Emailchef MCP by usefulapi server expose?

Emailchef MCP by usefulapi exposes 43 tools: emailchef_get_account, emailchef_get_subscription, emailchef_list_senders, emailchef_list_timezones, emailchef_list_lists, and 38 more. Their descriptions and schemas cost roughly 3,749 tokens of context every time the server is loaded.

Does the Emailchef MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Emailchef MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Emailchef MCP by usefulapi server still maintained?

Emailchef MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 6 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 Emailchef MCP by usefulapi server?

VerifyMCP ran 4 checks on Emailchef MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Emailchef MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.