MCP Hub
One server, one identity.
The same MCP server may appear in several sources. After review and merging, it has one record on REZICS, with its name, maintainers, versions, records, ratings, and discussion connected to it.
Four parts
A server record covers four different things.
Projects, packages, deployed endpoints, and tool lists change at different times, so REZICS records them separately.
Project
Its name, description, and maintainers. A new version or endpoint does not make it a new project. A project fork is a separate project linked to its source.
Package
A package version, its ecosystem, its native name, and its version number. Versions are ordered by the ecosystem’s own rules.
Deployed endpoint
The server’s network address. A working connection does not prove who owns it, whether it works with your client, or whether you have permission to call it.
Tool list
The tools a server exposed at a given time and the parameters each required. A change to the list adds a new observation.
Filters
Every filter matches the same record.
To find a server that successfully exports a file from a command-line client in Traditional Chinese, all three conditions must come from one record. They are never combined from unrelated records.
Servers that successfully organize tasks in Japanese in a code editor
The client, language, task, and result all come from one record.
Servers with a successful record for their latest version in the past 90 days
The version, date, and result are tied to one record.
All servers maintained by the same person
Find them by maintainer.
Servers that wrap a particular API
Find them by relationship, or start from the API.
Save filters as a named view to open again or follow it.Example view.
Lists
Lists reach the end and show where they stop.
Keep going to the last result
Results are not limited to the first few pages. Keep browsing until the last entry.
Accurate counts
Counts are marked as exact or estimated, with the data’s last updated date.
Say when a filter is unsupported
Unsupported combinations are identified clearly, not returned as a blank that looks like “no results.”
Parts
Eight shared parts across every kind.
MCP Hub is not a separate application. Its entries use the same parts as books, games, and software, arranged for MCP servers.
Identity
identityThe same server listed by different sources points to one identity.Editions
editionsEach version has its own record, including its package, tool list, and history.Specifications
specsCompatibility records include the date, client and version, task, language, and result.Credits
creditsMaintainers can be people or organizations, linked to their other projects.Ratings
ratingsEach rating is tied to a version and names the question it answers.Discussion
discussionDiscussion threads can be attached to the server or a specific version.Lists
listsAdd servers, skills, and APIs to the same list, with a note for each item.Follow
followFollow a server, maintainer, or saved view to get notified about new versions.
The same name does not make the same server. Merges need evidence and review.
After a merge, the original identities and history remain available.
Next page