
Trusty Squire
io.github.Trusty-SquirePublished by GitHub account Trusty-Squirev1.0.33Updated Oct 24, 2026
Credential broker that signs your AI agent up to SaaS dev tools, within a signed spending mandate.
Overview
A local credential broker that lets an AI agent sign up for SaaS developer tools within a signed spending mandate.
- What you can do
- Trusty Squire is a credential broker for AI agents. According to its registry description, it signs an agent up to SaaS developer tools while keeping activity inside a signed spending mandate. The manifest lists no tools, so the specific operations it exposes are not documented here. It runs as a local process over stdio.
- When to use it
- Consider it when you want an agent to register for or provision SaaS developer tooling on your behalf and you need those sign-ups bounded by a spending mandate you have signed. It is not a fit if you need a documented tool list before installing, since none is provided.
- Requirements
- Runs as a local process on the user's machine over stdio, installed from the npm package @trusty-squire/mcp, so Node.js and npm are needed. The manifest declares no authentication, environment variables or headers. Desktop only; no web executable.
Installation
In SourceWeft
- Open Trusty Squire in the dashboard and add it to a workspace.
- 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
0Version history
1- v1.0.33LatestSep 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
