list_serversLABSCO SUMMARY
A catalogue lookup, not a live registry probe.
What it reads is one README in one repository, parsed into entries with name, description, author and category — so it answers what is listed, not what is currently running or maintained. That is still the fastest way to answer does something already exist for X before writing your own, and the feature search is better suited to that question than scrolling a long Markdown page.
What it is
An MCP server that queries the official modelcontextprotocol/servers repository, parsing its README into a searchable catalogue split across reference, official and community entries — 547 servers by that page's own headline count, which is only ever as fresh as its last edit.
What you get
list_servers— browse the catalogue with an optionalcategoryof reference, official, community or all, a textsearch, and alimitdefaulting to 20get_server_details— everything known about one server, by namesearch_servers_by_feature— find servers offering a capability such as database, api or blockchain, with alimitdefaulting to 10get_random_servers— a random selection for browsing,countdefaulting to 5refresh_server_list— force a refresh of the cached catalogue from GitHub
Requirements
Nothing — no account, no key. The package is @atonomus/mcp-servers-search (1.0.1 in package.json), run with npx -y @atonomus/mcp-servers-search or installed globally. The catalogue is cached for 1 hour to keep GitHub API calls down; refresh manually when you need it fresher. MIT licensed.
Setup effort
One command — npm install -g @atonomus/mcp-servers-search
USE CASES
Checking whether a server already exists for a job
Search by capability — database, calendar, blockchain — before building something from scratch.
Reading up on one server you have heard of
Look it up by name and get its description, author and category in one call.
Seeing only the official entries
Filter the catalogue to the official category and skim what vendors themselves publish.
Discovering something you were not looking for
Pull a handful of random community servers when the goal is browsing rather than searching.
Making sure the list is current
Force a refresh past the one-hour cache before relying on the answer.
5 tools
Listed in project docs. Your client may show a different list.
get_server_detailssearch_servers_by_featureget_random_serversrefresh_server_listBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
npx on PATH
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
npm install -g @atonomus/mcp-servers-searchMCP Clients
Claude Desktop
{
"mcpServers": {
"servers-search": {
"command": "npx",
"args": [
"-y",
"@atonomus/mcp-servers-search"
]
}
}
}