Claim

io.github.LAHutchins91v1.0.1更新於 Oct 5, 2026

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

已驗證Streamable HTTP可網頁執行Productivity & WorkflowKnowledge & Memory

概覽

AI 產生的概覽

讓助理讀取品牌的已核准聲明、優惠、佐證、語氣與禁用詞句，並據此檢查草稿文案。

功能
Claim 會保存品牌的已核准聲明、目前優惠、佐證、語氣指引與禁用詞句，並提供工具來列出品牌、建立品牌、讀取品牌指南、儲存或移除聲明、優惠、佐證、語氣與禁用詞句，以及檢查草稿文案。檢查工具會標出虛構保證或折扣、使用禁用詞句，或聲明不在有效優惠範圍內的草稿；它不會儲存草稿。佐證用來說明某則已儲存聲明的依據，並不代表核准新的表述。
適用情境
適合行銷或品牌團隊，其助理需要撰寫文案並受已核准聲明與有效優惠約束。當草稿文案必須在交付前自動檢查而非人工審閱時，值得加入。
執行需求
遠端 Streamable HTTP 端點，位於部署的 /mcp 路徑，需透過 OAuth 登入 Claim 帳號；不接受 API 金鑰。品牌工具需要 Pro 訂閱或有效試用。自架需要 Node.js、依提供的 schema 設定的 Supabase 資料庫，以及包括 SUPABASE_URL、SUPABASE_ANON_KEY、SUPABASE_SERVICE_ROLE_KEY、STRIPE_SECRET_KEY、STRIPE_WEBHOOK_SECRET、STRIPE_PRICE_MONTHLY、STRIPE_PRICE_YEARLY 與 APP_BASE_URL 在內的環境變數。
安裝前請注意
透過 OAuth 登入；文件說明不要把 API 金鑰或密碼貼到標頭中，且 Claim 不接受 API 金鑰。品牌工具需要付費 Pro 方案或試用，帳務由 Stripe Checkout 處理。save_approved_claim、save_offer、save_proof、save_brand_voice、save_banned_phrase 與 remove_banned_phrase 等工具會寫入品牌指南，create_brand 會新增品牌。自架需要 Supabase 服務角色金鑰與 Stripe 密鑰，應設在主機環境中而非儲存庫中。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Claim，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "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.

來源：README.md，提交 db4fc1e

工具

0
工具後設資料尚未被收錄。

版本歷史

1
  1. v1.0.1最新Oct 5, 2026