feat(readme): adding mcp-watch in readme resources

[kapilduraphe]

Adds mcp-watch under resources which is a comprehensive security scanner for Model Context Protocol (MCP) servers that detects vulnerabilities and security issues in your MCP server implementations

Motivation and Context

Helps a developer or end user determining the quality of an mcp server

How Has This Been Tested?

Tested it with 1-2 community built mcp servs

Breaking Changes

None

Types of changes

• Documentation update

Checklist

• I have read the MCP Protocol Documentation
• My changes follows MCP security best practices
• I have updated the server's README accordingly
• I have tested this with an LLM client
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have documented all environment variables and configuration options

Note: I tried to keep it ordered alphabetically. Pls flag if I missed out. Thanks!

[kapilduraphe]

Hello @tadasant , I recently built a tool for scanning mcp server implementations from the vuln security angle. Please review the PR out. Also, I'd love/deeply appreciate if you end up trying it out. Welcoming any feedback 🙏

CCing some of the other reviewers as well: @dsp-ant @cliffhall 🙏 🙏

[tadasant]

@olaservo looks like this got merged into community servers, but I think it should've been under Resources. Maybe need a tweak to whatever process you used for adding labels?

[olaservo]

Thanks for your contribution to the servers list. This has been merged in this combined PR: #2007

This is a new process we're trying out, so if you see any issues feel free to re-open the PR and tag me.

[olaservo]

@olaservo looks like this got merged into community servers, but I think it should've been under Resources. Maybe need a tweak to whatever process you used for adding labels?

@tadasant hanks for catching this - yes there's a few resources links that most likely slipped through the cracks, moved this one in this PR which also re-alphabetizes: https://github.com/modelcontextprotocol/servers/pull/2055/files

Will add more specificity for the next round to reduce the chances of that happening.