io.github.NickLiapin/tdcv2
NPM · TDCV2-MCP · SCANNED OCT 3
Deterministic test data from a .tdc config, generated locally by the TDCv2 engine.
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 33 of 119 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to NickLiapin/tdcv2-agents). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability59
- 25% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 956 tokens (~106/item across 9 items; 6 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.NickLiapin/tdcv2 MCP server?
io.github.NickLiapin/tdcv2 runs locally as an npm package, launched with npx -y tdcv2-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · tdcv2-mcp
claude mcp add nickliapin-tdcv2 -- npx -y tdcv2-mcp
{
"mcpServers": {
"nickliapin-tdcv2": {
"command": "npx",
"args": [
"-y",
"tdcv2-mcp"
]
}
}
} {
"servers": {
"nickliapin-tdcv2": {
"command": "npx",
"args": [
"-y",
"tdcv2-mcp"
]
}
}
} codex mcp add nickliapin-tdcv2 -- npx -y tdcv2-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nickliapin-tdcv2": {
"type": "local",
"command": [
"npx",
"-y",
"tdcv2-mcp"
],
"enabled": true
}
}
} openclaw mcp add nickliapin-tdcv2 --command npx --arg -y --arg tdcv2-mcp
mcp_servers:
nickliapin-tdcv2:
command: "npx"
args: ["-y", "tdcv2-mcp"] {
"McpServers": {
"nickliapin-tdcv2": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"tdcv2-mcp"
]
}
}
} assistant mcp add nickliapin-tdcv2 -t stdio -c npx -a -y tdcv2-mcp
{
"mcpServers": {
"nickliapin-tdcv2": {
"command": "npx",
"args": [
"-y",
"tdcv2-mcp"
]
}
}
} 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.
- 2 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 1 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.07 ▲ functional
- Package version: 0.1.1 → 0.1.2 functional
- 30 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Sept 26 62
First indexed and scored.
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 3 Oct 2026 · Analysed npm/tdcv2-mcp@0.1.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | NickLiapin/tdcv2-agents |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/NickLiapin/tdcv2-agents/.github/workflows/release.yml@refs/tags/v0.1.2 |
| Rekor log index | 3028976469 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:ff0c04b668087682b5a4240b2c2b94eaeaa0fdfde8d450fdae010c7cab6c31cfbafcc8880744a03f8f39fc2dc139f1da6452d80b29f0fabf8c7362d70 |
Background: How many MCP packages publish verified provenance →
Dependencies 119 packages
| Packages resolved | 119 |
|---|---|
| Stale | 33 |
| 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 →
tdc_check Check a TDCv2 config ~99
Validate a .tdc config without generating anything. Returns every diagnostic with its code, line, column, hint and "did you mean" suggestion, plus warnings and whether a seed is set. Run it until the config is clean.
| Name | Type | Req | Description |
|---|---|---|---|
| config | string | – | The .tdc config text. Give this or `path`. |
| path | string | – | A .tdc file, relative to the project folder. Give this or `config`. |
No output schema declared.
No examples provided.
tdc_find_packs Find TDCv2 data packs ~141
Search the data packs installed on this machine by words ("last name", "iban", "city") — the paths to write in <gen type="template" value="…"/>. Never guess a path; ask this. Returns path, the locales that have it, and what it holds (never the values).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | At most this many results (default 15). |
| locale | string | – | Only packs for this locale, e.g. "fr". Says how to install it if missing. |
| query | string | yes | Words to look for, English works best: "last name", "email", "country". |
No output schema declared.
No examples provided.
tdc_format Format a TDCv2 config ~49
Pretty-print a .tdc config the way `tdcv2 format` does. Returns the text unchanged if it does not parse.
| Name | Type | Req | Description |
|---|---|---|---|
| config | string | yes | The .tdc config text. |
No output schema declared.
No examples provided.
tdc_generate Generate data from a TDCv2 config ~256
Make test data — CSV, JSON, SQL, any text — from a .tdc config, instead of writing a generator script. Without `output`: renders in memory and returns the first `preview` lines (max 50) — nothing is written. With `output`: writes the whole file inside the project folder and returns its size, a per-column summary and the first lines. A failed <assert> comes back as row, message, condition and values, so the config can be fixed. Same config and seed give the same bytes every time.
| Name | Type | Req | Description |
|---|---|---|---|
| config | string | – | The .tdc config text. Give this or `path`. |
| count | integer | – | Override <env count> for this run. For the delivered file keep count in the config instead. |
| output | string | – | File to write, relative to the project folder. Omit to preview only. |
| path | string | – | A .tdc file, relative to the project folder. Give this or `config`. |
| preview | integer | – | Lines to return (default 10, max 50). |
| seed | string | – | Override <env seed> for this run. For the delivered file keep seed in the config instead. |
No output schema declared.
No examples provided.
tdc_peek Summarise a generated file ~109
A short summary of a CSV, JSON or SQL file in the project: row count; per column the distinct values, the split, the range; INSERT rows per table. The proof that a file holds what was asked, without reading it all.
| Name | Type | Req | Description |
|---|---|---|---|
| column | string | – | One column in full (up to 50 values with counts). |
| path | string | yes | The file, relative to the project folder. |
| rows | integer | – | Sample rows to include (default 3). |
No output schema declared.
No examples provided.
tdc_read_docs Read the TDCv2 guide and reference ~149
Start here when asked for test data, fixtures or seed data: the TDCv2 guide ("guide" — read it before the first config), traps check does not catch ("traps"), using the data from test code in five languages ("from-code"), the list of reference pages ("index"), or one reference page such as "generators/date". `query` searches the page list.
| Name | Type | Req | Description |
|---|---|---|---|
| offset | integer | – | For long pages: continue from this character. |
| page | string | – | guide | traps | from-code | index | a reference path like generators/date. Default: guide. |
| query | string | – | Words to find in the page list instead of opening a page. |
No output schema declared.
No examples provided.
What is the io.github.NickLiapin/tdcv2 MCP server?
io.github.NickLiapin/tdcv2 is an MCP server listed in the public MCP registry as io.github.NickLiapin/tdcv2. Deterministic test data from a .tdc config, generated locally by the TDCv2 engine. This page covers its npm package (tdcv2-mcp).
Is the io.github.NickLiapin/tdcv2 MCP server safe to use?
io.github.NickLiapin/tdcv2 scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 3 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 io.github.NickLiapin/tdcv2 MCP server expose?
io.github.NickLiapin/tdcv2 exposes 6 tools: tdc_check, tdc_generate, tdc_find_packs, tdc_peek, tdc_read_docs, tdc_format. Their descriptions and schemas cost roughly 803 tokens of context every time the server is loaded.
Is the io.github.NickLiapin/tdcv2 MCP server still maintained?
io.github.NickLiapin/tdcv2 is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.NickLiapin/tdcv2 MCP server under?
io.github.NickLiapin/tdcv2 declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.