Add MyMCPTools (MCP server directory with liveness checks) - #58
Open
shibley wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds one entry, in alphabetical position between
muxandnanobot, using the existing**[Tool Name](URL)** - Description.format.Developer use case: picking an MCP server today means reading a README and hoping. MyMCPTools catalogs 2,726 of them and exposes the catalog as an MCP server (
search_mcp_servers,get_mcp_server,get_server_status,get_server_history,list_server_incidents,list_schema_drift,list_categories,get_catalog_stats), so the check happens in-session before anything lands in a config file. Remote Streamable HTTP, no API key.This is adjacent to Find MCP, already in the list — that one searches the official registry; this one adds liveness and schema-drift state on top of the catalog.
On the numbers, stated the unflattering way: of the 2,726 entries only 44 expose a remote endpoint that can be probed at all; the other 98% are local/stdio servers. Those are labelled unprobeable rather than shown with a made-up uptime percentage. Of the 44 probeable, 5 were serving at the last sweep, 38 require auth, 1 was down. I would rather you see that ratio in the PR than discover it after merging.
Verified live tonight:
initialize→serverInfo.name mymcptools,protocolVersion 2025-06-18;tools/list→ the 8 tools above;get_catalog_stats→total: 2726,probed_last_24h: 2726. https://mymcptools.com/ returns 200.Disclosure: I maintain MyMCPTools. Trim the description or close it if it is not what you want in the list.