Is Pentesting Mcp Servers Checklist safe to use?

Pentesting Mcp Servers Checklist has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under CC-BY-4.0.

How do I install Pentesting Mcp Servers Checklist?

Pentesting Mcp Servers Checklist can be installed by cloning its GitHub repository and following the setup instructions in the README.

What AI clients work with Pentesting Mcp Servers Checklist?

Pentesting Mcp Servers Checklist is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse transport.

Is Pentesting Mcp Servers Checklist actively maintained?

Pentesting Mcp Servers Checklist is recently maintained — last commit was 43 days ago. It has 32 GitHub stars.

Pentesting Mcp Servers Checklist

Name: Pentesting Mcp Servers Checklist
Author: appsecco

by appsecco

A practical, community-driven checklist for pentesting MCP servers. Covers traffic analysis, tool-call behavior, namespace abuse, auth flows, and remote server risks. Maintained by Appsecco and licensed for remixing.

32 0 tools GitHub

No known CVEs

CC-BY-4.0 license

Maintained

Last commit 43d ago

Works with most clients

Transport: stdio, sse

0 tools

Grade F

Edit this pageView history

Security

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, sse · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "pentesting-mcp-servers-checklist": {
      "command": "<see-readme>",
      "args": []
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/pentesting-mcp-servers-checklist)](https://mcppedia.org/s/pentesting-mcp-servers-checklist)

Read me

What Pentesting Mcp Servers Checklist does

A practical, community-driven checklist for pentesting Model Context Protocol (MCP) servers. This guide covers local and remote MCP server risks, traffic analysis, tool-call behaviors, context boundaries, authorization flows, and unsafe code paths.

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

30/100across 5 weighted dimensions

How we score →

0255075100

−70

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is Pentesting Mcp Servers Checklist safe to use?: Pentesting Mcp Servers Checklist has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under CC-BY-4.0.
How do I install Pentesting Mcp Servers Checklist?: Pentesting Mcp Servers Checklist can be installed by cloning its GitHub repository and following the setup instructions in the README.
What AI clients work with Pentesting Mcp Servers Checklist?: Pentesting Mcp Servers Checklist is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse transport.
Is Pentesting Mcp Servers Checklist actively maintained?: Pentesting Mcp Servers Checklist is recently maintained — last commit was 43 days ago. It has 32 GitHub stars.

Similar servers

Others in security

View all →

Ida Pro Mcp92

AI-powered reverse engineering assistant that bridges IDA Pro with language models through MCP.

8.7k 3

Evil Mcp Server91

An evil MCP server used for redteam testing

30 1

Atomic Red Team Mcp90

MCP server for Atomic Red Team

123 5

io.github.peacprotocol/peac90

Signed receipts for agent, API, and MCP interactions. Portable and offline-verifiable.

11 5

MCP Security Weekly

Get CVE alerts and security updates for Pentesting Mcp Servers Checklist and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

Security

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, sse · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "pentesting-mcp-servers-checklist": {
      "command": "<see-readme>",
      "args": []
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/pentesting-mcp-servers-checklist)](https://mcppedia.org/s/pentesting-mcp-servers-checklist)

Read me

What Pentesting Mcp Servers Checklist does

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

README

Version 3 is out now!

A practical, community-driven checklist for pentesting Model Context Protocol (MCP) servers. This guide covers local and remote MCP server risks, traffic analysis, tool-call behaviors, context boundaries, authorization flows, and unsafe code paths.

Originally created for the OWASP Bay Area talk on Pentesting MCP Servers (Oct 2025), this checklist is designed for practitioners performing assessments on MCP-based tools, agents, and integrations.

Why this exists

MCP servers are becoming the new execution layer for AI agents. This means they expose:

File system access
Tool execution
Remote APIs
STDIO and HTTP bridges
Autonomous actions initiated by LLMs

Because of this, MCP servers introduce a wide attack surface that security testers need structured guidance for. This checklist helps you perform systematic and repeatable assessments.

What this checklist covers

Traffic Analysis — proxy inspection of STDIO/HTTP, context injection, TLS enforcement
Authentication & Authorization — auth bypass, OAuth flows, IDOR, privilege escalation
Local MCP Server File and Code Review — embedded secrets, dangerous functions, dependency audits
MCP Tool Behavior and Functionality — tool boundary validation, chaining, local RCE
Tool Security — Input Validation — command injection, path traversal, SSRF, SQLi, SSTI
Tool Security — Output & Schema Validation — schema mismatches, sensitive data leakage, prompt injection via output
Tool Injection — prompt injection via tool names/descriptions, tool shadowing, name collisions
File System & Network Access — path traversal, scope enforcement, DNS rebinding
Context Isolation — cross-user leakage, namespace separation, session persistence
Secret & Credential Handling — hardcoded secrets, log exposure, token caching
Logging & Monitoring — log injection, rate limiting, access controls
Race Conditions & Concurrency — TOCTOU, parallel invocation, resource exhaustion
Advanced Attacks — context pollution, confused deputy, prototype pollution, GraphQL injection

How to use this repo

Use the CHECKLIST.md for field assessments
Fork and adapt it for your team
Submit PRs with improvements
Open issues for new MCP attack patterns

Contribute

We welcome:

New checklist items
Additional MCP server categories
Tooling contributions
Red-team test cases
Sanitized findings

License

This project is licensed under CC BY 4.0. You may remix, adapt, and build upon this checklist for any purpose, even commercially, as long as you provide attribution.

Maintainers

Appsecco

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

30/100across 5 weighted dimensions

How we score →

0255075100

−70

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is Pentesting Mcp Servers Checklist safe to use?: Pentesting Mcp Servers Checklist has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under CC-BY-4.0.
How do I install Pentesting Mcp Servers Checklist?: Pentesting Mcp Servers Checklist can be installed by cloning its GitHub repository and following the setup instructions in the README.
What AI clients work with Pentesting Mcp Servers Checklist?: Pentesting Mcp Servers Checklist is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse transport.
Is Pentesting Mcp Servers Checklist actively maintained?: Pentesting Mcp Servers Checklist is recently maintained — last commit was 43 days ago. It has 32 GitHub stars.