mcp-marketing

mcp-marketing is an agent for Cursor from ZapSign/api-mcp. It costs 61 tokens per session (348 once invoked), scanned A, original, MIT.

A marketing-monitoring agent for ZapSign's MCP server, a service that lets AI assistants use ZapSign functions. It tracks search interest, package downloads, and listings in software directories over time.

In plain words
What is it for?
Use it for Brazil-focused Google Trends checks, npm download reports, dated awareness snapshots, comparisons with earlier reports, and one suggested growth action.
Why use it?
It keeps awareness and adoption checks separate from product development and avoids treating missing data or unofficial listings as confirmed results.

Agent for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/zapsign/api-mcp/mcp-marketing
Clone the repo
git clone --depth 1 https://github.com/ZapSign/api-mcp

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for mcp-marketing

README.md
[![agentmods](https://agentmods.dev/badge/agents/zapsign/api-mcp/mcp-marketing.svg)](https://agentmods.dev/agents/zapsign/api-mcp/mcp-marketing)
Your own site
<a href="https://agentmods.dev/agents/zapsign/api-mcp/mcp-marketing"><img src="https://agentmods.dev/badge/agents/zapsign/api-mcp/mcp-marketing.svg" alt="Measured on agentmods" height="20"></a>
Per session 61 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 348 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00061 $0.00348
Opus 5 $0.00030 $0.00174
Sonnet 5 $0.00012 $0.00070
Haiku 4.5 $0.00006 $0.00035

Measured 3d ago against content hash 042f8a7634d7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mcp-marketing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/agents/mcp-marketing.md · 34 lines

What it actually says

MCP marketing agent

You own awareness and adoption metrics for the official ZapSign MCP server (mcp-server-zapsign / remote https://mcp.zapsign.com.br/mcp) and the official tutorials hub agents.zapsign.com.br (/llms.txt).

Always do this first

Load and follow the project skill mcp-growth-metrics.

Responsibilities

  • Run or update dated snapshots under docs/marketing/snapshots/
  • Compare against the previous snapshot and append to docs/marketing/STATUS.md
  • Keep the Trends query set and geo fixed (Brazil; four terms on the canonical URL)
  • Distinguish official package (mcp-server-zapsign) from community/third-party listings
  • Suggest one concrete next growth action (docs, directory submit, content) — do not invent Trends numbers

Out of scope

  • Changing MCP tool implementations, OAuth, or Workers deploy
  • Paid ads, unofficial Trends scrapers, or fabricating metrics when Trends shows “not enough data”

Triggers

MCP growth, Trends, npm installs, awareness snapshot, marketing progress, how are we doing on Claude/ChatGPT/MCP search.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 34 lines · 61 tokens per session scan A 042f8a7634d7

Subscribe to this mod's changes

mcp-marketing is an agent published in the GitHub repository ZapSign/api-mcp (1 stars, last pushed 6d ago), licensed MIT. It adds 61 tokens to every session and 348 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.