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.

Loop Marketing

REMOTE · LOOPMARKET.ING

Read Apple, Google, Meta and TikTok ad campaigns and draft changes a person approves in Loop.

Available components

+3 this week 77 Trust /100

Last scanned (22 hours ago)

Scores higher than 67% 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 Security89
Transport & Reachability100
Schema Quality & AI Usability51
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2335 tokens (~233/item across 10 items; 10 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 Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 82% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 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 (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.

  • 21 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.

  • 20 Nov 26 0
    • Tool “prepare_campaign_change” rewrote its description, which is the text the model reads security
    • “create_launch_draft” added an optional parameter “deviceOs” cosmetic
  • 19 Nov 26 +1
    • Tool “prepare_campaign_change” rewrote its description, which is the text the model reads security
    • Schema quality: 203 → 228 ▼ functional
    • “create_launch_draft” added an optional parameter “ageMax” cosmetic
    • “prepare_campaign_change” added an optional parameter “ageMax” cosmetic
    • “prepare_campaign_change” added an optional parameter “event” cosmetic
    • “prepare_campaign_change” added an optional parameter “instagramPositions” cosmetic
  • 18 Nov 26 0
    • Tool “prepare_campaign_change” rewrote its description, which is the text the model reads security
    • “create_launch_draft” added an optional parameter “ageMin” cosmetic
    • “prepare_campaign_change” added an optional parameter “ageMin” cosmetic
    • “prepare_campaign_change” reworded the description of “amount” cosmetic
    • “prepare_campaign_change” reworded the description of “campaignId” cosmetic
    • “prepare_campaign_change” reworded the description of “fromCampaignId” cosmetic
  • 16 Nov 26 +1
    • Tool “prepare_campaign_change” rewrote its description, which is the text the model reads security
    • “prepare_campaign_change” added an optional parameter “newKeywords” cosmetic
    • “prepare_campaign_change” reworded the description of “adGroupName” cosmetic
    • “prepare_campaign_change” reworded the description of “bid” cosmetic
    • “prepare_campaign_change” reworded the description of “matchType” cosmetic
    • “prepare_campaign_change” reworded the description of “overrideWorkspaceCap” cosmetic
  • 15 Nov 26 0
    • Tool “list_campaigns” rewrote its description, which is the text the model reads security
    • Tool “prepare_campaign_change” rewrote its description, which is the text the model reads security
    • “prepare_campaign_change” reworded the description of “adGroupName” cosmetic
    • “prepare_campaign_change” reworded the description of “maxCpc” cosmetic
  • 14 Nov 26 0
    • Tool “prepare_campaign_change” rewrote its description, which is the text the model reads security
    • Schema quality: 1522 → 1713 ▼ functional
    • New tool “get_spend_audit” functional
    • “prepare_campaign_change” added an optional parameter “bid” cosmetic
    • “prepare_campaign_change” added an optional parameter “keyword” cosmetic
    • “prepare_campaign_change” added an optional parameter “matchType” cosmetic
    • “prepare_campaign_change” reworded the description of “adGroupName” cosmetic
  • 13 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Stability: unverified → 0.03 ▲ 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://loopmarket.ing/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=loopmarket.ing CN=WR3,O=Google Trust Services,C=US 26 Oct 2026 25 Jan 2027 RSA 2048 SHA256-RSA 130582b5b26ea1ad0ad0f2d9dce87816
SANs: loopmarket.ing, www.loopmarket.ing
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of loopmarket.ing. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ing. DS published 27256 8 Verified
loopmarket.ing. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="loop"

Bearer realm="loop"
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=()

Protected resource metadata

Retrieved No
Problem No resource metadata

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://loopmarket.ing/api/mcp Verified 200
http (plaintext) http://loopmarket.ing/api/mcp HTTPS enforced 301 https://loopmarket.ing:443/api/mcp
MCP tools · 10 exposed · ~2,229 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
create_launch_draft ~545

Prepare a new campaign as a proposal in the Loop inbox (needs a propose key). Same checks as the Loop form: connected channel, unique name, budget plan, guardrails. Nothing is sent to the ad platform; a person approves it in Loop.

NameTypeReqDescription
ageMaxinteger–Meta only: oldest age the ad is shown to, as a hard limit (turns Advantage+ audience off). Omit for no limit.
ageMininteger–Meta only: youngest age the ad is shown to. Omit for no limit.
amountnumberyesTotal budget in major units of the currency the channel's ad account bills in (e.g. 30000 for ¥30,000). Channels whose account currency cannot be read use the workspace currency.
amountCurrencystring–The currency you mean the amount in (ISO 4217, e.g. JPY). If the ad account bills in another currency, nothing is saved.
appEventstring–Meta app event to optimise for instead of installs (see list_app_events).
bodyTextstring––
channelstringyesAd platform key, e.g. meta, google_ads, tiktok, apple_search_ads, microsoft_ads, linkedin_ads, amazon_ads. Must be connected.
countriesarray–ISO country codes, e.g. ["JP"].
deviceOsstring–Meta only: show the ad only on this device OS, as a hard limit (turns Advantage+ audience off). Omit for every device.
draftIdstring–Id of a pending draft to replace. Omit for a new draft.
endTimestringyesEnd, ISO 8601 with offset, e.g. 2026-11-30T23:59:59+09:00.
headlinestring––
imageCreativeIdstring–Creative id from this workspace.
libraryAssetIdstring–Library file id from this workspace.
linkstring–Destination URL (store or website).
moreHeadlinesarray–Google Ads App campaigns only: the 2nd to 5th headlines (Google needs 2–5, each up to 30 wide; full-width counts as 2).
namestringyesCampaign name. Must not exist in the workspace or wait in the inbox already.
placementsarray–Meta placements. Omit to let Meta choose.
startTimestring–Optional start, ISO 8601 with offset.
youtubeVideoIdsarray––

No output schema declared.

No examples provided.

get_campaign ~47

One campaign by id (from list_campaigns): numbers, daily spend, pending proposals and what was executed on it.

NameTypeReqDescription
campaignIdstringyes–
windowinteger––

No output schema declared.

No examples provided.

get_overview ~56

Home KPIs (spend, paid installs, cost per install vs the previous period), the honest headline, measurement caveats and how many proposals wait for a person.

NameTypeReqDescription
windowinteger–Days. Default follows the data.

No output schema declared.

No examples provided.

get_spend_audit ~82

A spend check over the window: campaigns to stop (spend that did not turn into purchases or installs at a cost the workspace can afford), campaigns worth more budget, campaigns with spend but no purchase yet, and ones without enough results to judge. Uses the same verdicts as the Campaigns page and changes nothing.

NameTypeReqDescription
windowinteger––

No output schema declared.

No examples provided.

list_app_events ~29

Meta in-app events this workspace's app sends, usable as appEvent in create_launch_draft.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_budget_tests ~29

Guardrailed budget tests: campaign, dates, daily range, stop rules and the latest verdict.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_campaigns ~46

Campaigns this workspace manages, with state, budget and platform-reported spend, installs and (where the channel reports them) purchases in the window.

NameTypeReqDescription
windowinteger––

No output schema declared.

No examples provided.

list_proposals ~58

The inbox: proposals waiting for a person, ones a guardrail is holding, and the recent execution log (newest first) with each failure's message.

NameTypeReqDescription
limitinteger–Max rows of the execution log. Default 20.

No output schema declared.

No examples provided.

list_workspaces ~30

The workspace this API key belongs to (one per key), with its currency and the key's scope.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

prepare_campaign_change ~1,307

Prepare a change to an existing campaign as a proposal in the Loop inbox (needs a propose key): set a Google Ads search campaign's languages, replace a running search ad's wording and landing page, change a daily budget by more than the per-change limit (the daily cap still applies), give a campaign a total cap that Loop pauses it at, set a max CPC you choose (campaign or ad group; above the workspace max CPC only with overrideWorkspaceCap), move the same daily amount from one campaign to another (total unchanged; both or neither), add an ad group (keywords and one responsive search ad) to a running Google Ads search campaign within its current budget, move a Google Ads or Apple Ads campaign's end date (optionally raising the total cap Loop watches so it does not pause before the new end), keep only chosen keywords in an Apple Ads campaign and pause the rest, set the bid of one keyword in an Apple Ads campaign (daily budget unchanged), add keywords (exact match by default) at one bid to an Apple Ads ad group (daily budget unchanged), set the default bid of an Apple Ads ad group with max_cpc and adGroupName (what a Search Match ad group with no keywords bids), pause a running or scheduled campaign with pause_campaign (budget, end date and ads unchanged; needs only campaignId), set the youngest age a Meta campaign's ad sets or an Apple Ads campaign's ad groups are shown to with min_age and ageMin, optionally (Meta only) with ageMax for the oldest age (Advantage+ audience is turned off so the range is a hard limit; budget, placements and ads unchanged), narrow the Instagram placements of a Meta campaign whose ad sets run on Instagram only with placements and instagramPositions, e.g. ["stream", "reels"] to drop Stories (narrowing only; budget, ages and ads unchanged), change the pixel event a Meta website campaign's ad sets optimize for with optimization_event and event (pixel, budget, targeting and ads unchanged; Meta restarts learning, so a person always approves it)…

NameTypeReqDescription
adGroupNamestring–max_cpc: an ad group of a manual CPC campaign (omit for the campaign max CPC); on Apple Ads the ad group whose default bid changes (may be omitted when the campaign has one ad group). add_ad_group: t…
adRefstring–replace_search_ad: the ad to replace (customers/…/adGroupAds/…).
ageMaxinteger–min_age: optional oldest age (at least ageMin). Turns off Advantage+ audience so Meta keeps the range as a hard limit.
ageMininteger–min_age: the youngest age the campaign's ad sets are shown to.
amountnumber–budget_transfer: the daily amount to move. total_transfer: the amount of total budget to move.
bidnumber–keyword_bid: the new max bid in the account's currency (major units, e.g. 376 for ¥376). add_keywords: the new keywords' max bid.
campaignIdstringyesThe campaign id from list_campaigns (budget_transfer, total_transfer: the campaign that receives).
capnumber–total_cap: the total in the campaign's currency.
dailyBudgetnumber–budget_move: the new daily budget in the campaign's currency.
descriptionsarray––
endDatestring–end_date: the new last day (YYYY-MM-DD) in the ad account's time zone.
eventstring–optimization_event: Meta's custom_event_type to optimize for (CONTENT_VIEW = ViewContent, START_TRIAL = StartTrial, …).
familystring–replace_search_ad / add_ad_group: the workspace campaign family for utm_campaign.
fromCampaignIdstring–budget_transfer, total_transfer: the campaign that gives the budget.
fundedBystring–budget_move: id of the campaign whose budget this uses (recorded only).
headlinesarray––
instagramPositionsarray–placements: the Instagram positions to keep (stream = Feed, story = Stories, reels, explore, …). Must be fewer than the ad sets use now.
keeparray–keep_keywords: the keyword texts to keep enabled; the campaign's other enabled keywords are paused.
keywordstring–keyword_bid: the text of the enabled keyword whose bid changes.
keywordsarray–add_ad_group: the new ad group's keywords.
kindstringyes–
landingstring–replace_search_ad / add_ad_group: landing page without utm_*; UTM is added by Loop.
languagesarray–languages: codes such as vi, ja; empty = all languages.
matchTypestring–keyword_bid: only needed when the same text is enabled with more than one match type. add_keywords: the match type (default EXACT).
maxCpcnumber–max_cpc: the new max CPC in the account's currency (Apple Ads: the ad group's default bid). add_ad_group: the new ad group's max CPC (manual CPC campaigns only).
newKeywordsarray–add_keywords: the keyword texts to add (up to 20); each gets matchType (default EXACT) and bid.
overrideWorkspaceCapboolean–max_cpc / add_keywords: allow a bid above the workspace max CPC.
raiseTotalCapboolean–end_date: if Loop watches a total cap on this campaign, raise it by the added days × daily budget.
sincestring–total_cap: YYYY-MM-DD to count spend from (default today).
utmCampaignstring–replace_search_ad / add_ad_group: utm_campaign for this campaign ({adgroup} allowed).

No output schema declared.

No examples provided.

Install

How do I install the Loop Marketing MCP server?

Loop Marketing is a hosted endpoint at https://loopmarket.ing/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 · loopmarket.ing

# add to Claude Code
claude mcp add --transport http ing-loopmarket-loop 'https://loopmarket.ing/api/mcp'
Common questions

What is the Loop Marketing MCP server?

Loop Marketing is an MCP server listed in the public MCP registry as ing.loopmarket/loop. Read Apple, Google, Meta and TikTok ad campaigns and draft changes a person approves in Loop. This page covers its hosted endpoint (https://loopmarket.ing/api/mcp).

Is the Loop Marketing MCP server safe to use?

Loop Marketing scores 77 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 Loop Marketing MCP server expose?

Loop Marketing exposes 10 tools: list_workspaces, get_overview, list_campaigns, get_spend_audit, get_campaign, and 5 more. Their descriptions and schemas cost roughly 2,229 tokens of context every time the server is loaded.

Does the Loop Marketing MCP server require authentication?

Yes. Loop Marketing 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 Loop Marketing MCP server still maintained?

Loop Marketing 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 Loop Marketing MCP server?

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