Trusty Squire

ai.trustysquirePublished by trustysquire.aiv1.1.39Updated Oct 31, 2026

Provision, ship, and pay from your coding agent — keys and cards never leave the vault.

VerifiedSTDIODesktop onlyFinanceDeveloper Tools

Overview

AI-generated overview

Trusty Squire is a local stdio MCP server that lets a coding agent provision, ship and pay for things while keys and cards stay in a vault.

What you can do
  • The registry lists no tools, so capabilities are known only from its one-line description.
  • It is presented as a way for a coding agent to provision resources and ship work.
  • It also covers paying for things, with keys and cards said to remain in a vault rather than reaching the agent.
  • No further detail on commands, providers or workflows is published.
When to use it
Consider it if you want a coding agent to handle provisioning, deployment and payment steps without exposing credentials or card details to the model. The published information is too thin to judge fit for any specific provider or workflow.
Requirements
Runs as a local process over stdio, installed from the npm package @trusty-squire/mcp, so a Node.js runtime is needed. Desktop only; no web execution. No authentication, environment variables or headers are declared, though the vault it relies on is not described.
Before you install
It is described as handling payments and card details, so real money and financial credentials may be involved; how the vault is secured, funded and audited is not documented. Provisioning and shipping imply actions that create or change resources. No tool list, README or instructions are published, so review behavior before connecting it to anything live.

Installation

In SourceWeft

  1. Open Trusty Squire in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the server did not complete the MCP handshake.

Version history

42
  1. v1.1.39LatestOct 31, 2026
  2. v1.1.39-rc.1Oct 31, 2026
  3. v1.1.38Oct 29, 2026
  4. v1.1.37Oct 26, 2026
  5. v1.1.37-rc.1Oct 20, 2026
  6. v1.1.36Oct 17, 2026
  7. v1.1.35Oct 15, 2026
  8. v1.1.35-rc.2Oct 15, 2026
  9. v1.1.33-rc.1Oct 12, 2026
  10. v1.1.32-rc.1Oct 11, 2026
  11. v1.1.31-rc.1Oct 9, 2026
  12. v1.1.30-rc.1Oct 9, 2026
  13. v1.1.29Oct 9, 2026
  14. v1.1.29-rc.3Oct 9, 2026
  15. v1.1.29-rc.1Oct 8, 2026
  16. v1.1.28Oct 6, 2026
  17. v1.1.27Oct 4, 2026
  18. v1.1.27-rc.2Oct 4, 2026
  19. v1.1.26Oct 3, 2026
  20. v1.1.25Oct 3, 2026
  21. v1.1.25-rc.1Oct 3, 2026
  22. v1.1.24Oct 2, 2026
  23. v1.1.23Sep 29, 2026
  24. v1.1.22-rc.1Sep 29, 2026
  25. v1.1.20Sep 29, 2026
  26. v1.1.19Sep 28, 2026
  27. v1.1.19-rc.4Sep 27, 2026
  28. v1.1.19-rc.1Sep 27, 2026
  29. v1.1.18Sep 27, 2026
  30. v1.1.18-rc.1Sep 27, 2026
  31. v1.1.17Sep 24, 2026
  32. v1.1.16Sep 23, 2026
  33. v1.1.16-rc.6Sep 22, 2026
  34. v1.1.16-rc.5Sep 22, 2026
  35. v1.1.16-rc.3Sep 19, 2026
  36. v1.1.16-rc.2Sep 18, 2026
  37. v1.1.15Sep 18, 2026
  38. v1.1.15-rc.2Sep 17, 2026
  39. v1.1.14Sep 17, 2026
  40. v1.1.14-rc.34Sep 17, 2026
  41. v1.1.14-rc.33Sep 16, 2026
  42. v1.1.14-rc.31Sep 16, 2026

Score

35% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts