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.

Promptafire

REMOTE · MARKETING.PROMPTAFIRE.COM

Read Promptafire's AI-for-marketers lessons and blog. Optional sign-in unlocks Pro lessons.

0 this week 90 Trust /100

Last scanned (17 hours ago)

Scores higher than 98% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Education and Research

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 Security83
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 391 tokens (~48/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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (25% of tools); any adoption earns full credit.Pass
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 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

  • 4 Oct 26 +1
    • Stability: 0.97 → pass security
  • 28 Sept 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
  • 25 Sept 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
  • 5 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 4 Sept 26 0

    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 5 Nov 2026 · Probed https://marketing.promptafire.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=marketing.promptafire.com CN=YR2,O=Let's Encrypt,C=US 14 Sept 2026 13 Dec 2026 RSA 2048 SHA256-RSA 51f87400337c8235ea17075fe8f2246085a
SANs: marketing.promptafire.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of marketing.promptafire.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
promptafire.com. DS published 2371 13 Verified
marketing.promptafire.com. Verified address RRset verified with the apex keys
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
Header Value
strict-transport-security max-age=63072000

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://marketing.promptafire.com/api/mcp Verified 200
http (plaintext) http://marketing.promptafire.com/api/mcp HTTPS enforced 308 https://marketing.promptafire.com/api/mcp
MCP tools · 8 exposed · ~338 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
fetch ~57

Return the full Markdown of one search result by id. Free lessons and blog posts always; Pro lessons only when the connected Promptafire account has Pro access, otherwise a short locked notice.

NameTypeReqDescription
idstringyesAn id returned by search
NameTypeReqDescription
idstringyes–
metadataobject––
textstringyes–
titlestringyes–
urlstringyes–

No examples provided.

get_module ~39

A module's description, duration, access level, and section list.

NameTypeReqDescription
slugstringyesModule slug, for example think-before-you-prompt

No output schema declared.

No examples provided.

list_modules ~27

The full curriculum: every track and module with its access level and a link to its overview.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_posts ~24

Every published Promptafire blog post with date, author, and a link.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

read_lesson ~56

The Markdown body of one lesson section. Free modules always. Pro modules only when the connected Promptafire account has Pro access.

NameTypeReqDescription
modulestringyesModule slug
sectionstringyesSection slug from get_module

No output schema declared.

No examples provided.

read_post ~28

The Markdown body of one blog post.

NameTypeReqDescription
slugstringyesPost slug from list_posts

No output schema declared.

No examples provided.

search ~55

Search Promptafire lessons and blog posts. Returns ids for fetch, titles, and web URLs. Lesson ids look like lesson:<module>/<section>, post ids like post:<slug>.

NameTypeReqDescription
querystringyesWhat to look for
NameTypeReqDescription
resultsarrayyes–

No examples provided.

search_curriculum ~52

Full-text search across Promptafire lessons. Returns module, section, whether it is free or Pro, a short snippet when readable, and the web URL.

NameTypeReqDescription
querystringyesWhat to look for

No output schema declared.

No examples provided.

Install

How do I install the Promptafire MCP server?

Promptafire is a hosted endpoint at https://marketing.promptafire.com/api/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 · marketing.promptafire.com

# add to Claude Code
claude mcp add --transport http com-promptafire-marketing-promptafire 'https://marketing.promptafire.com/api/mcp'
Common questions

What is the Promptafire MCP server?

Promptafire is an MCP server listed in the public MCP registry as com.promptafire.marketing/promptafire. Read Promptafire's AI-for-marketers lessons and blog. Optional sign-in unlocks Pro lessons. This page covers its hosted endpoint (https://marketing.promptafire.com/api/mcp).

Is the Promptafire MCP server safe to use?

Promptafire scores 90 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 Promptafire MCP server expose?

Promptafire exposes 8 tools: search, fetch, search_curriculum, list_modules, get_module, and 3 more. Their descriptions and schemas cost roughly 338 tokens of context every time the server is loaded.

Does the Promptafire MCP server require authentication?

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

Is the Promptafire MCP server still maintained?

Promptafire 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 Promptafire MCP server?

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