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.

ai.creationloop/creationloop

REMOTE · CREATIONLOOP.AI

CreationLoop is your Marketing Agent. Read the overview, offer, and FAQ; apply as a design partner.

Available components

0 this week 80 Trust /100

Last scanned (13 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 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 Security63
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 277 tokens (~69/item across 4 items; 4 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

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

Checks we could not complete (1)

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 fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

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.

  • 14 Nov 26 0
    • Stability: 0.97 → pass security
  • 13 Nov 26 +1

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

  • 11 Nov 26 +1

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

  • 9 Nov 26 +1

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

  • 7 Nov 26 +1

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

  • 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
  • 4 Nov 26 −4
    • Stability: pass → 0.67 functional
  • 15 Oct 26 0
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • HSTS header: fail → pass ▲ security
    • Transport: fail → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
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://creationloop.ai/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=creationloop.ai CN=YE2,O=Let's Encrypt,C=US 13 Nov 2026 11 Feb 2027 ECDSA 256 ECDSA-SHA384 5e1bb283b593f9a342ec62482100c5eb6cc
SANs: creationloop.ai
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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 creationloop.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
creationloop.ai. 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
Header Value
strict-transport-security max-age=63072000; includeSubDomains

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://creationloop.ai/api/mcp Verified 200
http (plaintext) http://creationloop.ai/api/mcp HTTPS enforced 301 https://creationloop.ai:443/api/mcp
MCP tools · 4 exposed · ~230 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_company_overview ~47

What CreationLoop is, how an agent run becomes verified, exactly what the ledger proves, the registry, and the design-partner offer. Served verbatim from the site's canonical copy.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_design_partner_offer ~38

The current offer, which is the design partnership: what the ledger proves and how to apply. Served verbatim from the site's canonical copy.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_faq ~27

Frequently asked questions about CreationLoop, with answers served verbatim from the site's canonical copy.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

submit_design_partner_application ~118

Apply to become a CreationLoop design partner. Records the full application: email, website host, and any name, company, and message provided; our founder reviews every application and follows up by email.

NameTypeReqDescription
companystring–Company name (optional).
emailstringyesApplicant email address (required).
messagestring–What should we know? Context for the email follow-up (optional).
namestring–Applicant name (optional).
websitestringyesThe brand's website URL (required).

No output schema declared.

No examples provided.

Install

How do I install the ai.creationloop/creationloop MCP server?

ai.creationloop/creationloop is a hosted endpoint at https://creationloop.ai/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 · creationloop.ai

# add to Claude Code
claude mcp add --transport http ai-creationloop-creationloop 'https://creationloop.ai/api/mcp'
Common questions

What is the ai.creationloop/creationloop MCP server?

ai.creationloop/creationloop is an MCP server listed in the public MCP registry as ai.creationloop/creationloop. CreationLoop is your Marketing Agent. Read the overview, offer, and FAQ; apply as a design partner. This page covers its hosted endpoint (https://creationloop.ai/api/mcp).

Is the ai.creationloop/creationloop MCP server safe to use?

ai.creationloop/creationloop scores 80 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 ai.creationloop/creationloop MCP server expose?

ai.creationloop/creationloop exposes 4 tools: get_company_overview, get_design_partner_offer, get_faq, submit_design_partner_application. Their descriptions and schemas cost roughly 230 tokens of context every time the server is loaded.

Does the ai.creationloop/creationloop MCP server require authentication?

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

Is the ai.creationloop/creationloop MCP server still maintained?

ai.creationloop/creationloop 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 ai.creationloop/creationloop MCP server?

VerifyMCP ran 12 checks on ai.creationloop/creationloop, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about ai.creationloop/creationloop: Authorization. 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.