T1/T2 Protocol
PYPI · T1-T2-PROTOCOL · SCANNED SEP 20
Caller-side T1/T2 heterogeneous validation MCP server. Stdlib-only Python.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 95 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 326 tokens (~108/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the T1/T2 Protocol MCP server?
T1/T2 Protocol runs locally as a PyPI package, launched with uvx t1-t2-protocol. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · t1-t2-protocol
claude mcp add fauxetine-t1-t2-protocol -- uvx t1-t2-protocol
{
"mcpServers": {
"fauxetine-t1-t2-protocol": {
"command": "uvx",
"args": [
"t1-t2-protocol"
]
}
}
} {
"servers": {
"fauxetine-t1-t2-protocol": {
"command": "uvx",
"args": [
"t1-t2-protocol"
]
}
}
} codex mcp add fauxetine-t1-t2-protocol -- uvx t1-t2-protocol
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fauxetine-t1-t2-protocol": {
"type": "local",
"command": [
"uvx",
"t1-t2-protocol"
],
"enabled": true
}
}
} openclaw mcp add fauxetine-t1-t2-protocol --command uvx --arg t1-t2-protocol
mcp_servers:
fauxetine-t1-t2-protocol:
command: "uvx"
args: ["t1-t2-protocol"] {
"McpServers": {
"fauxetine-t1-t2-protocol": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"t1-t2-protocol"
]
}
}
} assistant mcp add fauxetine-t1-t2-protocol -t stdio -c uvx -a t1-t2-protocol
{
"mcpServers": {
"fauxetine-t1-t2-protocol": {
"command": "uvx",
"args": [
"t1-t2-protocol"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.77 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
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 20 Sept 2026 · Analysed pypi/t1-t2-protocol@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
checksum ~73
Deterministic structural pre-validation (semantic ECC Pre-T2 Checksum) Input: AI answer text Output: structural integrity assessment (pass/fail) + diagnostics Zero LLM dependency - pure regex/string ops. Run before T2 to filter corrupted output.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The AI answer text to validate |
No output schema declared.
No examples provided.
t1_protocol ~148
Translates ambiguous questions into T1 structured prompts. Output: L1 facts / L2 assumptions / L3 hypotheses / L4 unknowns / core question / output requirements. v2.5+: L3 evidence status, core link exemption.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Output language: 'en' (default) or 'zh' |
| question | string | yes | The original question to translate |
| weight_hint | string | – | Optional evaluation weight hint. English: fact-first, efficiency-first, cost-first, robustness-first, general-first. Chinese: 事实优先, 效率优先, 成本优先, 鲁棒性优先, 通用优先. |
No output schema declared.
No examples provided.
t2_protocol ~105
Confidence evaluation for AI answers. Output: qualitative confidence (high/medium-high/medium/medium-low/low) + adoption recommendations. Run checksum before T2 when format integrity matters.
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The AI answer to evaluate |
| locale | string | – | Output language: 'en' (default) or 'zh' |
| weight_hint | string | – | Optional evaluation weight hint (default: factual accuracy > efficiency). Same values as t1_protocol weight_hint. |
No output schema declared.
No examples provided.
What is the T1/T2 Protocol MCP server?
T1/T2 Protocol is an MCP server listed in the public MCP registry as io.github.Fauxetine/t1-t2-protocol. Caller-side T1/T2 heterogeneous validation MCP server. Stdlib-only Python. This page covers its PyPI package (t1-t2-protocol).
Is the T1/T2 Protocol MCP server safe to use?
T1/T2 Protocol scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 T1/T2 Protocol MCP server expose?
T1/T2 Protocol exposes 3 tools: t1_protocol, t2_protocol, checksum. Their descriptions and schemas cost roughly 326 tokens of context every time the server is loaded.
Is the T1/T2 Protocol MCP server still maintained?
T1/T2 Protocol is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.