# ToolHive Registry Catalog

> Updated 2026-09-03 · type: tool · category: mcp-agents · status: active · rev 1

Open-source registry catalog of MCP servers from Stacklok. Demonstrates twin catalog streams — servers for executable components and skills for reusable…

- Open source: yes (Apache-2.0)
- Pricing model: free
- Best for: Developers and organizations building AI applications who want a catalog of MCP servers and skills that AI assistants can use with ToolHive.
- Last verified: 2026-09-04

- **Canonical:** https://gtmstacker.com/registry/tool/toolhive-catalog/
- **Source:** [stacklok/toolhive-catalog (GitHub)](https://github.com/stacklok/toolhive-catalog)
- **Tags:** mcp, registry, skills, catalog, security
- **Repository:** https://github.com/stacklok/toolhive-catalog

## Is ToolHive Registry Catalog open source?

Yes — Apache-2.0-licensed.

## How much does ToolHive Registry Catalog cost?

It is free to use.


---

ToolHive's catalog is a working example of a registry that maintains **twin catalog streams**: `servers` for executable MCP components and `skills` for reusable prompt workflows.

## Why it matters for agents

Each registered skill pairs a `skill.json` config with an adjacent `SKILL.md` payload. The config declares ownership namespace, semantic version, license, and an **`allowedTools`** array listing the exact tool names the skill may invoke. Restricting tool access inside the skill definition prevents agent privilege escalation and keeps execution bounded within declared parameters.

## Relevance

This registry borrows the twin-stream idea: `tool` entries describe executables, while a bundled Agent Skill (`consume-registry`) describes how to *use* the registry itself, with a bounded `allowedTools`.