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/adshaa/salla-mcp-serverWrote 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/adshaa/salla-mcp-server/mcp-server)<a href="https://agentmods.dev/rules/adshaa/salla-mcp-server/mcp-server"><img src="https://agentmods.dev/badge/rules/adshaa/salla-mcp-server/mcp-server/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/adshaa/salla-mcp-server/mcp-server"><img src="https://agentmods.dev/badge/rules/adshaa/salla-mcp-server/mcp-server.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.00023 | $0.01364 |
| Opus 5.5 | $0.00009 | $0.00546 |
| Sonnet 5.5 | $0.00005 | $0.00273 |
| Haiku 4.5 | $0.00002 | $0.00136 |
Grade A, and why
mcp-server 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- mcp-server — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Boilerplate Project Overview
This rule provides a guide to understanding the structure and core functionalities of the MCP Boilerplate project. It's designed to help you navigate and extend the boilerplate effectively.
Core Architecture
The project is a Cloudflare Worker that implements an MCP (Model Context Protocol) server with built-in support for user authentication and Stripe payments.
-
Main Entry Point:
src/index.ts- Initializes the
BoilerplateMCPagent, which extendsPaidMcpAgentfrom@stripe/agent-toolkit/cloudflare. - Sets up routing using Hono, handling the homepage (
@src/pages/index.html), payment success page (@src/pages/payment-success.html), and Stripe webhooks (@src/webhooks/stripe.ts). - Configures the
OAuthProviderfor handling authentication flows, defaulting to Google (@src/auth/google-handler.ts) but switchable to GitHub (@src/auth/github-handler.ts).
- Initializes the
-
Configuration:
wrangler.jsonc: Defines Cloudflare Worker settings, including Durable Objects (BoilerplateMCP), KV namespaces (OAUTH_KVfor storing OAuth related data), and compatibility flags.package.json: Lists project dependencies like@modelcontextprotocol/sdk,@stripe/agent-toolkit/cloudflare,hono,zod, and OAuth providers. It also contains scripts for development (dev) and deployment (deploy)..dev.vars(from@.dev.vars.example): Stores local development secrets and environment variables such as API keys for Google, GitHub, Stripe, andBASE_URL.
Tool Creation
MCP tools are defined in the src/tools/ directory. Each tool is typically in its own file and then exported via src/tools/index.ts to be registered in src/index.ts within the BoilerplateMCP.init() method.
- Free Tools:
- Defined using
agent.server.tool(). - Example:
@src/tools/add.ts(simple addition) and@src/tools/calculate.ts(more complex calculations). - Input parameters are validated using
zod.
- Defined using
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 · 80 lines · 23 tokens per session scan A 6a442d75b327
mcp-server is a cursor rule published in the GitHub repository adshaa/salla-mcp-server (7 stars, last pushed 6mo ago), licensed MIT. It adds 23 tokens to every session and 1,364 once invoked, about $0.0001 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
medusa-cursorrules
You are an expert senior software engineer specializing in modern web development, with deep expertise in TypeScript, Medusa, React.js, and TailwindCSS.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
hono-gateway
Hono gateway Worker rules - middleware order, shared @repo/hono-middleware exports, CORS/CSRF, errors, observability, validation, typing.
contracts
Zod DTO and enum contract rules - shared vs local shapes, layers, naming and type inference, schema authoring, additive changes.
testing
Vitest toolchain and testing discipline - two runtimes, no watch for agents, authoring gate, junk patterns.
service-bindings
Worker-to-Worker RPC - bindings.worker() by name, WorkerEntrypoint callee, typed RPC deferred, requestId propagation.