Claim

io.github.LAHutchins91v1.0.1Updated Oct 5, 2026

Approved claims, offers, proof, voice, and banned phrases for brand assistants.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Lets an assistant read a brand's approved claims, offers, proof, voice and banned phrases, and check draft copy against them.

What it does
Claim stores a brand's approved claims, current offers, proof, voice guidance and banned phrases, and exposes tools to list brands, create a brand, read the brand guide, save or remove claims, offers, proof, voice and banned phrases, and check draft copy. The check tool flags drafts that invent a guarantee or discount, use a banned phrase, or state an offer outside the active set; it does not save the draft. Proof explains why a saved claim exists and does not approve new language.
When to use it
Useful for marketing or brand teams whose assistants write copy and need it constrained to approved claims and live offers. Worth adding when draft copy must be checked before delivery rather than reviewed by hand.
Requirements
A remote Streamable HTTP endpoint at the deployment's /mcp path, with OAuth sign-in to a Claim account; no API keys are accepted. Brand tools need a Pro subscription or an active trial. Self-hosting needs Node.js, a Supabase database with the provided schema, and environment variables including SUPABASE_URL, SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY, STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, STRIPE_PRICE_MONTHLY, STRIPE_PRICE_YEARLY and APP_BASE_URL.
Before you install
Sign-in is through OAuth; the documentation says not to paste an API key or password into a header and that Claim does not accept API keys. Brand tools require a paid Pro plan or trial, and Stripe Checkout handles billing. Tools such as save_approved_claim, save_offer, save_proof, save_brand_voice, save_banned_phrase and remove_banned_phrase write to the brand guide, and create_brand adds a brand. Self-hosting requires the Supabase service role key and Stripe secrets, which should be set in…

Installation

In SourceWeft

  1. Open Claim in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "claim": {
      "type": "http",
      "url": "https://claim-continuity2.vercel.app/mcp"
    }
  }
}

README

Claim

Claim keeps a brand’s approved claims, current offers, proof, voice, and banned phrases, then lets an assistant read that guide before it writes. A check rejects draft copy that invents a guarantee, invents a discount, uses a banned phrase, or states an offer that is not in the active set.

It works with ChatGPT, Claude, Gemini, Grok, and Cursor, plus any other MCP client that can do Streamable HTTP and OAuth. It is not a ChatGPT-only plugin.

Sign in with your Claim account when the assistant opens OAuth. Do not paste an API key or password into a header. Claim does not accept API keys. Brand tools need Pro or an active trial. The site offers a 14-day trial, then Pro.

The MCP path on a deployment is /mcp. Registry metadata is in server.json (io.github.LAHutchins91/claim).

What the assistant can do

After you approve the connection, the server exposes these tools:

  • list_brands
  • create_brand
  • get_brand_guide
  • save_approved_claim
  • save_offer
  • save_proof
  • save_brand_voice
  • save_banned_phrase
  • remove_banned_phrase
  • check_brand_copy

check_brand_copy does not save the draft. Do not deliver copy when its verdict is rejected. Proof shows why a saved claim exists. It does not approve new language. Voice is tone, not permission to invent a promise. The assistant only calls these tools when you and the host allow it.

Connect

Cursor, in ~/.cursor/mcp.json or a project .cursor/mcp.json:

json
{  "mcpServers": {    "claim": {      "url": "https://YOUR_CLAIM_HOST/mcp"    }  }}

Claude Code:

bash
claude mcp add --transport http claim https://YOUR_CLAIM_HOST/mcp

Other clients: add the same URL, choose OAuth, and leave client id and secret empty. Claim supports dynamic client registration. Full steps for each assistant are on the connect page.

Run

bash
npm installnpm run buildnpm start

npm start runs node dist/src/server.js. When stdin is not a terminal, the process also speaks MCP on stdio so a sandbox can list tools without a token. A terminal keeps the HTTP listener only.

The server starts with empty Supabase and Stripe settings. Discovery (initialize, notifications/initialized, tools/list, and ping) does not need a user token. Saving or reading a brand requires a signed-in subscriber.

Copy supabase/schema.sql into the Supabase SQL editor before brand tools can read or write. Set these environment variables in the host, not in the repo:

  • SUPABASE_URL
  • SUPABASE_ANON_KEY
  • SUPABASE_SERVICE_ROLE_KEY
  • STRIPE_SECRET_KEY
  • STRIPE_WEBHOOK_SECRET
  • STRIPE_PRICE_MONTHLY
  • STRIPE_PRICE_YEARLY
  • APP_BASE_URL
  • PORT
  • OPENAI_APPS_CHALLENGE (optional)

Stripe Checkout shows the billing interval and trial before purchase.

Source: README.md at commit db4fc1e

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.1LatestOct 5, 2026