Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.
Warning

Malware flagged

A supply-chain scanner flagged a high-severity malware risk in this package. Treat it as unsafe to install until the finding is cleared. See Supply Chain Security in the trust breakdown.

io.github.Trusty-Squire/mcp

NPM · @TRUSTY-SQUIRE/MCP · SCANNED AUG 3

Credential broker that signs your AI agent up to SaaS dev tools, within a signed spending mandate.

Available components

npm · @trusty-squire/mcp 32
+24 this week 32 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security43
  • Malware check failed: a supply-chain vendor flagged a high-severity malware risk. See how to fix → Fail
  • Only part of the dependency tree could be resolved (249 of 250), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (249 of 250), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Trusty-Squire/trusty-squire). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake.Unverified

Unverified: 4 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @trusty-squire/mcp

# add to Claude Code
claude mcp add trusty-squire-mcp -- npx -y @trusty-squire/mcp
# add to Codex CLI
codex mcp add trusty-squire-mcp -- npx -y @trusty-squire/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "trusty-squire-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@trusty-squire/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add trusty-squire-mcp --command npx --arg -y --arg @trusty-squire/mcp
# ~/.hermes/config.yaml
mcp_servers:
  trusty-squire-mcp:
    command: "npx"
    args: ["-y", "@trusty-squire/mcp"]
// mcp.json
{
  "mcpServers": {
    "trusty-squire-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@trusty-squire/mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Aug 26 +27
    • Malware scan: unverified → fail ▼ security
    • Known CVEs: unverified → partial ▲ security
    • Install scripts: unverified → pass ▲ security
    • Provenance: unverified → pass ▲ security
    • Stability: Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare. security
    • The attested source repository moved: Trusty-Squire/trusty-squire security
    • Maintenance: unverified → pass ▲ functional
    • License: unverified → pass ▲ functional
    • Dependency health: unverified → partial ▲ functional
    • Capabilities: Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake. functional
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
    • Licence: MIT functional
  • 1 Aug 26 −1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 −2
    • Malware scan: fail → unverified ▼ security
    • Malware indicator gptMalware:QYNePg-f168cNtprVghSrpcuU18QmRX0rjxyCFN1YMdc cleared ▲ security
    • Malware indicator gptMalware:QcYx91ARuAb0pPPXC9MDUlxZItkWiEBdt5YC_-O5I_Tg cleared ▲ security
  • 30 Jul 26 0
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
  • 28 Jul 26 0
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
  • 27 Jul 26 8

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/@trusty-squire/[email protected]

Provenance verified

Ecosystem: npm · Outcome: verified

Reason: verified

Source repo:
Trusty-Squire/trusty-squire
Certificate issuer:
https://token.actions.githubusercontent.com
Certificate SAN:
https://github.com/Trusty-Squire/trusty-squire/.github/workflows/release.yml@refs/heads/main
Rekor log index:
2044028867
Predicate type:
https://slsa.dev/provenance/v1
Subject digest:
sha512:3008453434efdae6d714056da694504d871c288d44061a045ebf6ba9a640f0a687e34728bb1416a0fac64ab5af6938792e3e9a3b5d38e6b63c4be6a15
Discovery method:
attestation_endpoint
Dependencies 249 packages

249 packages in the resolved dependency tree · 244 deprecated · 93 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.