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.
git clone --depth 1 https://github.com/ZapSign/api-mcpWrote 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.
[](https://agentmods.dev/rules/zapsign/api-mcp/zapsign-mcp-project)<a href="https://agentmods.dev/rules/zapsign/api-mcp/zapsign-mcp-project"><img src="https://agentmods.dev/badge/rules/zapsign/api-mcp/zapsign-mcp-project/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/zapsign/api-mcp/zapsign-mcp-project"><img src="https://agentmods.dev/badge/rules/zapsign/api-mcp/zapsign-mcp-project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00507 | $0.00507 |
| Opus 5.5 | $0.00203 | $0.00203 |
| Sonnet 5.5 | $0.00101 | $0.00101 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
zapsign-mcp-project 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 1mo 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.
What it actually says
ZapSign MCP Server — Project Context
Key Context (read before ANY task)
- @file AGENTS.md — Coding standards, dev commands, task protocol, and commit convention
- The assigned task, issue, or pull request — Scope, acceptance criteria, dependencies, and blockers
- Relevant code, tests, and documentation — Current contract for the affected area
Architecture Summary
Remote MCP server: Claude AI → OAuth 2.1 (Cloudflare OAuthProvider) → ZapSign API v1. Stack: TypeScript strict, Cloudflare Workers, @modelcontextprotocol/sdk ^1.27.0, agents 0.6.0. 12 tools across 3 domains: documents (5), signers (4), templates (3).
Key References (fetch when implementing MCP or auth features)
- MCP spec (2025-06-18): https://modelcontextprotocol.io/specification/2025-06-18
- MCP SDK V1 API: https://github.com/modelcontextprotocol/typescript-sdk/tree/v1.x
- Cloudflare OAuthProvider: https://github.com/cloudflare/workers-oauth-provider
- Cloudflare Agents SDK: https://developers.cloudflare.com/agents/api-reference/mcp-handler-api/
- ZapSign API docs: https://docs.zapsign.com.br/english
- ZapSign auth (API token): https://docs.zapsign.com.br/english/authentication
- ZapSign create doc: https://docs.zapsign.com.br/english/documentos/criar-documento
- ZapSign signers: https://docs.zapsign.com.br/english/signatarios
- ZapSign templates: https://docs.zapsign.com.br/english/templates
- ZapSign environments: https://docs.zapsign.com.br/english/zapsign-environments
- Anthropic directory submission: https://support.claude.com/en/articles/12922490-remote-mcp-server-submission-guide
Before Implementing ANY Task
- Read AGENTS.md and the assigned task before inspecting or changing code
- Record a focused failing test or executable evidence check before making a change
- Follow the checkpoint protocol after completing the task
- Do not run tests against the real ZapSign API unless the task explicitly authorizes them and the sandbox preflight passes
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.
- 1mo ago First seen · 36 lines · 507 tokens per session scan A c010789081bd
zapsign-mcp-project is a cursor rule published in the GitHub repository ZapSign/api-mcp (1 stars, last pushed 7d ago), licensed MIT. It adds 507 tokens to every session, about $0.0020 per session on Opus 5.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.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).