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.
npx agentmods add rules/netlify/context-and-tools/netlify-mcp-servers-authenticationgit clone --depth 1 https://github.com/netlify/context-and-toolsWrote 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/netlify/context-and-tools/netlify-mcp-servers-authentication)<a href="https://agentmods.dev/rules/netlify/context-and-tools/netlify-mcp-servers-authentication"><img src="https://agentmods.dev/badge/rules/netlify/context-and-tools/netlify-mcp-servers-authentication.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.01062 |
| Opus 5 | $0.00008 | $0.00531 |
| Sonnet 5 | $0.00003 | $0.00212 |
| Haiku 4.5 | $0.00002 | $0.00106 |
Grade A, and why
netlify-mcp-servers-authentication 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Server Authentication
Two models. Pick based on who calls the server. Both put Authorization: Bearer <token> on every request and 401 anything that fails.
Model 1 — single shared secret (personal / single-user)
One token in an env var, compared in constant time. This is the whole thing — see checkBearer in the main SKILL. Generate with openssl rand -hex 32, store as a secret env var, hand the same token to your one client. To rotate or revoke: set a new value and update the client.
Use this when the server is just for you (or one trusted script). Don't reach for anything heavier than this until you actually have multiple users.
Model 2 — per-user API keys (multi-user)
Each person authenticates as themselves with their own revocable key. Netlify Identity protects a web UI where users mint keys; the MCP endpoint itself is authenticated by the key, not by an Identity session (agents have no browser cookie). The two systems are separate on purpose.
Store keys in Netlify Database. The essential rules:
- Never store the plaintext key. Store a SHA-256 hash plus a short non-secret prefix for display.
- Show the plaintext exactly once, at creation. If the user loses it, they mint a new one.
- Tie each key to a user and support revocation (soft-delete) so a leaked key is killable without touching others.
A workable row shape:
api_keys
id uuid
user_email text -- who this key acts as
label text -- "laptop", "ci", etc.
prefix text -- first ~11 chars, safe to display
key_hash text unique -- sha256(plaintext), hex
created_at timestamptz
last_used_at timestamptz
revoked_at timestamptz -- null = active
Generate
import { createHash, randomBytes } from "node:crypto";
export function generateApiKey() {
const plaintext = `mk_${randomBytes(24).toString("base64url")}`;
return {
plaintext, // return to the user ONCE
prefix: plaintext.slice(0, 11), // store + display
keyHash: createHash("sha256").update(plaintext).digest("hex"), // store
};
}
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.
- 5d ago First seen · 89 lines · 16 tokens per session scan A 81a390ca9085
netlify-mcp-servers-authentication is a cursor rule published in the GitHub repository netlify/context-and-tools (36 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 1,062 once invoked, about $0.0001 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-30.
Other cursor rules, from other repositories
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.
cli-error-handling
CLI command error handling patterns.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.