Skip to content

docs: add mcp-witness security testing toolkit to ADDITIONAL.md Resources - #4802

Open
desledishant10 wants to merge 1 commit into
modelcontextprotocol:mainfrom
desledishant10:docs/add-mcp-witness-resource
Open

desledishant10 wants to merge 1 commit into
modelcontextprotocol:mainfrom
desledishant10:docs/add-mcp-witness-resource

Conversation

@desledishant10

Copy link
Copy Markdown

Description

Adds mcp-witness to the 📚 Resources section of ADDITIONAL.md, alongside the security tooling already listed there (MCPWatch, ToolHive, Webrix MCP Gateway). This is a single-line addition following the section's existing - **[Name](url)** - Description. format.

On the "publish to the registry instead" note in this template: that guidance is for servers being added to the README's server list. mcp-witness is not an MCP server; it is a security testing toolkit for auditing MCP servers, the same category as MCPWatch and ToolHive already in this Resources list. ADDITIONAL.md remains the curated home for frameworks and resources, so this is the appropriate place for it rather than the Server Registry.

mcp-witness (Apache-2.0) is an open-source security testing toolkit for MCP servers: a static analyzer over a captured tools/list, a dynamic attack harness, and a capability classifier. It flags SSRF in URL-fetching tools, DNS-rebinding on HTTP-transport servers, and tool-definition weaknesses, and ships containerized reproduction harnesses so findings can be verified in seconds without cloud infrastructure.

Motivation and Context

The Resources section lists tools that help people build and operate MCP servers safely, including several security scanners (MCPWatch, ToolHive, Webrix). mcp-witness adds another audit option focused on transport-layer and tool-definition issues, with runnable reproduction harnesses for each finding class.

Types of changes

  • Documentation update

Checklist

  • I have read the MCP Protocol Documentation
  • My changes follow MCP security best practices
  • My code follows the repository's style guidelines (one-line entry in the existing Resources format)

The remaining checklist items (server README, testing with an LLM client, tests, error handling, environment variables) do not apply: this is a one-line Resources listing, not a server or a code change.

Additional context

Placed immediately before the MCPWatch entry to keep the two security scanners adjacent and preserve the section's rough alphabetical ordering.

desledishant10 added a commit to desledishant10/mcp-witness that referenced this pull request Sep 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant