MCP server index
Dated records show which servers work.
MCP Hub gives every MCP server an identity and a separate record for each version: the date, client and version, language, and task result.
One record
Before saying it works, name the setup.
A result depends on the server version, client, task, and language. Each record states all four, along with the outcome and date. Change any part, and it needs a new test.
Server version
Record the exact version. A new version gets a new record.
Client
Name the client and its version.
Task
What the server was asked to do.
Language
The same task can have a different result in another language.
Result and date
Whether it worked and when it was tested.
A record reports the result of one setup on one date. It does not prove a server is safe, grant a license, or represent an endorsement by REZICS.
This site
One page for each step, from finding a server to maintaining one.
Connected indexes
A server is part of a larger record.
The people behind it, the APIs it wraps, and the project it belongs to share one index, so you can find them from any direction.
Read the records before you choose a server.
Use one account for servers, skills, and APIs, as well as the books and games you follow on REZICS.