convez.ai
MCP Server
usethrone

throne-ci

usethrone/throne-ci

Ver no GitHub
InicialPluginScore · de 0 a 100

Gate MCP servers in CI: execute in a microVM, test against Claude Code and Cursor, fail the build on the verdict.

Instalação

$npx convez-ai usethrone/throne-ci

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
2
Forks
0
Acompanhando
0
Saúde
50%
Último commit
há 3 meses
Versão
v1.0.0
Issues abertas
0
Contribuidores
1

README

A tradução para o português deste README ainda está na fila.

Throne MCP Gate

English · 简体中文 · Русский · हिन्दी · 日本語 · 한국어 · Deutsch

Throne MCP Gate on the GitHub Marketplace test License: MIT

Stop shipping MCP servers that break on real clients. This action executes your server in a disposable microVM, replays nine protocol steps against client behaviour calibrated from recorded Claude Code and Cursor traffic, scans the source for security issues, and fails the build when the verdict regresses.

Every run links to a public evidence record. Nothing is asserted without the execution that proved it.

- uses: usethrone/throne-ci@v1
  with:
    target: "@your-scope/your-mcp-server"
    api-key: ${{ secrets.THRONE_API_KEY }}

Why

Every MCP directory lists self-reported entries. Nobody runs the servers. Throne does: a fresh Firecracker microVM per scan, installed from npm, PyPI, or GitHub, launched over stdio, and torn down afterward. The result is a verdict you can gate a merge on, backed by evidence anyone can read.

Quickstart

Gate every pull request, and post the verdict back as a comment:

name: throne-gate
on:
  pull_request:

permissions:
  contents: read
  pull-requests: write   # lets the action post the verdict comment

jobs:
  gate:
    runs-on: ubuntu-latest
    steps:
      - uses: usethrone/throne-ci@v1
        with:
          target: "@your-scope/your-mcp-server"   # or "uvx your-package" / https://github.com/you/repo
          api-key: ${{ secrets.THRONE_API_KEY }}

Drop the permissions block if you do not want PR comments, or set comment-on-pr: false.

Inputs

inputrequireddefaultmeaning
targetyesnpm package (@scope/name or name), uvx <pypi-name>, or https://github.com/owner/repo
api-keyyesyour Throne API key. Keep it in repo secrets
fail-onnonot_fitcomma-separated verdicts that block the merge. Add inconclusive for strict mode
comment-on-prnotruepost a sticky verdict comment on the PR (needs pull-requests: write)
github-tokenno${{ github.token }}token used for the PR comment
api-basenohttps://api.usethrone.devoverride only for self-hosted or testing
timeout-secondsno600give up waiting for the scan after this long

Outputs

outputmeaning
verdictfit, not_fit, inconclusive, or unknown
reasonwhen inconclusive: needs_credentials, needs_arguments, needs_environment, unsupported_layout, install_timeout, no_handshake, or launch_error
security-verdictclean, review, or not_run
scan-idthe scan backing this verdict
record-urlpublic evidence record
summaryone-line verdict summary
      - uses: usethrone/throne-ci@v1
        id: throne
        with:
          target: "@your-scope/your-mcp-server"
          api-key: ${{ secrets.THRONE_API_KEY }}
      - run: echo "Verdict was ${{ steps.throne.outputs.verdict }} — ${{ steps.throne.outputs.record-url }}"

What the verdict means

  • fit — full protocol compatibility on both client profiles. Safe to ship.
  • not_fit — a real protocol failure. This is the only verdict that blocks by default.
  • inconclusive — the server ran but could not be fully assessed. The reason says why. The most common is needs_credentials: the server installs and launches cleanly, then exits asking for an API key. That is usually fine, so inconclusive does not block unless you add it to fail-on.

Security findings are a separate axis. A review security verdict is material for a human to read; it never changes the compatibility verdict and never blocks a merge on its own.

Strict mode

To also block when the server could not be assessed:

        with:
          target: "@your-scope/your-mcp-server"
          api-key: ${{ secrets.THRONE_API_KEY }}
          fail-on: "not_fit,inconclusive"

Auditability

This is a composite action. The entire gate is one readable shell script, throne-gate.sh: no compiled binary, no bundled JavaScript, no transitive dependencies. For a tool you put in your release path, you should be able to read every line it runs. You can.

Getting a key

Founding-customer keys are $29/mo with a 12-month price lock. Email hello@usethrone.dev or see usethrone.dev/pricing.

Wear the crown

If your server is fit, its evidence record offers a live README badge that re-renders from the latest scan. If a release ever breaks the verdict, the badge says so on its own.

License

MIT. See LICENSE.

Ver o original no GitHub

Bom para

Relacionados