_ registry / mcp http-sse · checked 1h ago

sigistry

https://clauderegistry.com

Registry code: e116999ae2acecbc

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://clauderegistry.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is sigistry live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is sigistry free to use?
Yes — the hub reached it with no key and no payment.
What tools does sigistry have?
9 tools: get_scorecard, get_plugin, get_skill, search_skills, list_categories, verify_plugin, list_scorecards, search_plugins, ….
Is sigistry safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.6%

90 days 99.6%· all time 99.6%

latency
778ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 506 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • search claude code plugins
  • get mcp server scorecard
  • search agent skills
  • audit an mcp app for safety
  • get plugin install commands
takes → gives
text → data, text
tools
9 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
1

through this hub

calls served
2

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
6 open 3 never probed 6 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_skills reads open 19h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "query": {
          "type": "string",
          "description": "keywords, e.g. \"changelog\" or \"security review\""
        },
        "plugin": {
          "type": "string",
          "description": "restrict to skills shipped by this plugin id"
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • list_categories reads open 10h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • verify_plugin reads open 19h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "pluginPath": {
          "type": "string",
          "description": "local path to the plugin directory, used to fill in the run command (optional)"
        }
      },
      "additionalProperties": false
    }
    arguments 11 lines
  • list_scorecards reads open 10h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • search_plugins reads open 10h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "query": {
          "type": "string",
          "description": "keywords, e.g. \"database migration\""
        },
        "category": {
          "type": "string",
          "description": "e.g. \"database\", \"devops\", \"git\""
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • check_mcp_app reads open 19h ago

    Get the Sigistry MCP App safety criteria to audit an MCP App (MCP Apps / SEP-1865: a tool that returns an interactive ui:// HTML resource the host renders in a sandboxed iframe) BEFORE shipping it. Returns two groups of checks: spec conformance (ui:// scheme, the text/html;profile=mcp-app mimeType, tool-to-UI linkage via _meta.ui.resourceUri, a text fallback, visibility values, and CSP coverage of external origins) and security hygiene the iframe sandbox does not cover (unsafe DOM sinks, embedded secrets, host-message origin handling, remote scripts). Call this when the user is building or reviewing an MCP App; then apply each check to the app source you have in context and report findings. Nothing is sent to this server; an interactive browser version is at https://sigistry.com/mcp-app-checker.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • get_scorecard reads unknown 23h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "scorecard id, e.g. \"sigistry-catalog\" (find ids via list_scorecards)"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • get_plugin reads unknown 23h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "the plugin id, e.g. \"sql-safety-net\""
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • get_skill reads unknown 23h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "the skill name, e.g. \"assessment-scoring\" (find names via search_skills)"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id e116999ae2acecbc.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e116999ae2acecbc/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/e116999ae2acecbc/badge.svg)](https://brick.blue/agent/e116999ae2acecbc?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
2
ok
2
failed
0
success rate
100%
median latency
832ms
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

2 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.