Skip to content

SkillTriage

dev.moorai/skilltriagemoorai.devstreamable-httpv0.6.1Scanned

Scan AI agent skills, MCP server packages and MCP configs before you install them. Static analysis.

4 tools: 3 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 3 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 2 findings, 2 high

Anlyon alternative

3 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 3Claude Code: ask
  • scan_mcp_configCheck a pasted MCP client config (.mcp.json, claude_desktop_config.json, mcp.json, Codex config.toml).2 findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • High

      The description refers to ".mcp.json" and "claude_desktop_config.json".

      Matched text

      description: "Check a pasted MCP client config (.mcp.json, claude_desktop_config.json, mcp.json,..."

      What this check looks for
    • High

      The input schema at properties.filename.description refers to ".mcp.json".

      Matched text

      inputSchema.properties.filename.description: "...name, ending in .json or .toml (default .mcp.json)"

      What this check looks for
    Description, as the server wrote it
    Check a pasted MCP client config (.mcp.json, claude_desktop_config.json, mcp.json, Codex config.toml). Reports each npm or PyPI launch by its position and how its version is pinned (exact, @latest, a tag or range, none), flags releases on the known-compromised list, and runs static analysis over the text. Server names, package names, arguments, env and header values are never returned or stored; remove secrets before sending anyway. Static analysis only; nothing is run or fetched. Returns a verdict (CLEAN, CAUTION, REVIEW, DO-NOT-INSTALL or NAME-NOT-PUBLISHED), the pinning advice and a permalink.

    Annotations the server declares

    • title: Check an MCP config
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • scan_packageDownload one published package and run static analysis on its code with MoorAI's open-source engine.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Download one published package and run static analysis on its code with MoorAI's open-source engine. npm and PyPI packages also get ten MCP pre-install checks on their registry metadata, a reputation score and a known-compromised release check. Static analysis only: the package is never installed and the server is never run. Returns a verdict (CLEAN, CAUTION, REVIEW, DO-NOT-INSTALL or NAME-NOT-PUBLISHED), content-free findings (threat ids, categories, file paths, hashes; never file contents) and a permalink. The package name and version are sent to its registry. A completed analysis is reused for 24 hours; a new one can take a minute and runs one at a time.

    Annotations the server declares

    • title: Scan a package
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • scan_skillScan one agent skill or instruction file (SKILL.md, AGENTS.md, a tool.json, any text file) with MoorAI's open-source engine.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Scan one agent skill or instruction file (SKILL.md, AGENTS.md, a tool.json, any text file) with MoorAI's open-source engine. Static analysis only; nothing is run. The text is written to a temporary directory, scanned and deleted; only its hash, the verdict and content-free findings are kept. Returns a verdict (CLEAN, CAUTION, REVIEW, DO-NOT-INSTALL or NAME-NOT-PUBLISHED), the findings and a permalink.

    Annotations the server declares

    • title: Scan a skill file
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • lookup_verdictLook up the verdict the public catalogue has published for an MCP server package on npm or PyPI.No findings

    Why it is in this group

    • The name "lookup_verdict" says "lookup": a word for reading.
    Description, as the server wrote it
    Look up the verdict the public catalogue has published for an MCP server package on npm or PyPI. Returns found:false when the catalogue has no published verdict for that name; that is not a clean result. Nothing is downloaded or scanned. This request names the package to the server; to match without naming it, download /api/reputation-feed.json and match on your side.

    Annotations the server declares

    • title: Look up a verdict
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Findings

Matches of fixed checks, with the text they matched.

2 high
  • The description refers to ".mcp.json" and "claude_desktop_config.json".

    Matched text

    description: "Check a pasted MCP client config (.mcp.json, claude_desktop_config.json, mcp.json,..."

    What this check looks for
  • The input schema at properties.filename.description refers to ".mcp.json".

    Matched text

    inputSchema.properties.filename.description: "...name, ending in .json or .toml (default .mcp.json)"

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.6.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http skilltriage https://skilltriage.moorai.dev/mcp
claude mcp add --transport http skilltriage https://skilltriage.moorai.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__skilltriage__lookup_verdict"
    ],
    "ask": [
      "mcp__skilltriage__scan_package",
      "mcp__skilltriage__scan_mcp_config",
      "mcp__skilltriage__scan_skill"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as skilltriage. Review it before you use it.

Capability tags behind 1 rule
  • mcp__skilltriage__scan_package untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/dev.moorai/skilltriage/verify?hash=afa9009eae6232d833b99c081efa7453912324d2c193eb56f83728f5d7e1d5ab" | jq -e '.changed == false'

Pinned hash afa9009eae62, from Oct 31, 2026, 19:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/dev.moorai/skilltriage/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

anlyon.dev badge for dev.moorai/skilltriage
[![anlyon.dev](https://anlyon.dev/badge/dev.moorai/skilltriage.svg)](https://anlyon.dev/servers/dev.moorai/skilltriage)

Source: MCP Registry. Synced Oct 31, 2026, 19:17 UTC.