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.

EasyTdd

NUGET · EASYTDD.MCP

Generate C# builders, FluentMocks, tests and test cases from your .NET solution.

Available components

65 Trust /100

Last scanned (19 hours ago)

Scores higher than 43% of NuGet servers

Category Testing and QA

Trust breakdown (7 categories)

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 Security100
  • 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
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency19
  • Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
  • Build provenance not yet verified. View diagnostics → Unverified
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1452 tokens (~90/item across 16 items; 16 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "update_settings" implies "merge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 16 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 21 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 20 Oct 26 50

    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 23 Oct 2026 · Analysed nuget/EasyTdd.Mcp@6.0.2

Provenance Inconclusive

We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.

Result Inconclusive
Ecosystem nuget
Reason Signature present, unverified

Signer

Signed as Repository signature, names nuget.org
Subject CN=NuGet.org Repository by Microsoft,O=NuGet.org Repository by Microsoft,L=Redmond,ST=Washington,C=US
Issuer CN=DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1,O=DigiCert\, Inc.,C=US
Valid from 23 Feb 2024
Valid until 18 May 2027
Service index https://api.nuget.org/v3/index.json
Owners EasyTdd

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

Registry declarations For information only

What the registry and the package's own manifest say about this version. The publisher or the registry writes these, nothing here is verified, and none of it affects the score.

Repository https://bitbucket.org/kazys/easytdd
Repository type git
Commit 040da7e83d7668f597b175b8470fb8eade706d6b
Project URL https://easytdd.dev/
MCP tools · 16 exposed · ~1,452 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
check_generator_packages ~47

Check existing EasyTdd.Generators references in the loaded solution without changing files. Return proposed upgrades to the tested version. Ask the user to approve specific projects before calling update_generator_packages.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

customize_template ~76

Copy a default template to CustomTemplates and update settings to use the custom copy. Pass a path from templates_used in a generation tool response. After this call, edit the returned file path directly to customize the template.

NameTypeReqDescription
templateFilePathstringyesRelative template path from templates_used (e.g. defaulttemplates\builder.g.tpl)

No output schema declared.

No examples provided.

generate_builder ~123

Generate an incremental builder for a type. The builder is attribute-driven and auto-updates when the target class changes. This is the preferred builder approach.

NameTypeReqDescription
contextFilePathstring|null–Path to a file that uses or declares the type; required when typeName is a simple name
regenerateboolean–Retained for compatibility. Incremental marker files are never overwritten; delete the marker to recreate it.
typeNamestringyesFully qualified type name (e.g. MyApp.MyClass) or simple name when contextFilePath is provided

No output schema declared.

No examples provided.

generate_builder_plain ~125

Generate a template-based builder for a type. The builder is generated once and reflects the type's state at the time of generation. Use generate_builder for the auto-updating version.

NameTypeReqDescription
contextFilePathstring|null–Path to a file that uses or declares the type; required when typeName is a simple name
regenerateboolean–Overwrite existing files that have Recreate=true in settings. Default false.
typeNamestringyesFully qualified type name (e.g. MyApp.MyClass) or simple name when contextFilePath is provided

No output schema declared.

No examples provided.

generate_fluent_mock ~135

Generate an incremental FluentMock for an interface or abstract class. The mock wraps Moq with fluent Setup/Verify methods and auto-updates when the target type changes. This is the preferred approach.

NameTypeReqDescription
contextFilePathstring|null–Path to a file that uses or declares the type; required when typeName is a simple name
regenerateboolean–Retained for compatibility. Incremental marker files are never overwritten; delete the marker to recreate it.
typeNamestringyesFully qualified type name (e.g. MyApp.IUserService) or simple name when contextFilePath is provided

No output schema declared.

No examples provided.

generate_fluent_mock_plain ~130

Generate a template-based FluentMock for an interface or abstract class. Generated once, reflects the type's state at time of generation. Use generate_fluent_mock for the auto-updating version.

NameTypeReqDescription
contextFilePathstring|null–Path to a file that uses or declares the type; required when typeName is a simple name
regenerateboolean–Overwrite existing files that have Recreate=true in settings. Default false.
typeNamestringyesFully qualified type name (e.g. MyApp.IUserService) or simple name when contextFilePath is provided

No output schema declared.

No examples provided.

generate_test ~118

Generate a test class for a type. Creates test doubles (builders/mocks) for dependencies, a subject under test, and test method stubs.

NameTypeReqDescription
contextFilePathstring|null–Path to a file that uses or declares the type; required when typeName is a simple name
regenerateboolean–Overwrite existing files that have Recreate=true in settings. Default false.
typeNamestringyesFully qualified type name (e.g. MyApp.MyService) or simple name when contextFilePath is provided

No output schema declared.

No examples provided.

generate_test_cases ~120

Generate inline test cases for a parameterized test method. Adds a test case attribute to the method and inserts a source method below it in the same file.

NameTypeReqDescription
contextFilePathstring|null–Path to the test file; required when typeName is a simple name
methodNamestringyesMethod name. For overloads, append param types: Process(int,string)
typeNamestringyesFully qualified name of the containing type (e.g. MyApp.Tests.MyTests) or simple name when contextFilePath is provided

No output schema declared.

No examples provided.

generate_test_cases_external ~147

Generate test cases for a parameterized test method in an external class file. Adds a test case attribute to the method, adds a using, and creates a new source class file.

NameTypeReqDescription
contextFilePathstring|null–Path to the test file; required when typeName is a simple name
methodNamestringyesMethod name. For overloads, append param types: Process(int,string)
regenerateboolean–Overwrite existing files that have Recreate=true in settings. Default false.
typeNamestringyesFully qualified name of the containing type (e.g. MyApp.Tests.MyTests) or simple name when contextFilePath is provided

No output schema declared.

No examples provided.

get_model ~89

Return the model schema (field names and types) available in Scriban templates for a given generation tool. Use this to verify that a custom template uses only valid field names before or after an upgrade.

NameTypeReqDescription
toolNamestringyesMCP tool name: generate_builder, generate_builder_plain, generate_fluent_mock, generate_fluent_mock_plain, generate_test, generate_test_cases, generate_test_cases_external

No output schema declared.

No examples provided.

get_settings ~32

Return the current EasyTdd settings with field descriptions. Use this to show the user what is configured before making changes.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

initialize ~66

Initialize EasyTdd for this solution. Creates the .easyTdd folder, writes default settings.json, and deploys default templates. Must be called once before any generation tool. Review the returned settings with the user before generating — key decisions: test framework, project naming conventions, tooling namespaces.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

load_solution ~37

Load or reload a solution. Returns the list of project names.

NameTypeReqDescription
solutionPathstringyesAbsolute path to the .sln file

No output schema declared.

No examples provided.

update_generator_packages ~94

Update only approved project references to the tested EasyTdd.Generators version. Call check_generator_packages and obtain explicit user approval first. Recheck versions; never downgrade or overwrite shared/central versions.

NameTypeReqDescription
confirmedboolean–Set true only after explicit user approval of these upgrades; false makes no changes.
projectFilePathsarrayyesAbsolute project paths returned by check_generator_packages and explicitly approved by the user.

No output schema declared.

No examples provided.

update_settings ~66

Merge a partial settings JSON into the current EasyTdd settings. Only provide the fields you want to change. Example: {"Test": {"DefaultTestFramework": "xUnit"}}

NameTypeReqDescription
partialJsonstringyesPartial settings JSON to merge. Only provide fields you want to change.

No output schema declared.

No examples provided.

upgrade ~47

Upgrade EasyTdd settings and templates to the current installed version. Ask the user for confirmation before calling this tool. Returns a changelog of what changed and lists any custom templates that may need review.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the EasyTdd MCP server?

EasyTdd runs locally as a NuGet package, launched with dnx EasyTdd.Mcp@6.0.2 --yes. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

nuget · EasyTdd.Mcp

# add to Claude Code
claude mcp add dev-easytdd-easytdd -- dnx EasyTdd.Mcp@6.0.2 --yes
Common questions

What is the EasyTdd MCP server?

EasyTdd is an MCP server listed in the public MCP registry as dev.easytdd/easytdd. Generate C# builders, FluentMocks, tests and test cases from your .NET solution. This page covers its NuGet package (EasyTdd.Mcp).

Is the EasyTdd MCP server safe to use?

EasyTdd scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. It declares no install or post-install scripts. 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 EasyTdd MCP server expose?

EasyTdd exposes 16 tools: check_generator_packages, generate_fluent_mock_plain, load_solution, generate_test_cases, generate_fluent_mock, and 11 more. Their descriptions and schemas cost roughly 1,452 tokens of context every time the server is loaded.

Is the EasyTdd MCP server still maintained?

EasyTdd is still listed as active in the MCP registry. We last reached this channel on 23 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 EasyTdd MCP server under?

EasyTdd declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.