Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

CVIN

REMOTE · CVIN.ORG

GPU compute-asset identity registry: resolve device identity, verify history, buy official reports.

Available components

63 Trust /100

Last scanned (3 hours ago)

Scores higher than 44% of remote servers

Reachable. Last reached 5 Nov 2026.

Category IoT and Hardware

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1426 tokens (~95/item across 15 items; 15 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 65% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Nov 26 0
    • Schema quality: 1285 → 1426 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • New tool “cvin_market_price” functional
  • 3 Nov 26 62

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://cvin.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=cvin.org CN=YE1,O=Let's Encrypt,C=US 1 Nov 2026 30 Jan 2027 ECDSA 256 ECDSA-SHA384 5200bc46427274274de193ed88cc769e98d
SANs: cvin.org
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of cvin.org. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
org. present 725, 26974 8, 8 Verified
cvin.org. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=15552000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self'; connect-src 'self'; base-uri 'self'; form-action 'self'; frame-ancestors 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://cvin.org/mcp Verified 200
http (plaintext) http://cvin.org/mcp HTTPS enforced 308 https://cvin.org/mcp
MCP tools · 15 exposed · ~1,426 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
cvin_buy_key ~93

自助购买风控订阅 API 密钥(30 天有效期):history / verify / watch / 报告端点全部直通,不再按次付费。$10.00(x402)。适合需要批量或高频核验的 Agent。

NameTypeReqDescription
orgstring–可选:组织名,会登记在密钥元数据里(≤60 字符)

No output schema declared.

No examples provided.

cvin_clauses ~101

取合同条款模板(采购订单 / 租赁 / 抵押担保 / 保险 / RWA 入池 / 尽调),中英双语,可直接粘贴进合同。永久免费,复制与引用无需署名。

NameTypeReqDescription
idstring–条款编号,如 lien-01
kindstring–po / lease / lien / insurance / rwa / audit;不填返回全部

No output schema declared.

No examples provided.

cvin_encode ~101

由厂商/型号/形态/显存/序列号计算 CVIN(序列号不出本机:仅上传哈希后的结果参与登记)。免费。

NameTypeReqDescription
formstringyes–
memstringyes–
mfrstringyes–
modelstringyes–
serialstringyes设备序列号,仅用于本地计算哈希,不会被存储

No output schema declared.

No examples provided.

cvin_events ~109

拉取结构化事件流:失联、休眠、重复抵押、价格暴跌、跨地区流转等。支持 since 增量拉取。永久免费——事件流是地基层。

NameTypeReqDescription
limitnumber––
severity_minstring–info / notice / warn / critical
sincestring–ISO 8601,只返回该时刻之后的事件
typesstring–逗号分隔的事件类型

No output schema declared.

No examples provided.

cvin_governance ~91

治理结构:规范委员会三层分权、7 席构成(现全部空缺)、表决门槛、发起方交权清单、RFC 提案与公示期。redlines=true 时附带六条红线的可复算判定。免费。

NameTypeReqDescription
redlinesboolean–是否附带红线自检结果

No output schema declared.

No examples provided.

cvin_history ~79

返回该 CVIN 的完整观测历史(含哈希链),用于重复抵押与违约史核查。按次计费 $0.05(x402)。

NameTypeReqDescription
cvinstringyes待查询的 CVIN
limitnumber–最多返回多少条观测,默认 100

No output schema declared.

No examples provided.

cvin_identity ~77

查询某 CVIN 的身份级别(L0 挂牌指纹 / L1 序列号可观测 / L2 硬件信任根)、该级别能断言与不能断言什么、以及升到下一级的做法。免费。

NameTypeReqDescription
cvinstringyes–

No output schema declared.

No examples provided.

cvin_market_price ~141

查询某 GPU 型号的租赁行情:按平台返回最新报价(价格/地区/库存/观测时间)。输入 "nv.h100" 或裸型号 "h100"/"rtx4090"(自动匹配厂商前缀)。免费。型号级行情是供给报价,不指向具体设备;要核验某台具体设备请用 cvin_resolve / cvin_history。

NameTypeReqDescription
modelstringyesmfr.model(如 nv.h100 / amd.mi300x / his.ascend910b2)或裸型号(h100、rtx4090、a100…)

No output schema declared.

No examples provided.

cvin_permits ~115

判断某个身份级别能否用于某个用途(如「抵押登记」「保险核保」「资产池入池」)。返回 {allowed, level, upgrade_to}。免费——这一层让「L0 不能抵押」由机器把关而不是靠人记得。

NameTypeReqDescription
cvinstringyes–
usestringyes用途,如:抵押登记 / 保险核保 / 资产池入池 / 市场行情 / 在押持续验证

No output schema declared.

No examples provided.

cvin_provenance ~71

数据出处与合成数据占比:真实/合成各多少、设备级与型号级分开算、来自哪些源、离「合成占比 ≤10%」还差多少条真实观测。引用登记表统计前应先查这一项。免费。

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

cvin_report ~81

签发单台设备的正式核验报告(报告编号 + ed25519 签名 + 固定内容哈希,可留档可独立验签),供放款 / 承保 / 承租决策留档。按份计费 $2.00(x402)。

NameTypeReqDescription
cvinstringyes–

No output schema declared.

No examples provided.

cvin_resolve ~87

解析一个 CVIN:确认该算力资产是否存在于登记表,返回首次/最近观测时间、观测次数、观测类型与最近一次价格观测。永久免费、无限次。

NameTypeReqDescription
cvinstringyes形如 cvin:nv.h100.sxm.80g:6a1kfvdo43buqm34

No output schema declared.

No examples provided.

cvin_risk_signals ~72

风险信号聚合:身份级别分布、活跃度分布、在押与重复抵押计数、事件计数。事件数未达 200 阈值前只输出计数,不输出比率(先计数后比率)。免费。

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

cvin_schedule ~146

抵押物清单生成:给定一组 CVIN,逐台给出能否设押的结论(身份级是否够、是否已在押、是否重复抵押、履历是否为合成数据),输出可直接作为质押合同附件的清单。免费。

NameTypeReqDescription
counterpartystring–交易对手
devicesarrayyes[{cvin, note}] 列表,最多 500 项;也可传换行分隔的字符串
purposestring–用途,默认「算力资产质押」
referencestring–合同 / PO 编号

No output schema declared.

No examples provided.

cvin_verify ~62

连续性证明:重放该 CVIN 的哈希链并返回 ed25519 签名,任何人可独立复算校验。按次计费 $0.05(x402)。

NameTypeReqDescription
cvinstringyes–

No output schema declared.

No examples provided.

Install

How do I install the CVIN MCP server?

CVIN is a hosted endpoint at https://cvin.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · cvin.org

# add to Claude Code
claude mcp add --transport http briantian818-cvin 'https://cvin.org/mcp'
Common questions

What is the CVIN MCP server?

CVIN is an MCP server listed in the public MCP registry as io.github.BrianTian818/cvin. GPU compute-asset identity registry: resolve device identity, verify history, buy official reports. This page covers its hosted endpoint (https://cvin.org/mcp).

Is the CVIN MCP server safe to use?

CVIN scores 63 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the CVIN MCP server expose?

CVIN exposes 15 tools: cvin_resolve, cvin_history, cvin_verify, cvin_report, cvin_buy_key, and 10 more. Their descriptions and schemas cost roughly 1,426 tokens of context every time the server is loaded.

Does the CVIN MCP server require authentication?

No. We connected to CVIN without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the CVIN MCP server still maintained?

CVIN is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.