Skip to content
Terraphim Skills logo

Terraphim Skills MCP server

Which MCP servers are Terraphim Skills's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-28

← Back to Terraphim Skills

Whose server it is
  • Registry namemd.terraphim-skills/terraphim-skillsverified in the MCP registry

The registry name sits under terraphim-skills.md. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-28
  • Stateanswerschecked 2026-10-28
  • Tools3
  • Server calls itselfterraphim-skills-public
  • Server version0.1.2
  • Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 123 ms.

Should an agent connect itSkip it
  • Its tools do none of the product's use cases we checked: install a signed skill into Claude with one command; triage and prioritise Gitea issues into a ready-task list; review Rust and WebAssembly code for bugs and security issues.
  • Checked on 5 of the 7 days it takes to judge reliability.

Once connected

  • Parameters are untyped or undescribed in 3 of 3 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 5, the first on 2026-10-28
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
  • What an agent can do with it0 of 3 use cases
  • Answeredmeasuring5 of the 7 daily checks it takes to print a share
  • Median first answer245 ms
  • Space in an agent's context≈ 223 tokensthe definitions of all its tools (3), which an agent carries on every turn
  • Tool definitionsC · 67 of 100
  • Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 3 of 3
  • Not saying whether it only reads or can destroy: 3 of 3

What an agent can do with it

  • cannot · install a signed skill into Claude with one command
  • cannot · triage and prioritise Gitea issues into a ready-task list
  • cannot · review Rust and WebAssembly code for bugs and security issues

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers3 tools · read 2026-10-28
  • list_skills

    List public Terraphim marketplace catalogue metadata, optionally filtered by tier

  • search_skills

    Search public Terraphim marketplace catalogue metadata by keyword

  • show_skill

    Show public metadata for a single skill; full content remains gated

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "terraphim-skills": {
      "type": "http",
      "url": "https://mcp.terraphim-skills.md/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http terraphim-skills https://mcp.terraphim-skills.md/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.terraphim-skills.md/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.