SpineFrame
Run agent workflows with signed provenance, compliance audits, and OSINT checks through a governed MCP runtime.
Overview
SpineFrame is a Ship-phase MCP server that provides a governance runtime for AI agents with signed provenance, compliance audits, and OSINT.
What is this MCP server?
- Governance runtime for AI agents with signed provenance
- Compliance audit capabilities for agent runs
- OSINT-oriented tooling in the same MCP surface
- PyPI package with uvx runtime hint (spineframe)
- Configurable runs directory and providers.json via environment variables
- Server version 1.1.2
- PyPI identifier spineframe with uvx runtime hint
- Environment variables SPINEFRAME_RUNS_DIR and SPINEFRAME_CONFIG
What problem does it solve?
Agent runs leave weak audit trails and no standard way to prove compliance or attach verifiable provenance to outputs.
Who is it for?
Builders shipping agent-facing products who need provenance, policy checks, and structured run artifacts before going live.
Skip if: Hobby scripts with no compliance needs, or teams wanting a simple CRUD API without governance concepts.
What do I get? / Deliverables
After install, agents can execute inside a governed runtime that records runs, supports audits, and surfaces OSINT-aligned checks via MCP.
- Governed agent run storage under configured runs directory
- MCP-accessible compliance and provenance workflows
- OSINT-aligned capabilities bundled in the governance runtime
Recommended MCP Servers
Journey fit
How it compares
Agent governance MCP runtime, not a generic logging SaaS or a single prompt-based security skill.
Common Questions / FAQ
Who is SpineFrame for?
Indie and small-team builders running AI agents who need signed provenance, compliance audits, and OSINT hooks in one MCP server.
When should I use SpineFrame?
Use it when you are hardening agent workflows pre-launch or operating regulated-ish features that require auditable run history.
How do I add SpineFrame to my agent?
Register the PyPI stdio server spineframe (uvx runtime hint), set SPINEFRAME_RUNS_DIR and SPINEFRAME_CONFIG as needed, then expose tools to your MCP client.