Overture
Your coding agent posts its plan to a canvas you can edit, fill in and approve — and it waits there until you press approve.Read full description
SixHqLABSCO SUMMARY
Writes are refused until you confirm them.
The governance is the product, and it is specific: a write runs dry by default and mints a single-use, expiring plan token that has to be confirmed before anything changes; pricing, policy, proof and identity records are refused for autonomous mutation altogether, and unmapped kinds fail closed. Check which entitlement lane your plan is in before wiring an agent that needs to write — read and verification tools are the Free tier surface.
What it is
A remote MCP server for go-to-market teams. Positioning, proof points, brand voice, personas and validation rules live in a governed Truth Graph, and the server hands that context to MCP clients instead of copying company facts into each agent.
What you get
- Truth Graph search with provenance, so a fact arrives with where it came from
- Draft content validated against approved facts and guardrails before it ships
- Governed mutation: create and update records through dry-run and human-approved workflows
- Grounded collateral generated into quarantine, with preview and export gates, and re-rendered when the underlying story changes
- An AI search and GEO workspace — briefs, artifacts, evidence, goals, hosted sites and approval-gated publishing
- Readiness simulations and pre-call briefs
- 48 registered tools in total, with
tools/liston the live endpoint as the current surface
Requirements
An Assay account. The endpoint is https://app.assay.wiki/api/mcp/v2/mcp over streamable HTTP — Claude Code adds it with claude mcp add --transport http assay-truth-graph, and any client takes the same URL. Interactive clients get a browser OAuth prompt on first use; headless agents authenticate with an org API key from Assay Settings. Access is tiered: mcp_access covers read and verification tools from Free upward, mcp_control_access covers write and run tools from Scale upward.
Setup effort
One command plus a key — claude mcp add --transport http assay-truth-graph https://app.assay.wiki/api/mcp/v2/mcp, then supply credentials
USE CASES
01
Keeping generated copy factually straight
Validate the draft against approved facts and guardrails before it goes anywhere.
02
Giving several agents the same company truth
Point each client at one endpoint instead of pasting positioning into every system prompt.
03
Drafting collateral that stays current
Generate into quarantine and re-render when the underlying story changes.
04
Preparing for a customer call
Pull a pre-call brief built from the graph rather than assembling it by hand.
05
Letting an agent propose a change
Run the write dry, review the plan, and confirm the token if it is right.
BEFORE YOU INSTALL
What to know first
Requires
A client that can reach a remote MCP server over HTTP
INSTALLATION
Connect your client
Server setup
claude mcp add
Claude Code
TERMINAL
claude mcp add --transport http assay-truth-graph https://app.assay.wiki/api/mcp/v2/mcpHosted endpoint
ENDPOINT URL
https://app.assay.wiki/api/mcp/v2/mcpAdd this hosted endpoint to your MCP client using the credentials listed under Requirements.
MCP Clients
Codex
CODEX · TERMINAL
codex plugin marketplace add Assay-Org/assay-truth-graph-mcpThen install the Assay Truth Graph plugin from Codex Plugins.
