
SpineFrame
io.github.Ratnaditya-JPublished by GitHub account Ratnaditya-Jv1.1.2Updated Oct 25, 2026
Governance runtime for AI agents with signed provenance, compliance audits, and OSINT.
Overview
SpineFrame is a local governance runtime for AI agents, offering signed provenance, compliance audits and OSINT capabilities through an MCP stdio server.
- What you can do
- Provides a governance runtime for AI agents, covering signed provenance of agent activity, compliance auditing and OSINT work, as described in the registry entry. Runs locally over stdio and reads a providers configuration file plus a run-data directory. No individual tools are listed in the manifest, so the exact operations available are not documented here.
- When to use it
- Consider it when you need an agent's actions to be recorded with signed provenance, want compliance audits of agent runs, or need OSINT-style investigation support inside an MCP-connected assistant.
- Requirements
- Runs as a local process on the user's machine, launched with uvx from the spineframe PyPI package, so Python and uv are needed. Two environment variables configure it: SPINEFRAME_CONFIG points to a providers.json config file, and SPINEFRAME_RUNS_DIR sets where run data and artifacts are stored. Desktop only; no authentication is declared.
Installation
In SourceWeft
- Open SpineFrame 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.1.2LatestSep 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.