Skip to main content
hc
Submit
skillsFirst-partyReview first Safety ✓ Privacy ✓

MCP Server Authoring Security Capability Pack Skill

Expert MCP capability skill for secure server authoring, tool schema discipline, authorization boundaries, and prompt-injection risk review.

by JSONbored·added 2026-04-10·
Claude CodeCodexWindsurfGeminiCursorCLI
HarnessClaude CodeCodexWindsurfGeminiCursorCLI
Level:expertType:capability-packVerified:validated
Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL
https://heyclau.de/entry/skills/mcp-server-authoring-security-capability-pack
Source URLs
https://modelcontextprotocol.io/docs/tutorials/security/security_best_practices, https://github.com/JSONbored/awesome-claude/blob/main/content/skills/mcp-server-authoring-security-capability-pack.mdx
Package URL
/downloads/skills/mcp-server-authoring-security-capability-pack.zip
Package SHA256
88cfe7f7cbd688806926439fcef04929c691deaaa01909a87d5658bbeb8c28bb
Safety notes
Use the skill as a review and implementation checklist; do not deploy MCP auth, credential flow, or permission changes without human review., Validate tool schemas, authorization decisions, and logging behavior with tests before exposing an MCP server to real users or external clients., Treat generated threat models as incomplete until checked against current MCP security and authorization docs.
Privacy notes
Tool inventories, auth flows, logs, incident examples, prompts, and server code shared with this skill may enter model context., Redact access credentials, client secrets, user records, tenant identifiers, and production request bodies before using them as examples.
Platform compatibility
claude-code (native-skill), codex (native-skill), windsurf (native-skill), gemini (native-skill), cursor (adapter), cli (manual-context)
Author
JSONbored
Claim status
unclaimed
Last verified
2026-04-10

Decision playbook

Ready to evaluate for your workflow

Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.

Compare context
Selected

0

Current score

96

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done

  • Source provenance statusRequired

    Marked as first-party.

    Done

  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done

  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done

  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Complete

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done

  • Package verification flag

    Package marked verified.

    Done

  • Checksum metadata

    SHA-256 hash is present.

    Done

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending

  • Baseline comparison available

    No baseline peer selected yet.

    Pending

  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Package install

Copy-ready — paste the snippet to get started.

Install command

Provided

Config snippet

Not provided

Copy snippet

Provided

Prerequisites

3 to clear

Platforms

6 listed

Difficulty

90/100

Adoption plan

Balanced adoption plan

Current risk score 0/100. Use staged verification before broader rollout.

Risk 0

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done

  • Confirm metadata review state

    Listing has review metadata.

    Done

  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done

  • Review privacy notesRequired

    Privacy notes are present.

    Done

  • Verify package integrity metadata

    Package verification/checksum metadata is available.

    Done

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending

  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending

  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (6/6 signals complete).

Risk 0

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Present

Package integrity metadata is present.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

6/6 steps complete with no blocking gaps for this preset.

Risk 0

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is available.

Done

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

3 prerequisites to line up before setup.

0/3 ready
General3

Safety & privacy surface

Safety & privacy surface

3 safety and 2 privacy notes across 3 risk areas. Review closely: credentials & tokens, permissions & scopes.

3 areas
  • SafetyCredentials & tokensUse the skill as a review and implementation checklist; do not deploy MCP auth, credential flow, or permission changes without human review.
  • SafetyPermissions & scopesValidate tool schemas, authorization decisions, and logging behavior with tests before exposing an MCP server to real users or external clients.
  • SafetyPermissions & scopesTreat generated threat models as incomplete until checked against current MCP security and authorization docs.
  • PrivacyData retentionTool inventories, auth flows, logs, incident examples, prompts, and server code shared with this skill may enter model context.
  • PrivacyCredentials & tokensRedact access credentials, client secrets, user records, tenant identifiers, and production request bodies before using them as examples.

Safety notes

  • Use the skill as a review and implementation checklist; do not deploy MCP auth, credential flow, or permission changes without human review.
  • Validate tool schemas, authorization decisions, and logging behavior with tests before exposing an MCP server to real users or external clients.
  • Treat generated threat models as incomplete until checked against current MCP security and authorization docs.

Privacy notes

  • Tool inventories, auth flows, logs, incident examples, prompts, and server code shared with this skill may enter model context.
  • Redact access credentials, client secrets, user records, tenant identifiers, and production request bodies before using them as examples.

Prerequisites

  • MCP server implementation or design draft
  • Tool inventory and expected consumers
  • Logging/alerting sink for security events

Schema details

Install type
package
Reading time
9 min
Difficulty score
90
Troubleshooting
Yes
Breaking changes
No
Package metadata
Package verified
Yes
SHA-256
88cfe7f7cbd688806926439fcef04929c691deaaa01909a87d5658bbeb8c28bb
Skill and platform metadata
Skill type
capability-pack
Skill level
expert
Verification
validated
Verified at
2026-04-10
Retrieval sources
https://modelcontextprotocol.io/docs/tutorials/security/security_best_practiceshttps://modelcontextprotocol.io/docs/tutorials/security/authorizationhttps://modelcontextprotocol.io/specification/2025-06-18/basic/authorizationhttps://modelcontextprotocol.io/specification/2025-06-18/server/toolshttps://modelcontextprotocol.io/specification/2025-06-18
Tested platforms
ClaudeCodexOpenClawCursorWindsurfGemini
PlatformSupportInstall path
claude-codeNative.claude/skills/<skill-name>/SKILL.md
codexNative.agents/skills/<skill-name>/SKILL.md
windsurfNative.windsurf/skills/<skill-name>/SKILL.md
geminiNative.gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md
cursorAdapter.cursor/rules/<skill-name>.mdc
cliManualAGENTS.md or tool-specific context file
Full copyable content
# Trigger
"Apply the MCP server authoring security capability pack to this server."

# Required output
1) Threat model and trust boundaries
2) Tool schema and validation contracts
3) Auth and permission architecture
4) Abuse and incident response controls

About this resource

Knowledge Freshness

This capability pack is pinned to documentation re-verified on 2026-06-19. When upstream docs change, refresh endpoint contracts, examples, and constraints before using this skill for production changes.

Retrieval Sources

Always prefer direct retrieval from official docs/API references over model memory for limits, endpoint signatures, and behavior guarantees.

Source Verification Notes

Verified on 2026-06-19:

  • The MCP security best-practices page explicitly covers MCP-specific risks and mitigations including confused deputy flows, credential boundary mistakes, SSRF, session integrity risks, local server compromise, and scope minimization.
  • The MCP authorization docs and 2025-06-18 authorization specification describe OAuth-based authorization patterns, protected resource metadata, credential handling, and discovery expectations for protected MCP servers.
  • The MCP tools specification defines server-exposed tools and their schema metadata. This skill turns those source-backed concerns into a reusable review and implementation checklist; it is not itself an official MCP specification.

Core Workflow

  1. Confirm target version/runtime and pull latest official docs for the task scope.
  2. Build an execution plan with explicit read-only discovery before any mutation.
  3. Validate contracts, permissions, and safety constraints before applying changes.
  4. Execute with deterministic checkpoints and rollback criteria.
  5. Produce a verification report with evidence, caveats, and next actions.

Overview

This capability pack teaches agents how to design MCP servers that remain safe under real adversarial conditions. It emphasizes least privilege, explicit contracts, and secure default behavior.

Capability Scope

  • Threat modeling for tool invocation flows
  • Input validation and schema hardening
  • AuthN/AuthZ boundaries for tools and resources
  • Prompt-injection, session integrity, and data exposure risk review
  • Audit logging and incident response readiness

Compatibility

Native

  • Claude Code / Claude: native skill usage via SKILL.md.
  • Codex/OpenAI workflows: compatible with Agent Skills-style SKILL.md content as reusable workflow instructions.

Manual Adaptation

  • Gemini CLI: native skill usage via .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md where supported.
  • Cursor: use the generated .cursor/rules/*.mdc adapter for project rules.
  • OpenClaw and similar agents: use the same skill content as a reusable prompt/workflow file when native skill import is unavailable.

Production Rules

  • Validate all tool input before execution.
  • Scope each tool to minimal permissions.
  • Deny by default for unsafe/unknown operations.
  • Preserve immutable audit trails for sensitive invocations.

Troubleshooting

Issue: Tool abuse through crafted prompts
Fix: Add policy layer between prompt interpretation and tool invocation.

Issue: Schema drift breaks clients
Fix: Enforce contract tests and backward compatibility checks.

Issue: Difficult to investigate incidents
Fix: Add structured event logs with actor/tool/input/result correlation.

Output Contract

  1. Provide an implementation plan ordered by risk and dependency.
  2. Provide exact production-ready config/commands with no placeholders.
  3. Call out secrets, permissions, and least-privilege requirements.
  4. Include rollback and recovery guidance for each risky step.

Validation Checklist

  • Verify all referenced docs/versions before applying changes.
  • Run regression checks for core user flow and error paths.
  • Confirm observability/logging is enabled for changed components.
  • Confirm security controls (auth, rate limits, input validation) still pass.
  • Record final known limitations and follow-up actions.
#mcp#security#server-authoring#tools#capability-pack

Source citations

Add this badge to your README

Show that MCP Server Authoring Security Capability Pack Skill is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/skills/mcp-server-authoring-security-capability-pack.svg)](https://heyclau.de/entry/skills/mcp-server-authoring-security-capability-pack)

How it compares

MCP Server Authoring Security Capability Pack Skill side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).

Next steps differ across entries — use the actions in the table below to copy install commands and source links per resource.

Field
MCP Server Authoring Security Capability Pack Skill

Expert MCP capability skill for secure server authoring, tool schema discipline, authorization boundaries, and prompt-injection risk review.

Open dossier
MCP OAuth Server Hardening Capability Pack Skill

Expert MCP OAuth server hardening capability pack applying documented Dynamic Client Registration, oauth.scopes pins, callback ports, keychain token storage, and least-privilege scope review from official MCP documentation.

Open dossier
MCP Tool Contract Testing Skill

Validate MCP server tools with contract-style tests to catch schema drift, unsafe behavior, and integration regressions early.

Open dossier
MCP Server Security Hardening Skill

Secure MCP servers with strict tool boundaries, auth controls, dependency hygiene, and abuse-resistant runtime policies.

Open dossier
Next stepsDiffers
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustDiffersPackage verified2026-04-10Package not verifiedPackage verified2026-04-10Package verified2026-04-10
Source provenanceDiffersSource-backedSubmission linkedSource submissionNo submission linkNo submission link
SubmitterDiffers—kiannidev——
Install riskReview firstReview firstLow riskLow risk
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Brand————
Categoryskillsskillsskillsskills
Sourcefirst-partysource-backedfirst-partyfirst-party
AuthorJSONboredkiannidevJSONboredJSONbored
Added2026-04-102026-06-162026-04-102026-04-10
Platforms
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Source repo————
Safety notes✓Use the skill as a review and implementation checklist; do not deploy MCP auth, credential flow, or permission changes without human review. Validate tool schemas, authorization decisions, and logging behavior with tests before exposing an MCP server to real users or external clients. Treat generated threat models as incomplete until checked against current MCP security and authorization docs.✓Autonomous runs can execute tools without mid-run user input—scope paths and connectors first. Do not enable destructive automation without explicit approval gates. Review outputs as draft until a human validates evidence.✓Use this skill as planning or review guidance; verify generated commands, code, configuration, and infrastructure changes before running them. Apply least-privilege credentials and test in staging or a disposable branch before using it on production systems, CI, deployment, or account-write workflows.✓Treat findings and generated mitigations as review inputs; validate suspected vulnerabilities and patches before changing production controls. Coordinate disclosure-sensitive security work privately and avoid running destructive probes outside authorized systems.
Privacy notes✓Tool inventories, auth flows, logs, incident examples, prompts, and server code shared with this skill may enter model context. Redact access credentials, client secrets, user records, tenant identifiers, and production request bodies before using them as examples.✓Run output may contain proprietary code and credentials. Summaries for external channels require redaction.✓Inputs can include source files, prompts, logs, account metadata, repository details, and operational context that may be sent to the configured AI model. Redact secrets, customer data, private URLs, credentials, and proprietary implementation details before sharing prompts, reports, or generated artifacts.✓Security prompts and reports can include source snippets, vulnerability details, internal URLs, dependency metadata, and operational context. Redact secrets, customer data, exploit details, private infrastructure names, and unreleased findings before sharing outputs publicly.
Prerequisites
  • MCP server implementation or design draft
  • Tool inventory and expected consumers
  • Logging/alerting sink for security events
  • Claude Code version and plan eligibility per official documentation.
  • Team policy for autonomous or shared automation workflows.
  • Staging environment for safe validation.
  • Human owner for production rollout approval.
  • MCP server implementation and tool catalog
  • Staging environment for test execution
  • Known expected outputs per critical tool
  • Existing MCP server implementation (local or remote)
  • Access to server config, dependency manifest, and deployment settings
  • Ability to run integration tests after hardening
Install
curl -L https://heyclau.de/downloads/skills/mcp-server-authoring-security-capability-pack.zip -o mcp-server-authoring-security-capability-pack.zip && unzip -o mcp-server-authoring-security-capability-pack.zip -d ./mcp-server-authoring-security-capability-pack
—
curl -L https://heyclau.de/downloads/skills/mcp-tool-contract-testing.zip -o mcp-tool-contract-testing.zip && unzip -o mcp-tool-contract-testing.zip -d ./mcp-tool-contract-testing
curl -L https://heyclau.de/downloads/skills/mcp-server-security-hardening.zip -o mcp-server-security-hardening.zip && unzip -o mcp-server-security-hardening.zip -d ./mcp-server-security-hardening
Config————
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Source-backed guides for putting this to work.

guides

Build MCP Servers with Auth and Least Privilege

Design MCP servers with auth boundaries and narrow tools.

Review firstSource-backedReview firstAdded 1mo ago
Safety ✓ Privacy ✓by MkDev11
guides

Prompt Injection Defense For Tool Connected Agents

Reduce prompt injection risk for MCP and tool-connected Claude Code agents.

Review firstSource-backedReview firstAdded 28d ago
Safety ✓ Privacy ✓by kiannidev
guides

Threat Model MCP Servers Before Installation

Review MCP server trust boundaries before connecting them to Claude.

Review firstSource-backedReview firstAdded 1mo ago
Safety ✓ Privacy ✓by MkDev11

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.