xsolana
作者：XGamesFun
Design, check, simulate and launch Solana game economies on loot, one shared program, no contract.
在你的电脑上运行今天更新
安装
FactStamp
概览
作者提供的说明（英文原文）
Verify a company, figure or citation before you rely on it. Card or crypto; signed receipt.
PopNx MCP 的三大支柱
这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。
- 用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
- 我们的基础检查i3 项中通过 3 项依据公开信息检查；尚未扫描代码
- 使用情况i尚未统计★ –
它能帮你做什么
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
- 连接方式: 在云端运行
- 传输方式: Streamable HTTP
- 分类: 加密货币与区块链
安装
选择你使用的 AI 应用，然后复制设置。
安装之前
- 基础检查：3 项中通过 3 项
- 在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
- 可以做 18 件事（工具） list_series, route_claim, list_card_packages, buy_card_package …
- 注册中心没有列出需要填写的密钥。
你需要
- 在云端运行无需安装任何东西，通过互联网连接
你用的是哪个应用？
在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude：
- 打开 Settings → Connectors
- 点击 Add custom connector
- 粘贴下面的地址，然后点击 Add
- 如果要求登录，请登录作者的服务
https://agents.factstamp.dev/mcp在终端中运行这条命令
claude mcp add --transport http factstamp https://agents.factstamp.dev/mcp或者自己复制设置
粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json
{
"mcpServers": {
"factstamp": {
"url": "https://agents.factstamp.dev/mcp"
}
}
}浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。
或者自己复制设置
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"factstamp": {
"type": "http",
"url": "https://agents.factstamp.dev/mcp"
}
}
}浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。
ChatGPT 只能连接互联网上的服务器：
- 打开网页版 ChatGPT → Settings → Connectors (Apps)
- 点击 Create 或 Add（部分套餐需要先在 Advanced 中开启 Developer mode）
- 粘贴下面的地址，起个名字，然后保存
- 如果要求登录，请登录作者的服务
https://agents.factstamp.dev/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上，无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。
它能做什么
工具名称和描述与服务器在 2026年11月7日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。
list_seriesIncluded. What this engine covers, the publisher and as-of date behind each series, and the no-guess rule.
route_claimIncluded. Shows which series a claim would be routed to, the value and date extracted, and the signals behind the score. Returns NO verdict — pay for check_figure when you want one.
list_card_packagesIncluded. The one-off card packages as one machine-readable catalogue: the 11 products and their 13 prices in Australian dollars, the unit one payment buys for each SKU, what the package returns, and where the input is sent. One payment each, nothing metered, nothing subscribed.
buy_card_packageIncluded. Opens a Stripe Checkout Session for one card package and returns its payment link and its session id. This tool charges nothing and produces no artefact: on the card rail the thing that taps is a human. The package's work runs only at its redeem path, after Stripe's own
check_figureSubmit the dated figure you are about to act on. Returns verified, stale, contradicted or unknown, cited to the publisher's own series with its as-of date. Relevant wherever a number is going onto a page, deck or decision. Not advice. Comes with an Ed25519-signed receipt covering
check_entityVerify a legal entity: does this company exist, under which identifier and jurisdiction, and is its registration current? Cited to open primary registers (the GLEIF LEI index and US SEC EDGAR). Returns found, ambiguous, not_found or unknown; a near name match is never reported as
check_entity_fileThe entity file: ONE paid answer holding everything we hold about one company: the whole picture in ONE call rather than four separate facts stitched together, at the point of signing, onboarding, paying or acquiring a counterparty. It holds identity and standing, the registered
check_entity_file_ilIsraeli company lookup and company register check by company number (nine digits, with its own check digit) or by registered name, Hebrew or English: identity, corporation type, the register's own status and sub-status, description and stated purpose, incorporation date, governme
check_entity_file_caCanadian company lookup and Canadian federal corporation register check by nine-digit Business Number (BN) only: corporation number, BN, governing legislation, every registered name with type, current flag and effective date, the register's own status, the registered address, the
check_sanctionsSanctions screening of a name, for whether a person or company is on a sanctions list — and which one. Reads OFAC SDN, the UN consolidated list, the EU Financial Sanctions File and the UK Sanctions List, and returns listed, mismatch, not_found or unknown. The answer names the lis
check_vatAn EU VAT number check — VAT validity, and the VAT registration behind it. Reads the official VIES service (European Commission), keyless. Returns valid, invalid or unknown — an outage is NEVER reported as invalid — with the member state, the register's own request date, and the
verify_citationSays whether a citation can be repeated. Submit a DOI, an arXiv ID or a paper title: returns whether it exists, what it is (title, authors, year, container) and whether it has been retracted, cited to Crossref and arXiv. Optionally send what your document claims (title, authors,
verify_packageReports on a dependency at the point of installation. Submit a package and version plus its ecosystem: returns whether that exact version exists, whether it is yanked or deprecated, and every advisory OSV lists against it. An invented version returns not_found with the real versi
watch_addWatch ONE citation or ONE package version instead of checking it once. Send kind ('citation' or 'package') and the subject (a DOI, an arXiv ID or a title; or npm:express@4.18.2). The first check is answered immediately and signed, then re-checked daily for 30 days; every real cha
watch_portfolioWatch a whole list instead of one reference at a time: up to 25 citations or package versions re-checked every day for 30 days under one token. US$5 a portfolio — 20 cents a reference, under a cent a check — and the first check on every reference is answered and signed immediatel
verify_bulkCheck a whole list in one call: a bibliography or a dependency manifest. Send items[] of {tool, input} or the citations[]/packages[] shorthand. Up to 12 items at a flat US$0.12 on this door; longer lists pay 0.016667 an item on the pack-funded HTTP door (POST /bulk, up to 25 item
check_documentA whole document in one call: the claims that can be verified against a primary source, each answered by the door that owns it with its own signed receipt, plus one receipt over the document. Extraction is mechanical, so the claim list and the count are reproducible from your doc
audit_claimsAudit what an agent believes about companies. Send up to 10 claims ({subject:{identifier|name|jurisdiction}, field, value}) and get, claim by claim: supported (the register says this), contradicted (it says something else, shown), stale (the register records it as FORMER, with th
基础检查i
我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
- ✓ 通过
作者与仓库一致
注册名称已通过域名 alpineai.com.au 验证（注册中心会核实域名所有权）
- … 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
- … 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
- ✓ 通过
端点有响应
在 1086 毫秒内响应（HTTP 200）
- – 不适用
使用 OAuth 登录
无需登录
- ✓ 通过
工具描述中没有隐藏指令
已读取 18 个工具描述，未发现针对 AI 的隐藏指令
与“加密货币与区块链”中的其他服务器比较i
- 星标数多于此分类中其他 1614 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 1614 个服务器的 84% 更新
- 基础检查结果等于或优于此分类中其他 1614 个服务器的 100%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。
常见问题
FactStamp 安全吗？
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。
它需要哪些密钥或代码？
注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端？
它在作者的云端运行。通过互联网连接，无需安装，但你发送的内容会经过作者的服务器。
它还在维护吗？
GitHub 仓库最后更新于–，最新版本（0.1.4）于10天前进入注册中心。
哪些应用可以使用它？
支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。
有什么可以替代它？
同一分类中有：xsolana, CashPan, Agentwallet
替代选择
同一分类中其他作者的服务器，按星标数排序。
如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
CashPan
作者：cashpan.app
Give your AI an allowance: pay approved people within on-chain spending limits.
在云端运行今天更新
安装
Agentwallet
作者：hifriendbot
Wallet infrastructure for Ai agents. EVM + Solana. x402 payments. No KYC.
在你的电脑上运行今天更新
安装
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
FactStamp
Paid verification for agents, and a public record of every paid answer. Each call returns a cited, dated finding with a signed receipt you can verify offline, without asking us. Each settled call is written into a public log, and each day's root is stamped onto the Base blockchain whenever that day held a payment from someone other than us. When a check has to stay confidential there is a private option: a flat US$25 on top of the call price seals the request, so the world can see that a call happened and prove it later, but never learn what was asked. No model sits in the verdict path, and unknown is a first-class answer.
Live service: https://agents.factstamp.dev
What this repository is
The published machine interface of the FactStamp service, mirrored here so it can be read, diffed and cited without a wallet. Each row names the live route the copy came from, so any file here can be checked against the service in one request:
| File | What it is | Live source |
|---|---|---|
openapi.json | The OpenAPI 3.1 description of every route. | https://agents.factstamp.dev/openapi.json |
llms.txt | The plain-language map of the service: what each tool costs, what it returns, what it refuses to claim. | https://agents.factstamp.dev/llms.txt |
coverage.json | Which registers are read, per jurisdiction, section by section, with the price of each door. | https://agents.factstamp.dev/coverage.json |
server.json | The MCP registry manifest — the entry submitted to the official registry, not a route the service serves. | https://agents.factstamp.dev/.well-known/mcp.json (the live descriptor) |
These are dated snapshots, not a live feed. Coverage and prices move as registers change, so a copy here can lag the service. When the two disagree, the live route wins — fetch it and believe that, not this. The files exist so a person or an agent without a wallet can read the interface, and so a reader can cite exactly what was published on a given day.
The service's private source is not published here.
Routes
| Route | Purpose | Access |
|---|---|---|
/mcp | MCP endpoint — the tool surface agents call. | — |
/health | Service status: name, network, judge and registry versions. | open |
/openapi.json | Machine description of every route. | open |
/llms.txt | The service explained for readers. | open |
/coverage.json | Per-jurisdiction coverage and prices. | open |
/samples | Example answers, so you can see the shape before paying. | open |
/ledger/root | The public record: today's root, the last 30 daily roots, and each day's verdict. | open |
/ledger/zero-knowledge | The private-request option: what it is, what it publishes, what it costs. | open |
Paid routes include /citation, /package, /check, /entity, /entity-file, /bulk, /document, /watch, /watch/portfolio, and /verify for receipt checking. Prices are published, per call, in the files above rather than in prose here.
Published prices at the time of writing
Taken from /health and /llms.txt as served:
- figure door — US$0.05
- entity door — US$0.10 to US$0.25, set by the depth of the country you ask about: US$0.10 for a country publishing 1–4 verifiable items, US$0.15 for 5–6, US$0.20 for 7–9, US$0.25 for Australia's fifteen. The quote is shown in the payment challenge, before any money moves, and a country whose register cannot answer today is not sold at all — it is refused with no price rather than charged for an "I don't know".
- entity file — US$0.438119 (33p in the UK, at the dated rate carried on the answer and the receipt)
- citation — US$0.02, package lookup — US$0.02
- standing work: watch US$0.50, whole document in one call US$0.25, bulk at a flat US$0.12
- company packages: US$2.00 and US$10.00, one-time, from the human page at
/company
If a number here ever disagrees with llms.txt or openapi.json as served, the served file wins.
Receipts
Every paid answer carries a receipt signed with Ed25519 over the exact findings and the file's hash, so a third party can verify it offline against the published issuer and key document — no call back to us, and no trust in our uptime. The key document at /.well-known/factstamp-issuer.json states exactly which bytes the key identifier is derived from and carries a worked example, so the derivation can be reproduced in any hash tool. A receipt proves *that FactStamp said this, on this date*. It does not prove that the register itself is right, and nothing in this service claims it does.
The public record: the ledger, and what is stamped on Base
Every settled paid call, over HTTP and over MCP alike, appends one entry to a public log. The log is an RFC 6962 Merkle tree; each UTC day's log reduces to a single root, published at /ledger/root along with the last thirty days.
A day's root is written to the Base blockchain — one small data-only transaction, magic 0x46535401 followed by the 32-byte root — only when that day held at least one settlement paid by someone other than us. Our own test payments never anchor a day. The rule exists so that an anchor means something: a day is stamped because a stranger paid, not because we were busy.
Days already written (verifiable on Base, chain id 8453):
| Day | Transaction |
|---|---|
| 2026-10-23 | 0x3bd942ae61c053aa7218ebfe44c25db2d9726412a67ec75073267cfb376d38f3 |
| 2026-10-25 | 0xa80b18f7d829fe535d86a700daa98f7f69f183877f158f1f0b2094dd2a94138f |
A day that held no outside payment is published with the verdict that says so, rather than being quietly left blank. The honest limit: an anchor proves the root was committed publicly on the day the transaction landed, not on the day of the payment — the payment itself is already a public record, because it is a transfer on the same chain. The anchor adds our side of the story: that the answers we gave were fixed before anyone asked to see them.
Private requests: the sealed-entry option
By default a paid call's entry is published in full — the door, the price, the verdict, and the fact that the call happened. For a caller who needs the call itself to stay confidential there is a `zero_knowledge` option, declared on the request.
- Price: US$25.00 in addition to the call's own price. A US$0.10 entity check declared private costs US$25.10. The payment challenge quotes the total before anything is paid.
- What is published: an
entry_id, the day, the price, the scheme (salted_commitment_v1) and the network. Nothing else. - What is sealed: the question, the answer and the verdict. The entry is committed to with a salted hash, so its existence and its position in the log are public while its contents are not.
- What that buys: you can prove later that a specific call happened on a specific day — by revealing the salt to whoever needs it — without ever having published what you asked.
The private option is documented at /ledger/zero-knowledge, with its own root at /ledger/zero-knowledge/root and its entries at /ledger/zero-knowledge/entry/{entry_id}. It is an option on the paid doors, not a separate service.
What this service is not
- Not a KYB provider, and not a substitute for one. It does not perform customer due diligence on anyone's behalf.
- Not complete by assertion. Any register we did not consult is named on the answer as not consulted. A register we could not read returns
unknown, nevernot found. - Not a fetcher of records you can already get at no cost. You are paying for the citation, the check and the receipt, not for the register's own data.
Issues
Corrections about a claim we make are welcome as issues here. If we have said something about a company, a number or a register that is wrong, that is the fastest way to tell us.