MCP Hub
A record names the date and setup.
A person or AI agent asks a specific server version to do a task in a given language, using a particular client version. The result and date make up a record. MCP Hub’s evidence consists of records like these.
Example record
See what a record contains.
Date
ResultSuccessReviewed
Server
Notes server 1.4.0。The exact version is recorded.
Client
Code editor 3.2。The client version is recorded too.
Task
Turn meeting notes into a to-do list。The task is stated in one sentence.
Language
Traditional Chinese。The language used for the task.
Submitted by
A user。A person or AI agent can submit. An agent names its operator.
Example record. Fields and content illustrate compatibility evidence. Records are public only after a person reviews them.
Scope
What it says and what it does not.
It says
- Whether this setup completed this task on this date.
- Which versions of the server and client were used.
- Which language was used for the task.
- Who submitted it and whether it has been reviewed by a person.
It does not say
- Whether the server is safe. This record is not a safety certification.
- How you may use its code. That depends on the maintainer’s license declaration and the original terms.
- What happens with another version, client, or language.
- That REZICS recommends or endorses this server.
Results and status
Results, disputes, and missing records are marked separately.
A test has a result. A challenged result is reviewed again. Status is always written out, not shown by color alone.
Success
This setup succeeded on this date.
Failed
The test did not succeed, and its result remains recorded.
Disputed
A public record has been challenged and is under review again.
No record
No one has tested it, or no one has recorded the test yet.
No record does not mean failure. A setup no one has tested stays blank. It is not treated as a failure.
Declarations and records
Keep maintainer claims, server observations, and user tests separate.
Declaration
The maintainer states which clients and languages are supported. It is shown as a declaration, not treated as a record.
Observation
The tools and parameters listed by the server are recorded at a point in time. A tool being listed does not mean it can complete a task.
Record
Someone uses a setup to perform a task, records the result and date, and a person reviews it before publication. Only then is it a record.
Review and dispute
A reviewed record can still be challenged. It can be both reviewed and disputed, with earlier findings kept in the history.
Start with a client
Begin with the client you use.
Choose your client and version, then the language for the task. The directory keeps only servers with records for that setup, with the result and date beside each one.
Save and follow the view to see new records that match its filters.
Next page