Sigistry Plugin Catalog (formerly Claude Registry) MCP Server

by clauderegistry Your server? Claim it

answering

Sigistry Plugin Catalog (formerly Claude Registry) is answering right now. Last checked 7 min ago. It exposes 8 tools.

Renamed: prefer com.sigistry/plugin-catalog. This legacy endpoint keeps working.

Uptime history 52 days of history · worst day 93%

52 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

437 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 12

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 24 August 2026. No other catalogue keeps this.

11 Sep 2 tools appeared get_scorecard, list_scorecards

11 Sep a tool changed version

28 Aug 2 tools appeared get_skill, search_skills

28 Aug 2 tool descriptions were rewritten search_plugins, verify_plugin

28 Aug a tool changed version

24 Aug 4 tool descriptions were rewritten get_plugin, list_categories, search_plugins and 1 more

Nothing serious here today

Today is the operative word: we check Sigistry Plugin Catalog (formerly Claude Registry) every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add plugin-catalog --transport http https://clauderegistry.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "plugin-catalog": {
      "url": "https://clauderegistry.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.plugin-catalog]
url = "https://clauderegistry.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "plugin-catalog": {
      "url": "https://clauderegistry.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "plugin-catalog": {
      "url": "https://clauderegistry.com/mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

categories

list_categories

List the distinct plugin categories in the Sigistry marketplace with a count of plugins in each, plus the total plugin count.

plugin

get_plugin

Get the full details of a single Sigistry plugin by its id, including install commands, component counts, and its security-audit result (per-check pass/fail from the Verified by Sigistry methodology).

plugins

search_plugins

Search the Sigistry marketplace of Claude Code plugins by keyword and/or category. Returns matches with their install command and verification status (the registry runs an eight-check security audit; prefer "verified" plugins when recommending an install).

scorecard

get_scorecard

Get the full scorecard for one graded MCP server by its id: the overall grade, per-axis pass/partial/fail with cited evidence, hardening notes, the rubric version, and the exact commit graded. Grades describe the pinned commit only; a re-grade at a newer commit can be requested via an issue on the marketplace repo.

scorecards

list_scorecards

List the public MCP servers Sigistry has independently graded against its scorecard rubric (transport, stateless core, lifecycle, authorization, tool design, security hygiene), each with an overall grade A-F and the exact commit graded. Useful before connecting an agent to a third-party MCP server: check whether it has been assessed and how it scored. Use get_scorecard for the full per-axis breakdown.

skill

get_skill

Get one Sigistry skill by name, including the full raw SKILL.md source. The source is portable: it can be applied directly in any SKILL.md-aware agent (Claude Code, Claude Desktop, and others) without installing anything, or installed natively in Claude Code via the parent plugin, which keeps it verified and updated. The returned skill passed the Sigistry skill-safety check at the parent plugin's verification date.

skills

search_skills

Search the Sigistry catalog of verified skills (SKILL.md instruction sets for AI agents) by keyword, optionally filtered to one parent plugin. Every skill passed the skill-safety check: no command shadowing, honestly-scoped triggers, no injection or concealment language, no unsafe scripts. Use get_skill to fetch the full portable source of a match.

verify

verify_plugin

Get the recipe to run the Sigistry verification methodology (the eight static checks that gate the Verified badge: manifest integrity, hook safety, agent tool scopes, command hygiene, skill structure, skill safety, no secrets, documentation) against a plugin BEFORE publishing it. The verification runs entirely on the local machine via a dependency-free open-source Node script; the plugin code never leaves the user's computer and this server performs no computation. Call this when the user wants their plugin or skill checked, then follow the returned steps: download the script, run it against the plugin directory, and fix any FAIL findings it reports.

Endpoints

URL	Transport	State	Latency	Checked
https://clauderegistry.com/mcp	streamable-http	answering	437 ms	7 min ago

Alternatives to Sigistry Plugin Catalog (formerly Claude Registry)

same job, measured the same way

Sigistry Plugin & Skill Catalog

by sigistry

Search verified Claude Code plugins and skills; fetch portable SKILL.md sources. Read-only.

8 tools answering

Dsh Cert

by perrylink

Read-only MCP server exposing the dsh-plugin-certification registry for DeepSeek Harness plugins.

478 installs/wk local only

Roamer MCP

by mathismeadows

Project registry, behavioral specs, and engineering threads for AI coding agent workflows.

99 installs/wk answering

Tally Workout

by westvegh

First strength app Claude can write to: plan training in chat, it lands in the app ready to log.

answering

treg.to

by superdesigndev

OpenRouter for tools and data. Compare catalog providers and call them from one hosted MCP endpoint.

answering

Zola MCP

by chrischall

Zola wedding planning for Claude — vendors, budget, guests, seating, registry, and RSVPs

657 installs/wk local only

Claws Mail MCP Plugin

by it-atelier-gn

Claws Mail plugin exposing the running mail client over a local, bearer-token MCP endpoint.

local only

PitchPilot Agent Tools (legacy name - see sigtap)

by unnamedaiagent

Legacy name of io.github.unnamedaiagent/sigtap-agent-tools. Endpoints moved; see sigtap listing.

13 tools local only

Sigistry Plugin Catalog (formerly Claude Registry) — questions

Answers built from our own checks of this server.

What can Sigistry Plugin Catalog (formerly Claude Registry) do?

It exposes 8 tools, read directly from the server on our last check. Among them: get_plugin, get_scorecard, get_skill, list_categories, list_scorecards, search_plugins and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Sigistry Plugin Catalog (formerly Claude Registry) working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 437 ms. The bar chart above shows every period we have measured.

How do I connect Sigistry Plugin Catalog (formerly Claude Registry)?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Sigistry Plugin Catalog (formerly Claude Registry) need an API key?

No. Sigistry Plugin Catalog (formerly Claude Registry) completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Sigistry Plugin Catalog (formerly Claude Registry)?

It answers our handshake in 437 ms on average, which is faster than 36% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.