MCP Tool Registry

A metadata-only registry for managing and discovering MCP Tool Shop tools with schema validation and curated bundles.

What This Skill Does

This skill helps you interact with the MCP Tool Registry ecosystem to discover, validate, and manage Model Context Protocol tools. It provides access to a structured registry of tools with metadata, bundles, and validation capabilities.

Key Concepts

**MCP Tool Shop Architecture:**

**Security Model:**

**Versioning:**

Instructions

1. Exploring the Registry

When users want to discover available tools:

1. Check the registry structure:

- `registry.json` → Main tool registry

- `schema/registry.schema.json` → JSON Schema for validation

- `bundles/` → Curated tool collections

2. Available bundles:

- `core.json` → Essential utilities

- `agents.json` → Agent orchestration tools

- `ops.json` → Operations and infrastructure tools

3. Use Bash to view available tags:

```bash

git tag -l

```

2. Validating Registry Schema

When users need to validate registry entries:

1. Use npx with ajv to validate the schema:

```bash

npx ajv validate -s schema/registry.schema.json -d registry.json

```

2. Ensure all required fields are present for each tool:

- `id`: kebab-case identifier (e.g., `file-compass`)

- `name`: Human-readable name

- `description`: What the tool does

- `repo`: GitHub repository URL

- `install`: Installation config (type, url, default_ref)

- `tags`: Array of tags for search/filtering

- `defaults` (optional): Default settings like `safe_run`

3. Initializing with mcpt CLI

When users want to start using the registry:

1. Initialize with a pinned release version:

```bash

mcpt init --registry-ref v0.1.0

```

2. Explain that pinning the registry ref locks the metadata version, not tool code versions

4. Adding New Tools to Registry

When users want to contribute a tool:

1. Read the current `registry.json` file

2. Add a new entry following the schema requirements

3. Validate the updated registry against the schema

4. Guide users to submit a PR with their changes

5. Managing Tool Versions

When users need to pin specific tool versions:

1. Explain the difference:

- Registry ref → metadata version

- Tool ref → actual tool code version

2. Show how to pin a specific tool:

```bash

mcpt add tool-id --ref v1.0.0

```

6. Working with Bundles

When users want to use curated tool collections:

1. List available bundles (core, agents, ops)

2. Read the bundle files from `bundles/` directory

3. Explain what each bundle contains and when to use it

Examples

**Example 1: Discovering Available Tools**

```

User: "Show me what tools are available in the MCP registry"

Assistant: [Reads registry.json and lists tools with descriptions]

```

**Example 2: Validating a New Tool Entry**

```

User: "I want to add a new tool called 'data-analyzer'"

Assistant: [Reads schema, guides user through required fields, validates JSON]

```

**Example 3: Setting Up with Pinned Version**

```

User: "How do I start using the registry?"

Assistant: [Runs: mcpt init --registry-ref v0.1.0, explains versioning]

```

Important Notes

Constraints