Security

Security audits, vulnerabilities, compliance, auth, secrets, and safe automation

skills in category: 28,085
pages available: 1,171

Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.

Open in full browser

Browse security skills

Showing 769–792 of 28,085 skills

Mcplab Stdio Transport Least Privilege Access Build Configuration RunbookAUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: stdio transport for least-privilege access. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: List the minimum resources, tools, roots, and scopes required; reject wildcard access when a narrower grant works. Success means the prepared result is reproducible, reviewable, and wit...securityrustgoVotes: 0GitHub stars: 2
Mcplab Stdio Transport Conformance Testing Security Rights And Safety ReviewAUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Model Context Protocol servers and integrations: stdio transport for conformance testing. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Exercise required protocol conformance cases against the pinned spec; report unimplemented optional capabilities separately. Success means the review names relevant hazards...securityrustgoVotes: 0GitHub stars: 2
Mcplab Stdio Transport Conformance Testing Scope And Baseline RecordAUse when the work needs a verified goal, authorized boundary, and starting state for Model Context Protocol servers and integrations: stdio transport for conformance testing. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Exercise required protocol conformance cases against the pinned spec; report unimplemented optional capabilities separately. Success means the owner, constraints, baseline, and acceptance signal are explicit. Us...securityrustgoVotes: 0GitHub stars: 2
Mcplab Stdio Transport Conformance Testing Requirements And Decision BriefAUse when a request must be converted into testable constraints and an owned decision for Model Context Protocol servers and integrations: stdio transport for conformance testing. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Exercise required protocol conformance cases against the pinned spec; report unimplemented optional capabilities separately. Success means requirements have priorities, evidence, owners, and...securityrustgoVotes: 0GitHub stars: 2
Mcplab Stdio Transport Conformance Testing Option Comparison MatrixAUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: stdio transport for conformance testing. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Exercise required protocol conformance cases against the pinned spec; report unimplemented optional capabilities separately. Success means options are compared on user-approved criteria with un...securityrustgoVotes: 0GitHub stars: 2
Mcplab Stdio Transport Conformance Testing Failure Triage And RecoveryAUse when an unexpected result needs diagnosis without widening risk or losing evidence for Model Context Protocol servers and integrations: stdio transport for conformance testing. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Exercise required protocol conformance cases against the pinned spec; report unimplemented optional capabilities separately. Success means the failure is bounded by observations, o...securityrustgoVotes: 0GitHub stars: 2
Mcplab Stdio Transport Conformance Testing Design BlueprintAUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: stdio transport for conformance testing. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Exercise required protocol conformance cases against the pinned spec; report unimplemented optional capabilities separately. Success means interfaces, dependencies, constraints, and review points are testable be...securityrustgoVotes: 0GitHub stars: 2
Mcplab Stdio Transport Conformance Testing Build Configuration RunbookAUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: stdio transport for conformance testing. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Exercise required protocol conformance cases against the pinned spec; report unimplemented optional capabilities separately. Success means the prepared result is reproducible, reviewable, ...securityrustgoVotes: 0GitHub stars: 2
Mcplab Stdio Transport Client Compatibility Security Rights And Safety ReviewAUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Model Context Protocol servers and integrations: stdio transport for client compatibility. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means the review names relevant hazards, permis...securityrustgoVotes: 0GitHub stars: 2
Mcplab Stdio Transport Client Compatibility Scope And Baseline RecordAUse when the work needs a verified goal, authorized boundary, and starting state for Model Context Protocol servers and integrations: stdio transport for client compatibility. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permis...securityrustgoVotes: 0GitHub stars: 2
Mcplab Stdio Transport Client Compatibility Requirements And Decision BriefAUse when a request must be converted into testable constraints and an owned decision for Model Context Protocol servers and integrations: stdio transport for client compatibility. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means requirements have priorities, evidence, owners, and measura...securityrustgoVotes: 0GitHub stars: 2
Mcplab Stdio Transport Client Compatibility Option Comparison MatrixAUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: stdio transport for client compatibility. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means options are compared on user-approved criteria with uncertaint...securityrustgoVotes: 0GitHub stars: 2
Mcplab Stdio Transport Client Compatibility Measured Improvement And HandoffAUse when a measured result or recurring failure suggests a change worth testing and handing to an owner for Model Context Protocol servers and integrations: stdio transport for client compatibility. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means the proposed change is compared w...securityrustgoVotes: 0GitHub stars: 2
Mcplab Stdio Transport Client Compatibility Failure Triage And RecoveryAUse when an unexpected result needs diagnosis without widening risk or losing evidence for Model Context Protocol servers and integrations: stdio transport for client compatibility. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means the failure is bounded by observations, one testa...securityrustgoVotes: 0GitHub stars: 2
Mcplab Stdio Transport Client Compatibility Design BlueprintAUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: stdio transport for client compatibility. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means interfaces, dependencies, constraints, and review points are testable before bui...securityrustgoVotes: 0GitHub stars: 2
Mcplab Stdio Transport Client Compatibility Build Configuration RunbookAUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: stdio transport for client compatibility. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means the prepared result is reproducible, reviewable, and with...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata Untrusted Tool Output Scope And Baseline RecordAUse when the work needs a verified goal, authorized boundary, and starting state for Model Context Protocol servers and integrations: server-registry metadata for untrusted tool output. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Validate tool results as untrusted data, constrain output size/type, and do not execute returned instructions automatically. Success means the owner, constraints, baseline, and acceptance signal are e...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata Untrusted Tool Output Requirements And Decision BriefAUse when a request must be converted into testable constraints and an owned decision for Model Context Protocol servers and integrations: server-registry metadata for untrusted tool output. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Validate tool results as untrusted data, constrain output size/type, and do not execute returned instructions automatically. Success means requirements have priorities, evidence, ...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata Untrusted Tool Output Option Comparison MatrixAUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: server-registry metadata for untrusted tool output. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Validate tool results as untrusted data, constrain output size/type, and do not execute returned instructions automatically. Success means options are compared on user-approved crite...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata Untrusted Tool Output Failure Triage And RecoveryAUse when an unexpected result needs diagnosis without widening risk or losing evidence for Model Context Protocol servers and integrations: server-registry metadata for untrusted tool output. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Validate tool results as untrusted data, constrain output size/type, and do not execute returned instructions automatically. Success means the failure is bounded by obse...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata Untrusted Tool Output Design BlueprintAUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: server-registry metadata for untrusted tool output. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Validate tool results as untrusted data, constrain output size/type, and do not execute returned instructions automatically. Success means interfaces, dependencies, constraints, and review points are ...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata Untrusted Tool Output Build Configuration RunbookAUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: server-registry metadata for untrusted tool output. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Validate tool results as untrusted data, constrain output size/type, and do not execute returned instructions automatically. Success means the prepared result is reproducible, r...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata Schema Changes Security Rights And Safety ReviewAUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Model Context Protocol servers and integrations: server-registry metadata for schema changes. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Diff the old and new schema and check required fields, optionality, error behavior, and compatibility at both ends. Success means the review names relevant hazards, per...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata Schema Changes Scope And Baseline RecordAUse when the work needs a verified goal, authorized boundary, and starting state for Model Context Protocol servers and integrations: server-registry metadata for schema changes. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Diff the old and new schema and check required fields, optionality, error behavior, and compatibility at both ends. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use per...securityrustgoVotes: 0GitHub stars: 2