docs: add mcp discovery cli

[hashemix]

Description

Adding MCP Discovery CLI to the Resources section of the README.

It is a command-line tool written in Rust for discovering and documenting MCP Server capabilities. It supports outputting the results in the terminal or saving them to files in Markdown, HTML, or plain text formats.
It is also available as a GithubAction to automate and maintain up-to-date MCP Server documentation.

Here is a sample output that is generated for @modelcontextprotocol/server-everything server:
server-everything capabilities

Server Details

- Server:
- Changes to:
Not a server, but a CLI utility for discovering and documenting MCP Server capabilities.

Motivation and Context

It is a command-line tool written in Rust for discovering and documenting MCP Server capabilities. It supports outputting the results in the terminal or saving them to files in Markdown, HTML, or plain text formats.

It can be used to inspect capabilities of a MCP Server right from the terminal, can generate html, md, txt files and supports custom templates.

It is also available as a GithubAction to automate and maintain up-to-date MCP Server documentation.

How Has This Been Tested?

• integration testing
• manual testing with a large number of available MCP servers, here are a couple of examples:
  • @modelcontextprotocol/server-everything capabilities : https://rust-mcp-stack.github.io/mcp-discovery/examples/server-info.html
  • rust-mcp-filesystem capabilities : https://rust-mcp-stack.github.io/rust-mcp-filesystem/#/capabilities

First one is generated by CLI and second one is automatically generated with mcp-discovery-action GitHub Action

Breaking Changes

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• 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

Additional context