Check

Name: Check
Author: getstub

作者：getstub版本 0.1.0i★ –i在你的电脑上运行

注册名称dev.getstub/check

安装

概览

作者提供的说明（英文原文）

Verify what an AI agent did for someone, and what commercial influence the operator disclosed.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： STUB_REGISTRY

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "check": {
      "command": "npx",
      "args": [
        "-y",
        "@getstub/mcp-check"
      ],
      "env": {
        "STUB_REGISTRY": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add check --env STUB_REGISTRY=your-value -- npx -y @getstub/mcp-check

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "check": {
      "command": "npx",
      "args": [
        "-y",
        "@getstub/mcp-check"
      ],
      "env": {
        "STUB_REGISTRY": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "check": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@getstub/mcp-check"
      ],
      "env": {
        "STUB_REGISTRY": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

STUB_REGISTRY env
Registry host to resolve receipts against. Defaults to https://api.getstub.dev

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

✓ 通过
作者与仓库一致
注册名称已通过域名 getstub.dev 验证（注册中心会核实域名所有权）
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32466 个服务器的 0%
发布到注册中心的时间比此分类中其他 32466 个服务器的 43% 更新
基础检查结果等于或优于此分类中其他 32466 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Check 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.1.0）于2个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, HotCodePush

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211昨天更新

安装

HotCodePush

作者：hotcodepush-team

Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.

在云端运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Stub recipes

Working reference integrations for Stub, the allegiance receipt registry for AI agents.

Each recipe is a runnable agent with Stub wired in at the line where the ranking picks a winner. Clone one, run it, read the receipt it produces.

Every recipe here is a reference and a simulation. No real merchants, no real money, no real users. Nobody is running these in production, and each README says so. The point is to show exactly where a receipt belongs in code you recognise.

The recipes

Recipe	What it shows	Language
`tool-loop`	The primitive every framework wraps. A model, two tools, a loop.	JavaScript
`acp-commerce`	Allegiance lives upstream of checkout, in the ranking.	JavaScript
`mcp`	A public check server any agent can add, plus the operator issuing pattern.	JavaScript
`langchain-python`	The same integration inside a LangChain agent.	Python
`vercel-ai-sdk`	The biggest agent surface in JavaScript.	JavaScript
`insurance-advice`	The primitive outside commerce, with real stakes.	Python

Every recipe runs against the live registry and issues real receipts, under an operator id you choose. The free tier is 1,000 stubs a month, so trying all six costs nothing. There is no offline mode and no mock registry: the only way to issue a stub is to issue one.

The badge above

These recipes are exercised against the live registry every day, and the badge is drawn from the receipts that run produces. It is not a build status: it says the reference agents ranked their catalogues, disclosed what influenced the result, and issued signed records anyone can open. Click it to read them.

If it ever goes quiet, the recipes stopped working and this repo is telling you so before you clone it.

Start here

If you are new to this, read tool-loop first. It is the smallest one and it carries the lesson the others repeat: the model does nothing wrong, the ranking decided.

cd tool-loop

npm install export STUB_OPERATOR_ID=op_yourname_toolloop npm run demo

Pick an operator id that is yours. The first run registers it and saves your keypair to .stub-keys.json, which is gitignored. Every run after that uses the same identity.

The demo prints the ranking your code produced, with the reason beside each item, and then a receipt link anyone can open.

When you are ready to deploy

The recipes generate a fresh keypair each run, which is right for reading and wrong for production. PRODUCTION.md covers what changes: persisting your identity, where the receipt belongs, what never goes in the free text, and the mistakes we made taking our own agent live.

What a stub is

When your agent acts for someone, it issues a small signed record: who asked, what was done, what money moved, and what commercial influence applied. The person served checks it at a neutral registry, not on your servers and not on ours.

Here is a live one before you install anything:

https://api.getstub.dev/check/72b4baee1719ec34acc5df5c514a12fd2e19b9a6776de4b45706988f765c77d8

The integration, in full

import { Stub, influenced } from '@getstub/agent';

const stub = new Stub({ operator: 'Your Agent', declared: { paid_by: 'the user, subscription', conflicts: ['commission'], }, });

// at the line where your ranker picks a winner: const inf = []; if (pick.paid_placement) inf.push(influenced.placement(pick.seller)); if (pick.commission_pct) inf.push(influenced.commission(pick.commission_pct + '%'));

const receipt = await stub.issue({ principal: user.id, // hashed on your side, never sent raw agent: 'your-agent', requested: query, done: booked ${pick.name}, value_moved: { amount: pick.price, currency: 'USD' }, not_disclosed: inf, // an empty array is signed proof none applied });

Python is the same shape:

from getstub import Stub, influenced

Two things that keep coming up

Nobody hand writes disclosures. Your ranking code already knows when a commission or a placement fee shaped a result, because it applied it. The receipt reads the same flags at the same line. It scales the way your ranking scales.

An empty disclosure is not nothing. It is a signature saying conflicts exist in your business and none of them touched this action. That is worth more than silence, and it is why honest operators have something to gain here.

Install

npm install @getstub/agent

pip install getstub

Both clients sign over the same canonical form, verified rather than assumed: the Python test suite signs a stub and has the registry code verify it.

Free tier

1,000 stubs a month. Checking is free forever, because charging the person being served to verify would defeat the point.