MCP servers › io.github.BrianTian818 › cvin

MCP server · registry snapshot 2026-11-04 · last tested 2026-11-04

cvin MCP server

Registry name io.github.BrianTian818/cvin

by BrianTian818 · GitHub account (the registry's namespace rule)

GPU compute-asset identity registry: resolve device identity, verify history, buy official reports. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-11-04version 0.1.0streamable HTTP15 tools

Summary

io.github.BrianTian818/cvin is a remote MCP server listed in the official MCP registry at version 0.1.0, under the namespace of the GitHub account BrianTian818. On 2026-11-04 ProtocolProbe connected to it in read-only mode and read its inventory: 15 tools, 0 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

met: Registry entry is active and says how to run it
not met: Source repository link opens
not applicable: Repository is not archived
not applicable: Code pushed to the repository in the 90 days before our check
not applicable: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Your own values: none declared (not a guarantee)
Sign-in: none needed to open a session
Tools: 15
Last tested: 2026-11-04

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-04 (cvin.org), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (0.1.0).

Add to your client

How fresh this is

Live-tested: yes, a real session (not a text-only review)
Last tested: 2026-11-04
Mode: read-only (no tool calls)
Latest version: 0.1.0, published 2026-11-03 (registry, as of the 2026-11-04 snapshot)
First listed version: 2026-11-03 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-11-04
Package and repository: checked 2026-11-04
Engine: mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-03, listed on 2026-11-04 with version 0.1.0 (published 2026-11-03).

Source: the official MCP Registry list on 2026-11-03 and on 2026-11-04.

What it is

What does this server offer?

Observed inventory

15tools

0resources

0prompts

None of its 15 tools are described as changing anything. For 15 the reading was uncertain, so no mark is shown.

cvin_resolve
“解析一个 CVIN：确认该算力资产是否存在于登记表，返回首次/最近观测时间、观测次数、观测类型与最近一次价格观测。永久免费、无限次。”
1 input, 1 required
- cvinstringrequired“形如 cvin:nv.h100.sxm.80g:6a1kfvdo43buqm34”
cvin_history
“返回该 CVIN 的完整观测历史（含哈希链），用于重复抵押与违约史核查。按次计费 $0.05（x402）。”
2 inputs, 1 required
- cvinstringrequired“待查询的 CVIN”
- limitnumber“最多返回多少条观测，默认 100”
cvin_verify
“连续性证明：重放该 CVIN 的哈希链并返回 ed25519 签名，任何人可独立复算校验。按次计费 $0.05（x402）。”
1 input, 1 required
- cvinstringrequired
cvin_report
“签发单台设备的正式核验报告（报告编号 + ed25519 签名 + 固定内容哈希，可留档可独立验签），供放款 / 承保 / 承租决策留档。按份计费 $2.00（x402）。”
1 input, 1 required
- cvinstringrequired
cvin_buy_key
“自助购买风控订阅 API 密钥（30 天有效期）：history / verify / watch / 报告端点全部直通，不再按次付费。$10.00（x402）。适合需要批量或高频核验的 Agent。”
1 input
- orgstring“可选：组织名，会登记在密钥元数据里（≤60 字符）”
cvin_encode
“由厂商/型号/形态/显存/序列号计算 CVIN（序列号不出本机：仅上传哈希后的结果参与登记）。免费。”
5 inputs, 5 required
- mfrstringrequired
- modelstringrequired
- formstringrequired
- memstringrequired
- serialstringrequired“设备序列号，仅用于本地计算哈希，不会被存储”
cvin_identity
“查询某 CVIN 的身份级别（L0 挂牌指纹 / L1 序列号可观测 / L2 硬件信任根）、该级别能断言与不能断言什么、以及升到下一级的做法。免费。”
1 input, 1 required
- cvinstringrequired
cvin_permits
“判断某个身份级别能否用于某个用途（如「抵押登记」「保险核保」「资产池入池」）。返回 {allowed, level, upgrade_to}。免费——这一层让「L0 不能抵押」由机器把关而不是靠人记得。”
2 inputs, 2 required
- cvinstringrequired
- usestringrequired“用途，如：抵押登记 / 保险核保 / 资产池入池 / 市场行情 / 在押持续验证”
cvin_events
“拉取结构化事件流：失联、休眠、重复抵押、价格暴跌、跨地区流转等。支持 since 增量拉取。永久免费——事件流是地基层。”
4 inputs
- sincestring“ISO 8601，只返回该时刻之后的事件”
- typesstring“逗号分隔的事件类型”
- severity_minstring“info / notice / warn / critical”
- limitnumber
cvin_market_price
“查询某 GPU 型号的租赁行情：按平台返回最新报价（价格/地区/库存/观测时间）。输入 "nv.h100" 或裸型号 "h100"/"rtx4090"（自动匹配厂商前缀）。免费。型号级行情是供给报价，不指向具体设备；要核验某台具体设备请用 cvin_resolve / cvin_history。”
1 input, 1 required
- modelstringrequired“mfr.model（如 nv.h100 / amd.mi300x / his.ascend910b2）或裸型号（h100、rtx4090、a100…）”
cvin_clauses
“取合同条款模板（采购订单 / 租赁 / 抵押担保 / 保险 / RWA 入池 / 尽调），中英双语，可直接粘贴进合同。永久免费，复制与引用无需署名。”
2 inputs
- kindstring“po / lease / lien / insurance / rwa / audit；不填返回全部”
- idstring“条款编号，如 lien-01”
cvin_risk_signals
“风险信号聚合：身份级别分布、活跃度分布、在押与重复抵押计数、事件计数。事件数未达 200 阈值前只输出计数，不输出比率（先计数后比率）。免费。”
Takes no inputs.

Show 3 more tools

cvin_provenance
“数据出处与合成数据占比：真实/合成各多少、设备级与型号级分开算、来自哪些源、离「合成占比 ≤10%」还差多少条真实观测。引用登记表统计前应先查这一项。免费。”
Takes no inputs.
cvin_governance
“治理结构：规范委员会三层分权、7 席构成（现全部空缺）、表决门槛、发起方交权清单、RFC 提案与公示期。redlines=true 时附带六条红线的可复算判定。免费。”
1 input
- redlinesboolean“是否附带红线自检结果”
cvin_schedule
“抵押物清单生成：给定一组 CVIN，逐台给出能否设押的结论（身份级是否够、是否已在押、是否重复抵押、履历是否为合成数据），输出可直接作为质押合同附件的清单。免费。”
4 inputs, 1 required
- devicesarrayrequired“[{cvin, note}] 列表，最多 500 项；也可传换行分隔的字符串”
- referencestring“合同 / PO 编号”
- counterpartystring“交易对手”
- purposestring“用途，默认「算力资产质押」”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-04.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description: 65% of 26
Tools with a description: 100% of 15
Typical description length: 79 characters

The tool set

Counted from the listing

Tools: 15
Size of the list: about 1,040 tokens for an agent to load (characters ÷ 4)
Naming: 15 of 15 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 15 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-04 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://cvin.org/mcp

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

{
  "mcpServers": {
    "cvin": {
      "url": "https://cvin.org/mcp"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "cvin": {
      "type": "http",
      "url": "https://cvin.org/mcp"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"cvin","type":"http","url":"https://cvin.org/mcp"}'

Claude Code

claude mcp add --transport http cvin https://cvin.org/mcp

Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)

{
  "mcpServers": {
    "cvin": {
      "type": "streamableHttp",
      "url": "https://cvin.org/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}

Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project

{
  "mcpServers": {
    "cvin": {
      "httpUrl": "https://cvin.org/mcp"
    }
  }
}

OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project

[mcp_servers.cvin]
url = "https://cvin.org/mcp"

Zed · Zed settings file (command: zed: open settings file)

{
  "context_servers": {
    "cvin": {
      "url": "https://cvin.org/mcp"
    }
  }
}

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://cvin.org/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint cvin.org/mcp	Session opened	matches	our test · 2026-11-04
No credential declared as required	Opened a session without any credential	matches	our test · 2026-11-04

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
Does not applyRepository is not archivedNo public GitHub repository to read.
Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-04. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.github.BrianTian818/cvin

Answered from the data above

Who publishes io.github.BrianTian818/cvin?

The registry ties the namespace io.github.BrianTian818 to the GitHub account BrianTian818; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does io.github.BrianTian818/cvin need an API key or sign-in?

It opened a session without any credential on 2026-11-04. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.github.BrianTian818/cvin been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-04

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 2

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised

Not run, with the reason · 12

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 4

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-11-04, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
2,456 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 15 tools, 0 resources, 0 prompts.
7,814 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

pending: added in a later update

listed 2026-11-04; not classified yet

Pricing modelAI-classified

not checked

no website in the registry entry

Programming language

does not apply

no existing GitHub repository (server declares no repository link, so there is nothing to fetch)

Hosting type

remote (hosted by the publisher)

registry · 2026-11-04

MCP capability

tools

our test · 2026-11-04

Transport

streamable HTTP

registry · 2026-11-04

Required credentials

none declared

registry · 2026-11-04 · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-11-04

Lifecycle status

active

registry · 2026-11-04

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

not stated

no readable GitHub owner to describe

Maintenance

does not apply

server declares no repository link, so there is nothing to fetch

Environment

the publisher's infrastructure

where it runs, from the hosting type · 2026-11-04

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.BrianTian818/cvin: MCP server record.” Data checked 2026-11-04. https://protocolprobe.com/mcp/servers/io.github.BrianTian818/cvin

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.BrianTian818/cvin)](https://protocolprobe.com/mcp/servers/io.github.BrianTian818/cvin)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology