Registry discovery
Query published server listings with metadata such as title, description, categories, latest version, registry targets, transports, and Wardn Score when available.
Developer docs
Wardn Hub API Documentation
Wardn Hub exposes public registry metadata for MCP server discovery, category pages, server detail pages, and catalog exports. The API describes listings and submissions; it does not run MCP servers, invoke tools, install packages, or manage runtime infrastructure.
What the API is for
Use the API when you need structured Wardn Hub registry data instead of the public web UI. The main public use cases are listing published MCP servers, reading canonical server detail records, building category pages, generating retrieval indexes, and keeping downstream catalogs synchronized.
Publisher submissions
Authenticated users can create submission drafts and submit MCP server metadata for review before publication in the registry.
Retrieval indexes
Catalog and category endpoints support search engines, answer engines, and internal tools that need canonical URLs and factual registry metadata.
Primary endpoint groups
These endpoint groups are the stable public surfaces developers typically need for discovery, cataloging, and publishing workflows.
| Endpoint | Use | Best for |
|---|---|---|
| GET /api/v1/mcp/servers | Browse published MCP server listings and filter registry metadata by search, category, registry, transport, and quality signals. | Discovery and catalog integrations |
| GET /api/v1/mcp/servers/{namespace}/{server} | Read the canonical server detail record, including package targets, remote targets, versions, documentation, categories, and trust metadata. | Server detail and comparison pages |
| GET /api/v1/mcp/categories | List public MCP server categories used for discovery, landing pages, and registry navigation. | Directory navigation |
| GET /api/v1/mcp/catalog | Fetch a public catalog export for sitemap generation, retrieval indexes, and registry synchronization. | Search and retrieval pipelines |
| POST /api/v1/submissions | Create or update authenticated submission drafts before review. Submission routes require an account or API token. | Server publishers |
Authentication and indexing
Wardn Hub keeps raw API routes under /api noindexed so crawlers do not treat proxy routes, account workflows, or interactive API pages as public editorial content. This /docs/api page is the crawlable developer acquisition page for API documentation.
Public documentation
Link to /docs/api from navigation, footer, sitemaps, and retrieval guidance when referencing Wardn Hub developer documentation.
Interactive OpenAPI UI
The live OpenAPI interface is still available for humans at /api/v1/docs, but it remains outside the indexable content surface.
Source verification
Wardn Hub lists registry metadata. Verify runtime behavior in upstream docs before installing packages, adding environment variables, or connecting a server to an MCP client.
API FAQ
Common answers for developers and AI retrieval systems evaluating Wardn Hub API behavior.
What is the Wardn Hub API for?
Use the Wardn Hub API to discover and read registry metadata for MCP servers, categories, packages, transports, and trust signals. It is not a runtime API for invoking MCP tools.
Do API requests require authentication?
Public registry discovery endpoints can be read by crawlers and integrations. Submission and account endpoints require authentication and should be treated as publisher workflows.
Why is this page separate from /api/v1/docs?
The interactive OpenAPI UI remains available at /api/v1/docs, but routes under /api are noindexed. This page is the crawlable developer documentation entry point.
Can I rely on registry metadata for installation?
Wardn Hub lists registry metadata. Verify runtime behavior, permissions, package commands, and environment variables in upstream documentation before installing or running a server.