50-mcp-tools

A set of rules for retrieving outside information through connected tools. This includes requirements from task trackers, current code-hosting issues, live database details, and external documentation.

In plain words
What is it for?
Use it when a task depends on Jira, Linear, Trello, GitHub, GitLab, database schemas or data, or API references.
Why use it?
It prevents implementation based on missing or outdated context by requiring authoritative information first.

Cursor rule 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 rules/luxvil/ai-coding-rules/50-mcp-tools
Clone the repo
git clone --depth 1 https://github.com/Luxvil/ai-coding-rules

Made for: Cursor.

Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 109 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00016 $0.00109
Opus 5 $0.00008 $0.00055
Sonnet 5 $0.00003 $0.00022
Haiku 4.5 $0.00002 $0.00011

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

Security

Grade A, and why

50-mcp-tools 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 2d 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.

Origin

This is a copy

100% identical to 50-mcp-tools — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursor/rules/50-mcp-tools.mdc · 18 lines

What it actually says

MCP Usage

When to Use MCP

  • You need authoritative requirements (Jira/Linear/Trello).
  • You need current PR/issue context (GitHub/GitLab).
  • You need live schema or data (DB MCP).
  • You need external docs or API references.

Rule

  • Fetch missing context before implementing.
  • Cite the source of truth in notes.
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. 2d ago First seen · 18 lines · 16 tokens per session scan A fa26df5d2f2b

Subscribe to this mod's changes

50-mcp-tools is a cursor rule published in the GitHub repository Luxvil/ai-coding-rules (3 stars, last pushed 3d ago), licensed MIT. It adds 16 tokens to every session and 109 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to 50-mcp-tools, differing in 0 lines, and is treated as a copy.