api-auth

api-auth is a skill for Claude Code from cyanheads/tmdb-mcp-server. It costs 58 tokens per session (2,877 once invoked), scanned A, a copy of api-auth, Apache-2.0.

Authentication and access-control patterns for tools and resources in the @cyanheads/mcp-ts-core framework. Authentication checks who is calling, while authorization checks what that caller is allowed to use.

In plain words
What is it for?
Use it to require scopes on tools or resources, configure authentication modes, check permissions that depend on input, and pass a tenant ID through request context.
Why use it?
It removes the need to implement common permission checks separately in every handler. It also provides patterns for JWT or OAuth login, access scopes, and tenant-specific data.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the tmdb-mcp-server plugin — 33 skills, 1 MCP server shipped together

Good fit Use it to require scopes on tools or resources, configure authentication modes, check permissions that depend on input, and pass a tenant ID through request context.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cyanheads/tmdb-mcp-server/api-auth
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.

Any agent
npx skills add cyanheads/tmdb-mcp-server --skill api-auth
Clone the repo
git clone --depth 1 https://github.com/cyanheads/tmdb-mcp-server

Made for: Claude Code.

Or install tmdb-mcp-server, the plugin that ships this one along with the rest of its 33 skills, 1 MCP server.

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 api-auth

README.md
[![agentmods](https://agentmods.dev/badge/skills/cyanheads/tmdb-mcp-server/api-auth/github.svg)](https://agentmods.dev/skills/cyanheads/tmdb-mcp-server/api-auth)
Your own site
<a href="https://agentmods.dev/skills/cyanheads/tmdb-mcp-server/api-auth"><img src="https://agentmods.dev/badge/skills/cyanheads/tmdb-mcp-server/api-auth/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.

agentmods 80×15 button for api-auth

Your own site · 80×15
<a href="https://agentmods.dev/skills/cyanheads/tmdb-mcp-server/api-auth"><img src="https://agentmods.dev/badge/skills/cyanheads/tmdb-mcp-server/api-auth.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,877 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00058 $0.02877
Opus 5.5 $0.00023 $0.01151
Sonnet 5.5 $0.00012 $0.00575
Haiku 4.5 $0.00006 $0.00288

Measured 12d ago against content hash 58c9fe9d1b92, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

api-auth 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 12d 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 api-auth — 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.

framework-skills/api-auth/SKILL.md · 217 lines

How it starts

The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Overview

The framework handles auth at the handler factory level — tools and resources declare required scopes declaratively, and the framework enforces them before calling the handler. No try/catch or manual scope checking required for the common case.


Inline auth (primary pattern)

Declare required scopes directly on the tool or resource definition via the auth property. The handler factory checks ctx.auth.scopes against these before calling handler.

import { tool } from '@cyanheads/mcp-ts-core';

const myTool = tool('my_tool', {
  input: z.object({ query: z.string().describe('Search query') }),
  output: z.object({ result: z.string().describe('Search result') }),
  auth: ['tool:my_tool:read'],
  async handler(input, ctx) {
    // Only reached if caller has 'tool:my_tool:read' scope
  },
});

When MCP_AUTH_MODE=none, auth checks are skipped and defaults are allowed.

A failed check returns Forbidden (-32005, Insufficient permissions.) or, when auth is enabled but the request carries no auth context, Unauthorized (-32006). Neither carries data: the required, granted, and missing scope names stay in the server log, so a caller cannot enumerate scopes from the error.

The scope check logs a missing scope at warning, naming the missing scopes. On a tool, the call's Error in tool:<name> record follows at notice with no stack — the refusal is the caller's standing, not a fault in this server — and mcp.errors.classified counts it with mcp.error.severity: "notice". That holds for the inline check and for checkScopes in a handler alike, and the level is fixed: the refusal carries no data.reason, so no errors[] entry can set it. A missing auth context keeps its Error in tool: record at error, and so does a forbidden() the handler throws itself. A resource read the inline check refuses writes only the scope check's own records.


Dynamic auth

For runtime-computed scopes (e.g., scopes that depend on input values like a team or resource ID), use checkScopes from @cyanheads/mcp-ts-core/auth inside the handler:

Read the full file on GitHub · 217 lines

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. 12d ago Changed · +4 lines 58c9fe9d1b92
  2. 1mo ago First seen · 213 lines · 58 tokens per session scan A 5d676a9b6163

Subscribe to this mod's changes

api-auth is a skill published in the GitHub repository cyanheads/tmdb-mcp-server (1 stars, last pushed 3d ago), licensed Apache-2.0. It adds 58 tokens to every session and 2,877 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to api-auth, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

api-context

Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.clientCapabilities, ctx.enrich, ctx.content), and when to use each.

cyanheads/internet-archive-mcp-server · 84 tokens

api-errors

McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.

cyanheads/internet-archive-mcp-server · 54 tokens

api-config

Reference for core and server configuration in @cyanheads/mcp-ts-core. Covers env var tables with defaults, priority order, server-specific Zod schema pattern, and Workers lazy-parsing requirement.

cyanheads/internet-archive-mcp-server · 43 tokens

design-mcp-server

Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.

cyanheads/osv-advisory-mcp-server · 62 tokens

add-service

Scaffold a new service integration. Use when the user asks to add a service, integrate an external API, or create a reusable domain module with its own initialization and state.

cyanheads/internet-archive-mcp-server · 38 tokens

design-mcp-server

Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.

cyanheads/devops-status-mcp-server · 62 tokens