Skip to content

Add VerifiedState MCP extension for verified agent memory#8297

Closed
1vanbui wants to merge 4 commits into
aaif-goose:mainfrom
1vanbui:add-verifiedstate-extension
Closed

Add VerifiedState MCP extension for verified agent memory#8297
1vanbui wants to merge 4 commits into
aaif-goose:mainfrom
1vanbui:add-verifiedstate-extension

Conversation

@1vanbui
Copy link
Copy Markdown

@1vanbui 1vanbui commented Apr 3, 2026

Summary

Adds documentation for the VerifiedState MCP extension, which provides verified agent memory with cryptographic receipts.

What it does

VerifiedState adds a decision trace layer to Goose. Every assertion a Goose agent makes gets:

  • A cryptographic verification receipt (Ed25519 signed)
  • Evidence grounding (what supported the assertion)
  • Point-in-time queryability (reconstruct beliefs at any moment)
  • Conflict detection (contradicting assertions flagged)

MCP Tools

Tool Description
memory_ingest Store content as an artifact
memory_query Six-channel retrieval
memory_verify Produce signed receipt
memory_health Namespace health metrics

Why this matters for Goose

Goose handles ~90% of Block's code submissions. These are consequential decisions. When something breaks months later, teams need to know what Goose believed about the codebase when it made that choice. VerifiedState provides that audit trail.

Links

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5291271774

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@@ -0,0 +1,91 @@
---
title: VerifiedState Extension
description: Add VerifiedState MCP Server as a Goose Extension for verified agent memory with cryptographic receipts
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Use lowercase goose branding in docs

documentation/AGENTS.md explicitly requires the product name to always be written as lowercase goose across the documentation tree, but this new page introduces multiple Goose usages (starting in the frontmatter description and repeated throughout the body). This violates a documented repository standard and will produce inconsistent published docs unless all occurrences are normalized to lowercase.

Useful? React with 👍 / 👎.

@1vanbui
Copy link
Copy Markdown
Author

1vanbui commented Apr 4, 2026

Fixed — normalized all Goose references to lowercase goose per AGENTS.md standard.

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d531abbfd4

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment on lines +49 to +50
command="npx"
args={["@verifiedstate/mcp-server"]}
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Pass full command string to CLIExtensionInstructions

CLIExtensionInstructions renders the configured command from its command prop only, and does not consume an args prop (see documentation/src/components/CLIExtensionInstructions.tsx). With command="npx" here, the generated CLI walkthrough tells users to run just npx, so the extension command in goose configure is incomplete and will not start the VerifiedState server when users follow this section.

Useful? React with 👍 / 👎.

type="stdio"
command="npx"
args={["@verifiedstate/mcp-server"]}
envVars={["VERIFIEDSTATE_API_KEY", "VERIFIEDSTATE_NAMESPACE_ID"]}
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Provide envVars as key/value objects

This component expects envVars entries shaped like { key, value }, but this page passes plain strings. In CLIExtensionInstructions, those entries are destructured as objects when rendering the sample goose configure flow, so the environment-variable prompts render undefined names/values and give readers incorrect setup instructions for required credentials.

Useful? React with 👍 / 👎.

@1vanbui
Copy link
Copy Markdown
Author

1vanbui commented Apr 4, 2026

Both Codex review items addressed:

  1. Combined command + args into single command="npx @verifiedstate/mcp-server" (removed separate args prop)
  2. Changed envVars from plain strings to key/value objects: { key: "VERIFIEDSTATE_API_KEY", value: "your-api-key" }

- using-goosehints.md: Replace <details>/<summary> HTML tags with
  standard markdown numbered list + code blocks. The <details> tags
  inside a numbered list caused MDX compilation to fail with
  "Expected a closing tag for <details> before the end of paragraph".

- verifiedstate-mcp.md: Add GooseDesktopInstaller tab, goose://
  installer link, timeout prop, and infoNote — matching the exact
  pattern used by firecrawl-mcp.md and other working extensions.

Signed-off-by: Van Bui <1vanbui@users.noreply.github.com>
@1vanbui
Copy link
Copy Markdown
Author

1vanbui commented Apr 5, 2026

Fixed the deploy build failure. The issue was not in our MCP doc file — it was a pre-existing MDX compilation error in documentation/docs/guides/context-engineering/using-goosehints.md:

Error: MDX compilation failed for file "using-goosehints.md"
Cause: Expected a closing tag for `<details>` (156:4-156:13) before the end of `paragraph`

The <details>/<summary> HTML tags inside a numbered list with an interrupting paragraph caused MDX to choke. Replaced them with standard markdown numbered list + code blocks.

Also updated verifiedstate-mcp.md to exactly match the pattern used by other working MCP extensions (e.g., firecrawl-mcp.md):

  • Added GooseDesktopInstaller component for the Desktop tab
  • Added goose://extension? quick install link
  • Added timeout={300} and infoNote props
  • Added :::info node.js requirement note

All commits have Signed-off-by for DCO compliance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants