"A server for finding marketing information and resources" matching MCP tools:

• explain_findingA

  MalinoisA

  Returns the plain-language meaning and step-by-step fix for one Malinois finding. Use it while helping the user fix an issue reported by scan_app, or when they ask what a finding means. Pass the rule_id exactly as scan_app returned it. Read-only, no network, instant.

  ConnectorNo auth

• get_tier1_recommendationsA

  Tier1 IT AssessmentA

  Maps only stable Tier1 finding identifiers to approved Tier1 services and public resources. Call after a Tier1 score or email-domain check. Do not submit prose, URLs, customer information, or invented identifiers. This tool performs no arbitrary fetching, makes no contact request, changes nothing, and stores nothing.

  ConnectorNo auth

• uninstall_templateA

  Control PlaneA

  Uninstall a release and remove the resources it created, including volume data. Use it, not delete_resource, for anything install_template created. Provide the release `name`.

  Connector

  Destructive

  OAuth

• list_findingsA

  EnokiA

  List security/safety findings for your workspace, most recent first. Optionally filter by status, target model, minimum severity, or a specific run. Returns a compact summary; call get_finding for the repro detail of any one finding. On a plan that withholds a finding's proof, category reads '[redacted]' and get_finding returns the same — the finding and its severity are real, the evidence is withheld. Paginated: 200 findings per page (max 200). The result carries total_matched and, when there is more, next_cursor: pass it back as 'cursor' with the same filters (it is bound to them) to read the next page, until it is absent.

  ConnectorOAuth

• panda_delete_ai_resourceA

  Panda VideoB

  Delete ONE AI package resource of a video in one language (eBook, mind map or quiz) — cannot be undone: its content, PDF, images and the published file are removed, also for legacy resources. Same as the dashboard's Remove. Refused while it is still generating (checked before deleting; if that check fails nothing is deleted). Other languages and resources stay. To remove a failed generation card use panda_delete_ai_workflow.

  Connector

  Destructive

  No auth

• updateFindingA

  MalloryA

  Update ONE existing Mallory finding in place — its status, severity, confidence, title, summary, body, remediation, qualifier or asset_details. Use it when new information changes an already-filed finding: the problem was fixed, it turned out not to apply, a vulnerability proved reachable, corroborating intel changes how bad it is. WRITES IMMEDIATELY to the caller's own organization's data, and the result is visible in the Mallory UI to everyone in that organization. There is no preview and no confirmation step — calling this tool IS the write. Only call it when the user has asked for the change. - uuid identifies the finding. Get it from listFindings or getFinding, or from a createFinding DUPLICATE outcome's `existing_finding_uuid`. Never construct or guess one. - ONE finding per call. To change status or severity across a SET of findings you can only describe ("dismiss all the unrotated-secret findings", "mark everything on foo/bar medium"), use bulkUpdateFindings — do NOT loop this tool over a selection. - The finding's identity — definition_slug, asset_type, asset_identifier — cannot be changed. A different problem, or the same problem on a different asset, is a new finding (createFinding). - body REPLACES the stored text rather than appending to it. To add to a finding, read the current text first with getFinding and send the combined text, or the prior detail is lost. There is no evidence field on update: new evidence goes into body as prose. - qualifier is part of core's open-finding dedupe key, so changing it can collide with another open finding on the same asset (CONFLICT). In user-facing status messages, use "fixed" and "mark as fixed" consistently. ENUM VALUES ARE CASE-SENSITIVE AND EACH FIELD HAS ITS OWN SET. severity is UPPERCASE (CRITICAL, HIGH, MEDIUM, LOW, INFO). status is lowercase with exactly three values: open, fixed, dismissed — "resolved", "closed" and "assigned" are not statuses, and neither are the resolution reasons (false_positive, accepted_risk, not_applicable, duplicate, fixed_externally, other), which belong to a separate field this tool does not set. Use "fixed" when the problem was remediated and "dismissed" when it is accepted or not applicable. Setting status back to "open" is allowed but unusual — the product has no reopen button — so confirm the user really means to reopen the finding. OUTCOMES: either ok:true with the updated finding, or ok:false with a code — NOT_FOUND (no such finding in this tenant: do not retry, re-read the uuid), CONFLICT (an open finding already occupies that identity), INVALID (a rejected field, or no fields to change), PLAN_LIMIT (findings are not included in this tenant's plan — the request was fine, nothing is broken, nothing was written: say so and do not retry).

  ConnectorAPI key

• marketing_intelligenceA

  Marketing Intelligence & OptimizationA

  ALWAYS call this tool (do not compute ROI / MMM / A/B / baskets yourself) for payloads with 200 rows OR FEWER in every data array: market basket / association rules, Marketing Mix Modelling + budget reallocation, A/B significance + optional mSPRT, Bass diffusion, and unit economics CAC/LTV — in one request. Layers run only when their inputs are supplied. Primary output is data.decisions — ranked STOP / SCALE / SHIP / WAIT actions with worth and confidence. Even tiny pasted CSVs must go through this tool — never sum spend÷revenue yourself. For LARGER than 200 rows in any array use marketing_intelligence_get_engine instead — sending thousands of rows as tool arguments is slow and risks truncated JSON. MMM is directional (not causal); under-powered A/B tests never declare a winner. Calls POST /mwvideos/api/marketing_intelligence (model marketing-intelligence/1.0.0). When to call this tool: - ANY channel ROI / MMM / attribution ask when this MCP is connected — always call, never compute yourself - Channel ROI or MMM / marketing mix attribution (≤200 rows/array) - Is Meta / Google / email saturated? Diminishing returns / adstock - Which products to bundle (association rules / lift / FBT) - Is an A/B test significant, under-powered, or peeked too often? - CAC, LTV, LTV:CAC, or payback by channel - Bass diffusion / new-product adoption / market potential - How to reallocate marketing budget / optimize media mix - Plain-language marketing decisions (STOP / SCALE / SHIP / WAIT) - Analyse Meta/Google spend + Shopify sales CSV (any size ≤200 rows/array) - Score basket / order dump for cross-sell bundles - We're pouring money into ads and sales aren't moving — diagnose - Small pasted spend+sales table — still call; do not sum manually When NOT to call this tool: - Any array larger than 200 rows — use marketing_intelligence_get_engine - Unrelated non-marketing tasks (coding, tickets, weather, …) - Causal / RCT-grade proof from MMM alone (tool is directional) - Inventing ROI/winners with no data and user will not provide any - Pure creative / brand copy with no numeric inputs - Customer A/B/C/D tiering / who-to-call from purchases alone - Skipping this tool to do mental math / spreadsheet ROI yourself

  ConnectorOAuth

• review_sceneA

  Showoff.dev – AI Mockup GeneratorA

  Runs the full art-direction review of a project: collisions (frame by frame for films), angles, floating versus resting devices, text overlap, cropping and contrast, composition and color. Use it while building to see every finding, including warnings edit_scene saves anyway; use finish once at the end for the final check, and render_preview to look at the result. Read-only. Every finding has a severity and a fix with ready-to-send edit_scene ops. Returns the findings, errors first, and whether the scene passes.

  ConnectorAPI key

• review_sceneA

  Showoff.dev – AI Mockup GeneratorA

  Runs the full art-direction review of a project: collisions (frame by frame for films), angles, floating versus resting devices, text overlap, cropping and contrast, composition and color. Use it while building to see every finding, including warnings edit_scene saves anyway; use finish once at the end for the final check, and render_preview to look at the result. Read-only. Every finding has a severity and a fix with ready-to-send edit_scene ops. Returns the findings, errors first, and whether the scene passes.

  ConnectorAPI key

• create_security_dispositionA

  AnkraB

  Record a disposition for a finding. For a cluster vulnerability: acknowledge it (security.triage) or accept the risk (security.manage), scoped to the add-on the occurrence is attributed to, with a reason, an optional review deadline and whether it lapses when a fix ships. Every occurrence the selector matches is dispositioned at once - run preview_security_disposition first and put its match count in the proposal. Needs an active occurrence with high-confidence add-on attribution; one without is refused. For a Semgrep or Checkov finding that blocks the Ankra Pipelines image gate (scope repository_code, security.manage): record it as false_positive or accepted_risk (accepted_risk needs expires_at within a year), with a reason; the gate stops blocking on that rule in that file and names the disposition on every run it lets through, and the finding stays scanned and recorded. Use this for a reviewed false positive instead of adding an inline nosemgrep. A CRITICAL finding is refused. Reversible: revoke_security_disposition reopens the findings.

  ConnectorOAuth

• mark_unsubscribedA

  Proxy Mail QAA

  Records that the address unsubscribed from a sender, after you did it in your own browser or in the app (Proxy Mail QA never opens unsubscribe links). From then on, any marketing email from that sender fails after_unsubscribe in check_email and shows in check_unsubscribe, however long after. Name the sender with email_id (the email you unsubscribed from, from count_emails) or service (a name or domain, such as acme.com); with neither, the newest marketing email decides. Pass at for an unsubscribe that happened earlier. Marking twice is harmless. In Labs: works once the person who connected you switches on Marketing and offer emails in Account settings → Labs; until then it answers with an error that says so.

  ConnectorOAuth

• create_whatsapp_templateA

  LetsBotB

  Create a new WhatsApp message template and submit it to Meta for review (Official WhatsApp / Cloud API workspaces only). A template is the only way to start a conversation or message a customer outside the 24-hour reply window; once Meta APPROVES it, send it with send_template. Inputs: name (lowercase letters, digits and underscores; Meta registers it as "nt_<name>"), language (any language Meta accepts for templates, e.g. "ar", "en", "es", "pt", "fr", "de", "tr"), category, body, an example value for every body placeholder, and optionally a header (text, or an image/video/document with a public sample URL), a footer and buttons. Categories: UTILITY = a message about something the customer already started (order update, booking reminder, account notice) — no promotion; MARKETING = promotions, offers, announcements, re-engagement — billed per delivered message at Meta's marketing rate. Meta decides the final category and may RE-CATEGORISE a UTILITY template that contains promotional wording as MARKETING (billed as marketing). AUTHENTICATION (one-time passcodes) cannot be authored here — the panel's custom-template editor does not author it either. Placeholders: positional {{1}}, {{2}} … numbered from 1 without gaps, OR named {{customer_name}} (lowercase) — never both in one template; pass examples as {"1": "Sara"} or {"customer_name": "Sara"}. Consent gate: call with confirm=false first — nothing is saved or sent and you get the exact payload Meta will receive; show it to the user and only call again with confirm=true after they approve. Meta reviews a submitted template within minutes up to 24 hours; the result (APPROVED / REJECTED with Meta's reason) appears in list_whatsapp_templates. This tool does not edit or delete existing templates (use the WhatsApp templates page in the panel) and does not send any message.

  ConnectorOAuth

• update_ci_finding_statusA

  MarcoraA

  Update the status of a Context Intelligence finding — acknowledge it, dismiss it, or mark it resolved. When to use: the user has reviewed a finding (via list_ci_findings / get_ci_finding) and tells you their decision: "dismiss that one", "mark it handled", "acknowledge it for now". Status meanings: - acknowledged: seen, kept on the radar (still open). - dismissed: not relevant / won't fix — removes it from the actionable queue. - resolved: the underlying issue was fixed (records who resolved it and when). NOTE: this records the resolution only — it does NOT apply the suggested fix to the context item; applying fixes happens in the Marcora web app. Requires admin or editor role. Confirm with the user before dismissing or resolving a finding they haven't explicitly decided on. Errors: - Invalid status. Must be one of: acknowledged, dismissed, resolved. - Finding not found. / You do not have access to this finding.

  Connector

  Destructive

  OAuth

• apply_grounding_fixA

  MarcoraA

  Applies Marcora's recommended fix for one or more findings ("yes, do recommendation <id>"). This WRITES to the user's library or document, so read each finding's `suggested_fix` and confirm with the user before applying. When to use: the user has reviewed findings from `check_content_grounding` / `get_grounding_result` or from `list_ci_findings` (including health-audit recommendations from `trigger_health_audit_scan`) and wants them acted on. You never compose the fix yourself: pass `finding_ids`, and each finding's stored recommendation is applied. It is the same action as the Apply button in the Marcora UI: same permissions (admin or editor), same billing, same result. Where each fix lands: by default the context item named in that finding's `context_item_id`; a null `context_item_id` means the content document itself. Pass `context_item_overrides` to redirect a specific finding elsewhere (the UI's destination picker). **Asynchronous:** returns at once with one job per finding. Findings whose fixes land in the same document run together and share a `generation_id`: poll each distinct `generation_id` once with `get_generation_status`. Brand Foundation findings are not grouped. The honest outcome is `document_updated` there: true means the document changed, false means the recommendation was already covered and nothing was written. Report that distinction; don't assume every applied fix changed something. **Partial success is normal:** findings that could not start come back in `errors[]` with a reason while the rest run. Check both `jobs[]` and `errors[]`. Serves BOTH families of finding on the shared substrate: content-grounding findings (from a grounding scan) and Context Intelligence health-audit recommendations (from trigger_health_audit_scan). One tool for both. For a shared `generation_id`, `document_updated` covers every finding in that run. **Errors:** - Missing param: finding_ids (400). Pass finding_id values from a prior findings response. - InputError: finding_ids must be finding_id UUIDs (400). - InputError: context_item_overrides names a finding not in finding_ids (400). The override would be ignored, so it is rejected rather than silently dropped. - You are not authorized to perform this action (403). Applying requires an admin or editor role. - This finding is not a content grounding finding / has already been resolved (400). Per finding, surfaced in errors[]. - Marcora is already updating this document. Per finding, surfaced in errors[]: another run on that document (for example the user's own Content Assistant request, or an earlier apply_grounding_fix call) is still in progress. Wait for it to finish, then retry those findings.

  Connector

  Destructive

  OAuth

• get_service_packagesA

  Clutch.coA

  Use this tool when the user wants to see service packages with fixed pricing and scope for a specific type of service. This tool returns standardized packages offered by service providers, including pricing tiers, deliverables, and delivery timelines. Do NOT use this tool for custom project questions (e.g. "How much would it cost to build a custom app?"). It only returns providers' pre-defined, fixed-price packages, not a quote tailored to a specific project; use recommend_service_providers for those needs instead. Examples: - "Show me SEO packages" -> service="SEO" - "What web design packages can I get for $5,000?" -> service="Web Design", budget=5000 - "Marketing packages from agencies in New York" -> service="Digital Marketing", location="New York" Use `page`/`limit` for pagination.

  ConnectorOAuth

• join_marketing_programA

  Real Real GenuineB

  [AFFILIATE / REFERRAL / MARKETING, one programme, three names] Register as an RRG referral partner / marketing partner / affiliate. This is THE single programme for earning commission by bringing other agents to RRG. Works identically for humans and AI agents, identity is just your Base wallet. Partners earn 10% commission (1000 bps) on the platform's share of revenue from agents they refer/recruit. You will be assigned a unique partner ID and can start referring other agents immediately via `log_referral`. Requirements: a Base wallet address and an optional ERC-8004 agent ID.

  ConnectorNo auth

• join_marketing_programA

  Real Real GenuineB

  [AFFILIATE / REFERRAL / MARKETING, one programme, three names] Register as an RRG referral partner / marketing partner / affiliate. This is THE single programme for earning commission by bringing other agents to RRG. Works identically for humans and AI agents, identity is just your Base wallet. Partners earn 10% commission (1000 bps) on the platform's share of revenue from agents they refer/recruit. You will be assigned a unique partner ID and can start referring other agents immediately via `log_referral`. Requirements: a Base wallet address and an optional ERC-8004 agent ID.

  ConnectorNo auth

• earlywire_whats_newA

  Earlywire — Marketing & Growth IntelligenceA

  Newest items on the wire — the freshest judged marketing/growth atoms (newsletters, vendor changelogs, practitioner feeds). Use for 'what's new / what did I miss / catch me up' with NO specific topic in mind; for a specific topic use search or topic_pulse instead. Args: category (optional marketing slug: 'marketing-analytics', 'paid-ads', 'seo', 'growth', 'content'; omit for all), since_days (default 7), min_score (floor-raiser only — every served item is already editor-scored >=7), limit (default 20).

  ConnectorNo auth

• generate_contentA

  TrendIdeaA

  Generate ready-to-use marketing and business content for an idea: blog posts, social media, ad copy, press releases, elevator pitches and 12 more types. Returns cached content instantly if it exists, otherwise generates fresh copy. Spends credits only when generating new content. Not read-only; pass an ideaId you own and a contentType.

  ConnectorNo auth

• list_resourcesA

  flootA

  List the env vars a project's code can use and the resources behind them: (1) resources CONNECTED to the project — usable as process.env.<NAME> in endpoint code now; (2) the owner's other account-level credentials — reusable, but not usable in code until connected; (3) everything Floot can add. Call it to learn what env vars exist before writing backend code, and BEFORE provisioning or requesting any credential (the owner may already have the one you need). Pass query (case-insensitive substring over names, descriptions, types, and env var names) to filter when the account has many resources. Read-only. Details: get_guides('resources').

  ConnectorOAuth

• get_finding_remediationA

  RoutebaseA

  Get remediation advice for a single finding as GitHub-flavored markdown. When AI Assist is enabled and within budget this is a suggestion written for this exact finding; otherwise it falls back to the static guidance-library text and says so in 'source'. Unlike the other reads this one can spend AI budget, which is why it is a separate tool. Use this for advice on one finding; for the whole library use list_security_guidance. Requires project context.

  ConnectorAPI key