
Signato
io.github.Signato-aiPublished by GitHub account Signato-aiv0.13.1Updated Oct 24, 2026
Local confidentiality chamber: blocks the wrong AI output before it leaves the machine.
Overview
Signato is a local confidentiality chamber that checks AI output against a who-can-know-what matrix before it leaves the machine.
- What you can do
- Checks outgoing AI output against a local confidentiality matrix before it leaves the machine, blocking output the matrix does not allow. Reads the who-can-know-what rules from a matrix.yaml file whose absolute path is given in JOHARI_GUARD_CONFIG. Returns NOT_CHECKED and points to the quickstart command when no configuration is supplied. Runs as a local process on the user's desktop.
- When to use it
- Worth adding when an assistant's output may contain information that only certain people are allowed to see, and you want a local check before that output leaves the machine.
- Requirements
- Runs as a local process on the user's desktop (desktop only, not web executable), installed from the PyPI package signato over stdio. Needs a matrix.yaml file defining who-can-know-what, with its absolute path set in the JOHARI_GUARD_CONFIG environment variable; without it the server answers NOT_CHECKED.
Installation
In SourceWeft
- Open Signato 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- v0.13.1LatestSep 16, 2026
Score
25% 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
Declare a license in the repository or the registry entry.