@@ -3,9 +3,11 @@ title: Explore the registry
3
3
description : How to use the built-in registry to find MCP servers.
4
4
---
5
5
6
- ToolHive includes a built-in registry of MCPs with verified configurations,
7
- allowing you to discover and deploy MCP servers effortlessly. Simply select one
8
- from the list and run it securely with a single command.
6
+ ToolHive includes a built-in registry of MCP servers with verified
7
+ configurations that meet a
8
+ [ minimum quality standard] ( ../concepts/registry-criteria.md ) , allowing you to
9
+ discover and deploy high-quality tools effortlessly. Simply select one from the
10
+ list and run it securely with a single command.
9
11
10
12
## Find MCP servers
11
13
@@ -174,23 +176,6 @@ thv config unset-registry-url
174
176
175
177
This restores the default behavior of using ToolHive's built-in registry.
176
178
177
- # # Contribute to the registry
178
-
179
- If you have an MCP server that you'd like to add to the ToolHive registry, you
180
- can
181
- [open an issue](https://github.com/stacklok/toolhive/issues/new?template=add-an-mcp-server.md)
182
- or submit a pull request to the ToolHive GitHub repository. The ToolHive team
183
- will review your submission and consider adding it to the registry.
184
-
185
- Criteria for adding an MCP server to the ToolHive registry are outlined in
186
- [Registry criteria](../concepts/registry-criteria.md). These criteria ensure
187
- that the servers in the registry meet the standards of security, quality, and
188
- usability that ToolHive aims to uphold.
189
-
190
- Registry entries are defined in the
191
- [`pkg/registry/data/registry.json`](https://github.com/stacklok/toolhive/blob/main/pkg/registry/data/registry.json)
192
- file in the ToolHive repository.
193
-
194
179
# # Next steps
195
180
196
181
See [Run MCP servers](./run-mcp-servers.mdx) to run an MCP server from the
0 commit comments