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.

NewsletterProAI

REMOTE · NEWSLETTERPROAI.ELITEAIEMPIRE.COM

NewsletterProAI drafts a real newsletter issue from your own notes and sends a real test delivery th

+29 this week 64 Trust /100

Last scanned (14 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Marketing and SEO

Recent critical change

Authorization (16 Nov 2026). See the changelog before you install this server.

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 Security57
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 612 tokens (~76/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 60% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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.

  • 20 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 17 Nov 26 −2
    • HSTS header: pass → fail ▼ security
    • Tool “get_checkout_link” rewrote its description, which is the text the model reads security
    • Schema quality: 57 → 76 ▼ functional
    • Tool coverage: 43% → 60% ▲ functional
    • “get_checkout_link” added an optional parameter “accept_terms” cosmetic
    • “get_checkout_link” added an optional parameter “buyer_email” cosmetic
    • “get_checkout_link” added an optional parameter “store_handle” cosmetic
  • 16 Nov 26 +29
    • Authorization: unverified → fail ▼ critical
    • Injection markers: unverified → pass ▲ security
    • MCP protocol: unverified → fail ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Schema quality: 76 → 57 ▲ functional
    • Tool coverage: 33% → 43% ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.23 ▲ functional
    • New tool “get_checkout_link” functional
    • New tool “get_company_info” functional
    • New tool “list_pricing” functional
    • New tool “search_site” functional
  • 13 Nov 26 −26
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.10 → unverified ▼ security
    • Authorization: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 12 Nov 26 +1

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

  • 10 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 9 Nov 26 59

    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 21 Nov 2026 · Probed https://newsletterproai.eliteaiempire.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=eliteaiempire.com CN=YE1,O=Let's Encrypt,C=US 6 Oct 2026 4 Jan 2027 ECDSA 256 ECDSA-SHA384 517249ed134f0bde704a0af855a2b2bb62e
SANs: *.eliteaiempire.com, eliteaiempire.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of newsletterproai.eliteaiempire.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
eliteaiempire.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://newsletterproai.eliteaiempire.com/mcp Verified 200
http (plaintext) http://newsletterproai.eliteaiempire.com/mcp HTTPS enforced 302 https://newsletterproai.eliteaiempire.com/mcp
MCP tools · 8 exposed · ~612 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
get_checkout_link ~206

Checkout URL for a plan. With no arguments: the main paid plan. Where the site supports it the URL is a Stripe-hosted Checkout session (created unpaid; a human pays, nothing is charged by this tool). A free plan is only returned when the plan is requested or the company sells nothing else.

NameTypeReqDescription
accept_termsboolean–ONLY where the site requires the buyer to accept its Terms/refund policy before checkout: set true only after the human buyer has read and accepted the policy links the tool lists. Never set it on yo…
buyer_emailstring–only for sites that need the buyer's email or store handle before checkout: the human buyer's own receipt email
intervalstring––
planstring–plan name from list_pricing
store_handlestring–only where the site asks for it (StoreForge): the store handle the buyer chose, 3+ chars a-z 0-9 -

No output schema declared.

No examples provided.

get_company_info ~30

What this company sells, who it is for, and every agent/API entry point. No account needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_pricing ~34

Current plans and prices in USD: plan, interval, amount_usd, currency, what_you_get. No account needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

newsletter_about ~71

What NewsletterPro AI does and what is free Pricing: {"unit": "call", "price_usd": 0, "free_quota": "200 per day per IP", "note": "Keyed volume pricing is published at https://newsletterproai.eliteaiempire.com/pricing"}.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

newsletter_draft ~144

Returns a subject line and HTML body written from your topic and notes. Needs a write-scoped key; each call is metered. Pricing: {"unit": "call", "price_usd": null, "pricing_url": "https://newsletterproai.eliteaiempire.com/pricing", "free_quota": 0, "per_key_daily_cap": 25, "note": "Needs a scoped API key. The per-call price is not published yet; keys are issued on request."}.

NameTypeReqDescription
confirmbooleanyesMust be true. This action is paid or destructive.
notesstringyes–
topicstringyes–

No output schema declared.

No examples provided.

newsletter_pricing ~70

Where prices live and what costs nothing Pricing: {"unit": "call", "price_usd": 0, "free_quota": "200 per day per IP", "note": "Keyed volume pricing is published at https://newsletterproai.eliteaiempire.com/pricing"}.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_site ~38

Find pages on this site by keyword; returns url, title and summary.

NameTypeReqDescription
limitinteger––
querystringyeskeywords

No output schema declared.

No examples provided.

usage_get ~19

Usage for the calling key (last 30 days)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the NewsletterProAI MCP server?

NewsletterProAI is a hosted endpoint at https://newsletterproai.eliteaiempire.com/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 · newsletterproai.eliteaiempire.com

# add to Claude Code
claude mcp add --transport http com-eliteaiempire-newsletterproai 'https://newsletterproai.eliteaiempire.com/mcp'
Common questions

What is the NewsletterProAI MCP server?

NewsletterProAI is an MCP server listed in the public MCP registry as com.eliteaiempire/newsletterproai. NewsletterProAI drafts a real newsletter issue from your own notes and sends a real test delivery th. This page covers its hosted endpoint (https://newsletterproai.eliteaiempire.com/mcp).

Is the NewsletterProAI MCP server safe to use?

NewsletterProAI scores 64 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 NewsletterProAI MCP server expose?

NewsletterProAI exposes 8 tools: newsletter_draft, newsletter_about, newsletter_pricing, usage_get, get_company_info, and 3 more. Their descriptions and schemas cost roughly 612 tokens of context every time the server is loaded.

Does the NewsletterProAI MCP server require authentication?

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

Is the NewsletterProAI MCP server still maintained?

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

VerifyMCP ran 13 checks on NewsletterProAI, 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.