ai.creationloop/creationloop
REMOTE · CREATIONLOOP.AI · SCANNED SEP 22
CreationLoop is your Marketing Agent. Read the overview, offer, and FAQ; apply as a design partner.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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
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
claude mcp add --transport http ai-creationloop-creationloop 'https://creationloop.ai/api/mcp'
{
"mcpServers": {
"ai-creationloop-creationloop": {
"url": "https://creationloop.ai/api/mcp"
}
}
} {
"servers": {
"ai-creationloop-creationloop": {
"type": "http",
"url": "https://creationloop.ai/api/mcp"
}
}
} [mcp_servers.ai-creationloop-creationloop] url = "https://creationloop.ai/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-creationloop-creationloop": {
"type": "remote",
"url": "https://creationloop.ai/api/mcp",
"enabled": true
}
}
} openclaw mcp add ai-creationloop-creationloop --url 'https://creationloop.ai/api/mcp' --transport streamable-http
mcp_servers:
ai-creationloop-creationloop:
url: "https://creationloop.ai/api/mcp" {
"McpServers": {
"ai-creationloop-creationloop": {
"Transport": "http",
"Url": "https://creationloop.ai/api/mcp"
}
}
} assistant mcp add ai-creationloop-creationloop -t streamable-http -u 'https://creationloop.ai/api/mcp'
{
"mcpServers": {
"ai-creationloop-creationloop": {
"type": "http",
"url": "https://creationloop.ai/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 5 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.1.0 → 0.2.0 functional
- 26 Aug 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 Aug 26 +1
- Stability: 0.97 → pass security
- 11 Aug 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
- 8 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “submit_design_partner_application” rewrote its description, which is the text the model reads security
- “submit_design_partner_application” reworded the description of “message” cosmetic
- 5 Aug 26 0
- Tool “get_design_partner_offer” rewrote its description, which is the text the model reads security
- 31 Jul 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
- 30 Jul 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
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 22 Sept 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 | 29 Aug 2026 | 27 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 572684c135f233e2bff6894c66453e1e292 |
| 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. | present | 3799 | 8 | Verified |
| creationloop.ai. | absent | 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 |
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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Company name (optional). |
| string | yes | Applicant email address (required). | |
| message | string | – | What should we know? Context for the email follow-up (optional). |
| name | string | – | Applicant name (optional). |
| website | string | yes | The brand's website URL (required). |
No output schema declared.
No examples provided.
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 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.