Ext Ops Panel
Open dashboard
Comparison

io.github.Garl-Protocol/agent-trust vs SpineFrame

io.github.Garl-Protocol/agent-trust is an MCP server published by Garl-Protocol. Marketplaces we read that list it: 1 (Official MCP Registry). SpineFrame is an MCP server published by Ratnaditya-J. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceio.github.Garl-Protocol/agent-trustSpineFrame
Official MCP Registry Listed, marked deprecated
Version: 1.4.3
Downloads/month (npm): 310
Downloads/week (npm): 27
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Listed
Version: 1.1.2
No figure published
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

io.github.Garl-Protocol/agent-trust vs SpineFrame
Factio.github.Garl-Protocol/agent-trustSpineFrame
Marketplaces that list it11
Stars (GitHub) (differs)2No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@garl-protocol/mcp-server)On your machine (spineframe)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 12, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/garl-protocol/garlgithub.com/ratnaditya-j/spineframe
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

io.github.Garl-Protocol/agent-trust

In its own words, on Official MCP Registry:

Tamper-evident action receipts, trust scoring & capability tokens for AI agents. 29 MCP tools.

SpineFrame

In its own words, on Official MCP Registry:

Governance runtime for AI agents with signed provenance, compliance audits, and OSINT.

How to run each

io.github.Garl-Protocol/agent-trust As a local MCP server: npm package

Claude Code
claude mcp add --env "GARL_API_KEY=<YOUR_GARL_API_KEY>" --transport stdio agent-trust -- npx -y @garl-protocol/mcp-server

Requires: GARL_API_KEY (secret)

SpineFrame As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio spineframe -- uvx spineframe

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only io.github.Garl-Protocol/agent-trust asks for

  • GARL_AGENT_ID
  • GARL_API_KEY (secret)
  • GARL_API_URL

Only SpineFrame asks for

  • SPINEFRAME_CONFIG
  • SPINEFRAME_RUNS_DIR

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: io.github.Garl-Protocol/agent-trust · What it can do: SpineFrame · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built