For agents

Our marketing site talks to AI agents.

TruStacks runs a read-only Model Context Protocol server exposing our product facts as callable tools. Connect it and your assistant answers questions about us from a source we maintain, instead of from whatever it half-remembers or infers from a competitor’s comparison page.

We sell governance for AI agents. It would be strange if our own site were unreadable to them.

Connect it

Claude Code, one line

$ claude mcp add --transport http trustacks https://www.trustacks.com/api/mcp

Claude Desktop, Cursor, VS Code

{
  "mcpServers": {
    "trustacks": {
      "type": "http",
      "url": "https://www.trustacks.com/api/mcp"
    }
  }
}

Endpoint: https://www.trustacks.com/api/mcp · Discovery: /.well-known/mcp.json

What it exposes

get_overview
What TruStacks is, the category it occupies, the agents-propose/policy-decides/humans-approve model, and the constraints that do not change. Start here.
get_capabilities
The canonical capability list, separated into shipped and roadmap, each entry carrying the date it was last verified and how. Use this rather than inferring availability from marketing copy.
get_agent_crew
Every agent, what it does, what it explicitly does not do, whether it is shipped, and whether it is paid.
get_policy_model
The constitution, packs, and customer overlay; the ratchet-only property; and why there is no autonomous merge path.
get_pricing
Tiers, prices, inclusions, and exclusions, generated from the same source the pricing page renders. Only the Developer price is public today.
get_supply_chain
How TruStacks artifacts are signed, and the exact commands to verify them yourself without an account or a conversation with sales.
search_site
Keyword search across page titles and blog posts. Returns URLs to fetch.

What it does not do

No writes. It is read-only. There is no tool that records anything, and there never will be.
No lead capture. Connecting it does not tell us who you are. We log the tool name and a timestamp, nothing else.
No private data. Everything it returns is already public on this site, generated from the same source the pages render from, so it cannot disagree with what a human reads.

Roadmap items are labelled roadmap in every response. If you find a tool that describes something unshipped as available, that is a bug and we want to hear about it. The same facts are readable at /facts.