Sigistry Plugin Catalog (formerly Claude Registry)

Get a Claude Code plugin

get_plugin

Read-onlyIdempotent

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

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	the plugin id, e.g. "sql-safety-net"

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`name`	Yes
`tags`	Yes	keywords from the marketplace entry
`agents`	Yes	relative paths to agent files
`author`	No
`counts`	Yes	component counts
`skills`	Yes	relative paths to skill manifests
`license`	No
`version`	No
`category`	No
`commands`	Yes	relative paths to command files
`homepage`	No
`description`	No
`verification`	No	security-audit result for this plugin (null when never audited)
`installCommand`	Yes	command to install this plugin
`searchableText`	Yes	lowercased text used for matching
`installMarketplace`	Yes	command to add the marketplace to Claude Code

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedAug 6, 2026

addedOutput schema / properties / verification

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "badgeUrl": {
+          "description": "SVG badge for this plugin",
+          "type": "string"
+        },
+        "checks": {
+          "description": "per-check results of the security audit",
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "detail": {
+                "type": "string"
+              },
+              "id": {
+                "type": "string"
+              },
+              "status": {
+                "description": "pass | fail | n/a",
+                "type": "string"
+              },
+              "title": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "id",
+              "title",
+              "status"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "commit": {
+          "description": "pinned commit the verification applies to",
+          "type": "string"
+        },
+        "date": {
+          "description": "date of the last audit run",
+          "type": "string"
+        },
+        "firstSeen": {
+          "description": "date the plugin entered the registry",
+          "type": "string"
+        },
+        "hosting": {
+          "description": "registry (vendored) | external (author repo)",
+          "type": "string"
+        },
+        "methodologyUrl": {
+          "type": "string"
+        },
+        "methodologyVersion": {
+          "type": "string"
+        },
+        "repo": {
+          "description": "external repo (owner/name), when externally hosted",
+          "type": "string"
+        },
+        "status": {
+          "description": "verified | listed | stale | failed",
+          "type": "string"
+        }
+      },
+      "required": [
+        "status",
+        "checks"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "security-audit result for this plugin (null when never audited)"
+}

Changed1 schema field changedJul 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "agents": {
+      "description": "relative paths to agent files",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "author": {
+      "additionalProperties": false,
+      "properties": {
+        "name": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "category": {
+      "type": "string"
+    },
+    "commands": {
+      "description": "relative paths to command files",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "counts": {
+      "additionalProperties": false,
+      "description": "component counts",
+      "properties": {
+        "agents": {
+          "type": "integer"
+        },
+        "commands": {
+          "type": "integer"
+        },
+        "skills": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "commands",
+        "agents",
+        "skills"
+      ],
+      "type": "object"
+    },
+    "description": {
+      "type": "string"
+    },
+    "homepage": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "installCommand": {
+      "description": "command to install this plugin",
+      "type": "string"
+    },
+    "installMarketplace": {
+      "description": "command to add the marketplace to Claude Code",
+      "type": "string"
+    },
+    "license": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "searchableText": {
+      "description": "lowercased text used for matching",
+      "type": "string"
+    },
+    "skills": {
+      "description": "relative paths to skill manifests",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "tags": {
+      "description": "keywords from the marketplace entry",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "version": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "tags",
+    "commands",
+    "agents",
+    "skills",
+    "counts",
+    "installMarketplace",
+    "installCommand",
+    "searchableText"
+  ],
+  "type": "object"
+}

First observedJul 15, 2026

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the bar is lower. The description adds value beyond annotations by disclosing what the response includes (install commands, component counts, and the per-check pass/fail security result), which is genuinely useful behavioral context. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence that leads with the tool's core purpose and packs the return-value details without padding. Every clause earns its place; there is no redundant restatement of the name or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is a simple single-parameter read, the safety profile is fully covered by annotations, and an output schema exists, so return values need no description. The only shortfall is the missing guidance on how get_plugin relates to verify_plugin for security-audit needs, but the definition is otherwise complete for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% — the single id parameter is already documented in the schema with an example ('sql-safety-net'). The description only restates that the tool operates 'by its id', adding no new semantics over the schema. Baseline 3 applies because the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get the full details of a single Sigistry plugin by its id') and enumerates the return content (install commands, component counts, security-audit result). This clearly differentiates it from siblings list_categories and search_plugins, which operate at a different scope and grain.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context — you call this when you already have a plugin id and want full details — which is clear from 'by its id'. However, it names no alternatives or exclusions, and the security-audit portion overlaps with the sibling verify_plugin without any guidance on which tool covers that need. Meaningful but implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Sigistry Plugin Catalog (formerly Claude Registry) tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool targets a distinct resource/action: plugin details, skill details, category listing, plugin search, skill search, and verification recipe. There is no meaningful overlap between tools, and the descriptions reinforce the boundaries clearly.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (get_, list_, search_, verify_). The singular/plural variation is conventional and does not create confusion.

Tool Count5/5

Six tools is well-scoped for a plugin and skill catalog: discovery, detail retrieval, category browsing, and verification guidance are all represented without redundancy. Each tool earns its place.

Completeness5/5

This covers the core catalog workflow: browse categories, search plugins/skills, fetch details or portable skill source, and obtain verification instructions. The verify_plugin handoff to a local script is intentional and provides explicit next steps rather than a dead end.

Resources

Need Help?