Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Sigistry Plugin & Skill Catalog

REMOTE · SIGISTRY.COM · SCANNED SEP 20

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

Available components

+3 this week 85 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 766 tokens (~95/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Sigistry Plugin & Skill Catalog MCP server?

Sigistry Plugin & Skill Catalog is a hosted endpoint at https://sigistry.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · sigistry.com

# add to Claude Code
claude mcp add --transport http com-sigistry-plugin-catalog 'https://sigistry.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-sigistry-plugin-catalog": {
      "url": "https://sigistry.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-sigistry-plugin-catalog": {
      "type": "http",
      "url": "https://sigistry.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-sigistry-plugin-catalog]
url = "https://sigistry.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-sigistry-plugin-catalog": {
      "type": "remote",
      "url": "https://sigistry.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-sigistry-plugin-catalog --url 'https://sigistry.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-sigistry-plugin-catalog:
    url: "https://sigistry.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-sigistry-plugin-catalog": {
      "Transport": "http",
      "Url": "https://sigistry.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-sigistry-plugin-catalog -t streamable-http -u 'https://sigistry.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-sigistry-plugin-catalog": {
      "type": "http",
      "url": "https://sigistry.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 0
    • Schema quality: 574 → 766 functional
    • Server version: 1.5.0 → 1.6.0 functional
    • New tool “get_scorecard” functional
    • New tool “list_scorecards” functional
  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://sigistry.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=sigistry.com CN=YE1,O=Let's Encrypt,C=US 24 Aug 2026 22 Nov 2026 ECDSA 256 ECDSA-SHA384 66cc212a81c1ac200901c27e58ab1e8a5a2
SANs: sigistry.com, www.sigistry.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of sigistry.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
sigistry.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://sigistry.com/mcp Verified 200
http (plaintext) http://sigistry.com/mcp HTTPS enforced 301 https://sigistry.com/mcp
MCP tools · 8 exposed · ~766 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_plugin ~68

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).

NameTypeReqDescription
idstringyesthe plugin id, e.g. "sql-safety-net"
NameTypeReqDescription
agentsarrayyesrelative paths to agent files
authorobject
categorystring
commandsarrayyesrelative paths to command files
countsobjectyescomponent counts
descriptionstring
homepagestring
idstringyes
installCommandstringyescommand to install this plugin
installMarketplacestringyescommand to add the marketplace to Claude Code
licensestring
namestringyes
searchableTextstringyeslowercased text used for matching
skillsarrayyesrelative paths to skill manifests
tagsarrayyeskeywords from the marketplace entry
verificationsecurity-audit result for this plugin (null when never audited)
versionstring

No examples provided.

get_scorecard ~104

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.

NameTypeReqDescription
idstringyesscorecard id, e.g. "sigistry-catalog" (find ids via list_scorecards)
NameTypeReqDescription
axesarrayyesper-axis results with evidence
commit
date
endpoint
gradestringyes
idstringyes
namestringyes
notesarrayhardening suggestions and context
repo
rubricUrl
rubricVersion
selfAssessmentboolean

No examples provided.

get_skill ~120

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.

NameTypeReqDescription
namestringyesthe skill name, e.g. "assessment-scoring" (find names via search_skills)
NameTypeReqDescription
commitstringpinned commit the source is served from, when externally hosted
descriptionstringyesthe skill trigger: when an agent should load it
detailUrlstringyeshuman-readable page for this skill
hostingstringyes"registry" (vendored here) or "external" (author repo, verified at a pinned commit)
installCommandstringyesClaude Code command installing the parent plugin (skill loads automatically)
namestringyesstable skill name, e.g. "assessment-scoring"
pluginstringyesparent plugin id that ships this skill
pluginCategorystring|nullyescategory of the parent plugin
repostringauthor repo (owner/name), when externally hosted
sourcestring|nullyesthe complete raw SKILL.md (frontmatter + body); null only if the fetch failed
sourceUrlstringyesGitHub location of the skill directory
verificationstringyesverification status of the parent plugin; prefer "verified"
verifiedDatestring|nullyesdate of the verification run covering this skill

No examples provided.

list_categories ~32

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

Input schema present but exposes no named parameters.

NameTypeReqDescription
categoriesarrayyescategories sorted by descending plugin count
totalintegeryestotal number of plugins

No examples provided.

list_scorecards ~88

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
rubricUrlstring|nullyes
rubricVersionstring|nullyes
scorecardsarrayyes
totalintegeryes

No examples provided.

search_plugins ~86

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).

NameTypeReqDescription
categorystringe.g. "database", "devops", "git"
querystringkeywords, e.g. "database migration"
NameTypeReqDescription
resultsarrayyesup to 15 matching plugins, best matches first

No examples provided.

search_skills ~115

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.

NameTypeReqDescription
pluginstringrestrict to skills shipped by this plugin id
querystringkeywords, e.g. "changelog" or "security review"
NameTypeReqDescription
resultsarrayyesup to 20 matching skills, best matches first

No examples provided.

verify_plugin ~153

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.

NameTypeReqDescription
pluginPathstringlocal path to the plugin directory, used to fill in the run command (optional)
NameTypeReqDescription
checksarrayyesthe eight checks the script will run
commandsobjectyes
interpretingstringyes
methodologyUrlstringyes
methodologyVersionstringyes
nextStepsstringyes
runsWherestringyesalways "local": verification executes on the user's machine
stepsarrayyeswhat the agent should do, in order

No examples provided.

Common questions

What is the Sigistry Plugin & Skill Catalog MCP server?

Sigistry Plugin & Skill Catalog is an MCP server listed in the public MCP registry as com.sigistry/plugin-catalog. Search verified Claude Code plugins and skills; fetch portable SKILL.md sources. Read-only. This page covers its hosted endpoint (https://sigistry.com/mcp).

Is the Sigistry Plugin & Skill Catalog MCP server safe to use?

Sigistry Plugin & Skill Catalog scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Sigistry Plugin & Skill Catalog MCP server expose?

Sigistry Plugin & Skill Catalog exposes 8 tools: search_plugins, get_plugin, list_categories, search_skills, get_skill, and 3 more. Their descriptions and schemas cost roughly 766 tokens of context every time the server is loaded.

Does the Sigistry Plugin & Skill Catalog MCP server require authentication?

No. We connected to Sigistry Plugin & Skill Catalog without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Sigistry Plugin & Skill Catalog MCP server still maintained?

Sigistry Plugin & Skill Catalog is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.