Campaign Pack
REMOTE · TOOLS.CAMPAIGNPACK.AI
Turn a product photo and a brief into a full ad campaign: scripts, stills, client-ready PDF.
Available components
Last scanned (16 hours ago)
Scores higher than 83% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Marketing and SEO
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1484 tokens (~114/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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 →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 0
- Tool “get_pack” rewrote its description, which is the text the model reads security
- Tool “list_campaigns” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- “check_campaign” added an optional parameter “session_id” cosmetic
- “get_pack” added an optional parameter “session_id” cosmetic
- “check_campaign” made “job_id” optional cosmetic
- “get_pack” made “job_id” optional cosmetic
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 10 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.
- 8 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.1.0 → 0.1.1 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 21 Nov 2026 · Probed https://tools.campaignpack.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=melihozlem.com | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 18 Aug 2026 | 3 Mar 2027 | RSA 2048 | SHA256-RSA | e9246e737112ea7ccf678b404b18c83 |
| SANs: melihozlem.com, *.melihozlem.com, *.aicreations.net, *.aiscienceresearch.com, campaignpack.ai, *.campaignpack.ai, aiscienceresearch.com, aicreations.net, *.noncomputable.com, noncomputable.com | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tools.campaignpack.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| campaignpack.ai. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="campaignpack", resource_metadata="https://tools.campaignpack.ai/.well-known/oauth-protected-resource"
Bearer realm="campaignpack", resource_metadata="https://tools.campaignpack.ai/.well-known/oauth-protected-resource" Protected resource metadata
| Document | https://tools.campaignpack.ai/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://tools.campaignpack.ai/mcp |
| Authorisation server | https://tools.campaignpack.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tools.campaignpack.ai/mcp | Verified | 200 | |
| http (plaintext) | http://tools.campaignpack.ai/mcp | HTTPS enforced | 301 | https://tools.campaignpack.ai/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 →
abort_campaign Stop a campaign ~27
Stop a running campaign.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | Job id returned by start_campaign. |
No output schema declared.
No examples provided.
answer_approval Answer an approval prompt ~86
Answer a paused run that wants to send the user's data somewhere outside Campaign Pack. Ask the person; never decide for them.
| Name | Type | Req | Description |
|---|---|---|---|
| decision | string | yes | What the person said: 'allow' to let the run go ahead, 'refuse' to deny it. This must be their answer, not yours. |
| job_id | string | yes | Job id returned by start_campaign. |
No output schema declared.
No examples provided.
check_campaign Check campaign progress ~102
Progress of a running campaign: status, the tools it has just called, queue position, and whether it is waiting for a human approval. Poll about every 20 seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | – | Job id returned by start_campaign. |
| session_id | string | – | Campaign to follow, from list_campaigns. An alternative to job_id for a run started in another conversation; only works while it is still going. job_id wins when both are given. |
No output schema declared.
No examples provided.
get_download_url Get a download link ~108
A link the person can open to get one file — the campaign PDF, a product still, a video. Works for any file in the workspace, including ones too big or too binary to read as text. The link expires within the hour.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | File path relative to the workspace, as shown by list_workspace_files. |
| session_id | string | – | Link a file from a campaign shared with this account rather than its own files. Omit for your own workspace. |
No output schema declared.
No examples provided.
get_pack Get the finished pack ~113
Collect a finished campaign: the folder, its files, the written overview, and the path to the PDF. Takes the job_id from start_campaign, or the session_id from list_campaigns — use session_id for a campaign run in an earlier conversation, where no job id survives.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | – | Job id returned by start_campaign. |
| session_id | string | – | Campaign to collect, from list_campaigns. An alternative to job_id, not an addition: job_id wins when both are given. |
No output schema declared.
No examples provided.
list_campaign_access List who can see a campaign ~42
Who owns a campaign and who it is shared with.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | Campaign to act on — the session id from start_campaign or check_campaign. |
No output schema declared.
No examples provided.
list_campaigns List past campaigns ~92
Campaigns on this account, newest first, including ones shared with it. Start here when you do not already have an id — the ids from start_campaign only exist in the conversation that made them, so this is how you find a campaign from last week. Pass a session_id from here to get_pack to open one.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many to return, newest first. Default 20. |
No output schema declared.
No examples provided.
list_workspace_files List workspace files ~90
List files and folders in the account's workspace — campaign folders, scripts, product stills, PDFs, uploads. Directories end in '/'.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Folder to list, relative to the workspace. Omit or '.' for the top level. |
| session_id | string | – | Look inside a campaign shared with this account rather than its own files. Omit for your own workspace. |
No output schema declared.
No examples provided.
read_workspace_file Read a workspace file ~97
Contents of a text file in the workspace — a script, the plan, the creator brief, a transcript. Large files are truncated. For a PDF, image or video call get_download_url instead.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | File path relative to the workspace, as shown by list_workspace_files. |
| session_id | string | – | Read from a campaign shared with this account rather than its own files. Omit for your own workspace. |
No output schema declared.
No examples provided.
share_campaign Share a campaign ~130
Give a teammate access to a campaign by email address — including while it is still running. They see the same live run from their own AI client or the website, can abort it, answer its approval prompts, and take the next turn. They must already have a Campaign Pack account; sharing does not create one.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address of the person to let in. They must already have a Campaign Pack account under this address; sharing does not create one or send an invitation. | |
| session_id | string | yes | Campaign to act on — the session id from start_campaign or check_campaign. |
No output schema declared.
No examples provided.
start_campaign Start a campaign ~246
Start a marketing campaign pack on Campaign Pack's own GPUs. Produces a campaign plan, ideas, ad and social scripts, a creator brief, and a client-ready PDF — plus product stills on the image sizes. Returns immediately with a job id; the run itself takes minutes, so poll check_campaign rather than waiting. Write the brief yourself from what the user told you: the richer and more specific it is, the better the pack. Nothing is sent to any third-party model provider.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | The brand name, spelled exactly as the customer spells it. Every mention in the pack is rewritten to match this. |
| brief | string | yes | What the product is, who it is for, what matters about it. A few sentences to a few paragraphs. State only facts the user gave you — invented metrics or customers end up in the finished pack. |
| photo | string | – | Workspace path from upload_product_photo. Required for the image sizes: the stills are edited from the real photo rather than generated from nothing. |
| size | string | – | Pack size. Available here: 'text' (about a minute), 'lite' (about ten minutes). |
No output schema declared.
No examples provided.
unshare_campaign Remove someone's access ~67
Revoke a collaborator's access. Takes effect on their next request.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address of the collaborator to remove. The owner cannot be removed this way. | |
| session_id | string | yes | Campaign to act on — the session id from start_campaign or check_campaign. |
No output schema declared.
No examples provided.
upload_product_photo Upload a product photo ~106
Put a product photo into the user's workspace so a campaign can edit stills from the real thing. Base64 of the image bytes.
| Name | Type | Req | Description |
|---|---|---|---|
| data_base64 | string | yes | The image file's bytes, base64-encoded. The raw image, not a data: URL and not a path on your own machine. |
| filename | string | yes | Name to save it under, with the extension — 'bottle.jpg'. Reusing a name that is already there replaces that photo. |
No output schema declared.
No examples provided.
How do I install the Campaign Pack MCP server?
Campaign Pack is a hosted endpoint at https://tools.campaignpack.ai/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 · tools.campaignpack.ai
claude mcp add --transport http ai-campaignpack-campaignpack 'https://tools.campaignpack.ai/mcp'
What is the Campaign Pack MCP server?
Campaign Pack is an MCP server listed in the public MCP registry as ai.campaignpack/campaignpack. Turn a product photo and a brief into a full ad campaign: scripts, stills, client-ready PDF. This page covers its hosted endpoint (https://tools.campaignpack.ai/mcp).
Is the Campaign Pack MCP server safe to use?
Campaign Pack scores 83 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 Campaign Pack MCP server expose?
Campaign Pack exposes 13 tools: start_campaign, check_campaign, get_pack, list_campaigns, list_workspace_files, and 8 more. Their descriptions and schemas cost roughly 1,306 tokens of context every time the server is loaded.
Does the Campaign Pack MCP server require authentication?
Yes. Campaign Pack asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Campaign Pack MCP server still maintained?
Campaign Pack 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 Campaign Pack MCP server?
VerifyMCP ran 13 checks on Campaign Pack, 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.