# SkillTriage (remote · skilltriage.moorai.dev)

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

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `skilltriage.moorai.dev`: 73/100 (this document), [markdown](https://verifymcp.io/servers/dev-moorai-skilltriage/skilltriage.md), [page](https://verifymcp.io/servers/dev-moorai-skilltriage/skilltriage)

## Channel facts

- Endpoint: `https://skilltriage.moorai.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.6.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-06.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 777 tokens (~194/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the SkillTriage MCP server?

SkillTriage is a hosted endpoint at https://skilltriage.moorai.dev/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.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "dev-moorai-skilltriage": {
      "url": "https://skilltriage.moorai.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-moorai-skilltriage": {
      "type": "http",
      "url": "https://skilltriage.moorai.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-moorai-skilltriage]
url = "https://skilltriage.moorai.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-moorai-skilltriage": {
      "type": "remote",
      "url": "https://skilltriage.moorai.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-moorai-skilltriage --url 'https://skilltriage.moorai.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-moorai-skilltriage:
    url: "https://skilltriage.moorai.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-moorai-skilltriage": {
      "Transport": "http",
      "Url": "https://skilltriage.moorai.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-moorai-skilltriage -t streamable-http -u 'https://skilltriage.moorai.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-moorai-skilltriage": {
      "type": "http",
      "url": "https://skilltriage.moorai.dev/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-06 (score 73, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-04 (score 72, +1)

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

### 2026-11-02 (score 71, +1)

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

### 2026-11-01 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 0.6.1 → 0.7.0

### 2026-10-31 (score 70)

First indexed and scored.

## MCP tools (4)

### `scan_package` (~197 tokens)

Scan an MCP server or skill package

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.

Input parameters:

- `ref` (string, required): npm:<name>[@version], pypi:<name>[==version] or github:<owner>/<repo>/<path>[@ref] (a folder, not a whole repository)

### `scan_mcp_config` (~189 tokens)

Check an MCP client config

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.

Input parameters:

- `filename` (string): The config's filename, ending in .json or .toml (default .mcp.json)
- `text` (string, required): The config file's text

### `scan_skill` (~138 tokens)

Scan an agent skill file

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.

Input parameters:

- `filename` (string): The file's name, which sets how it is analysed (default SKILL.md)
- `text` (string, required): The file's text

### `lookup_verdict` (~130 tokens)

Look up a published MCP server verdict

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.

Input parameters:

- `ecosystem` (string, required): The package registry
- `name` (string, required): The package name
- `version` (string): Optional: the version you plan to install; the reply says whether the published verdict is for it

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-moorai-skilltriage/skilltriage#diagnostics

## Score history

- 2026-11-06: 73
- 2026-11-05: 72
- 2026-11-04: 72
- 2026-11-03: 71
- 2026-11-02: 71
- 2026-11-01: 70
- 2026-10-31: 70

## Common questions

### What is the SkillTriage MCP server?

SkillTriage is an MCP server listed in the public MCP registry as dev.moorai/skilltriage. Scan AI agent skills, MCP server packages and MCP configs before you install them. Static analysis. This page covers its hosted endpoint (https://skilltriage.moorai.dev/mcp).

### Is the SkillTriage MCP server safe to use?

SkillTriage scores 73 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 SkillTriage MCP server expose?

SkillTriage exposes 4 tools: scan_package, scan_mcp_config, scan_skill, lookup_verdict. Their descriptions and schemas cost roughly 654 tokens of context every time the server is loaded.

### Does the SkillTriage MCP server require authentication?

No. We connected to SkillTriage without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SkillTriage MCP server still maintained?

SkillTriage is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the SkillTriage MCP server?

VerifyMCP ran 13 checks on SkillTriage, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://skilltriage.moorai.dev/mcp
- Website: https://skilltriage.moorai.dev/api
- Changelog RSS feed: https://verifymcp.io/servers/dev-moorai-skilltriage/skilltriage.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-moorai-skilltriage/skilltriage/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-moorai-skilltriage/skilltriage.json
- HTML version of this page: https://verifymcp.io/servers/dev-moorai-skilltriage/skilltriage