More than a list of MCP server names
Wardn Hub keeps install metadata, transports, environment variables, namespace evidence, review status, and Wardn Score close to each server listing.
Compare install targets, remote endpoints, environment variables, namespace evidence, and Wardn review signals in one place.
As of July 27, 2026, Wardn Hub lists 3803 MCP servers across 50 categories. Last registry update observed July 27, 2026.
Wardn Hub keeps install metadata, transports, environment variables, namespace evidence, review status, and Wardn Score close to each server listing.
Wardn Hub is a trusted MCP server directory. It helps developers compare Model Context Protocol servers by installation metadata, transports, environment variables, namespace verification, review status, and Wardn Score before adding a server to an MCP client.
Start with servers that publish clear package or remote metadata, documented environment variables, current source links, and a strong Wardn Score. Then verify upstream documentation before installing or connecting sensitive accounts.
No. Wardn Hub is a registry and discovery product, not an MCP runtime or gateway. It lists metadata, trust signals, and links so operators can evaluate a server before runtime use.