Complexity Analysis
NUGET · COMPLEXITYANALYSIS.MCP
Analyze C# complexity, inspect member evidence, and compare deterministic snapshots.
Available components
Last scanned (21 hours ago)
Scores higher than 95% of NuGet servers
Category Testing and QA
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 & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to rodri-oliveira-dev/complexity-analyzers). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 350 tokens (~116/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 Management33
- Stability observed for 10 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 1.0.0 → 1.0.1 functional
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 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.
- 25 Oct 26 82
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 4 Nov 2026 · Analysed nuget/ComplexityAnalysis.Mcp@1.0.1
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 | nuget |
| Reason | Verified |
| Discovered via | GitHub artifact attestations |
| Source repo | rodri-oliveira-dev/complexity-analyzers |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/rodri-oliveira-dev/complexity-analyzers/.github/workflows/release-mcp.yml@refs/heads/main |
| Rekor log index | 3581189573 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha256:4ed846c82b4a392cba8da4c993a3740ecdc6df02df13d55875a20da5f5268eb0 |
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 | rodri-oliveira-dev |
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://github.com/rodri-oliveira-dev/complexity-analyzers |
|---|---|
| Repository type | git |
| Branch | refs/heads/main |
| Commit | 24779a2f8b93a9c5195cf323349bb32fa30803c0 |
| Project URL | https://github.com/rodri-oliveira-dev/complexity-analyzers |
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 →
analyze_project ~153
Analyzes a C# project or solution below --root. Returns a deterministic snapshot with explicit Unknown results. Use responseMode='summary' to reduce context, then query_member_evidence with analysisId for exact member details.
| Name | Type | Req | Description |
|---|---|---|---|
| maxMembers | integer|null | – | Maximum member summaries (1-500) when responseMode is 'summary'; default 100. Supplying it in full mode is rejected. |
| path | string | yes | Relative or absolute path to a .csproj, .sln, or .slnx file below the configured --root. |
| responseMode | string | – | Response detail: 'full' preserves the complete report; 'summary' returns a bounded member index with explicit truncation metadata. |
Structured output declared, but exposes no named fields.
No examples provided.
compare_snapshots ~78
Compares baseline and current complexity-snapshot JSON files below --root. Unknown estimates remain incomparable and are never promoted to proven regressions.
| Name | Type | Req | Description |
|---|---|---|---|
| baselinePath | string | yes | Relative or absolute path to the baseline .json snapshot below --root. |
| currentPath | string | yes | Relative or absolute path to the current .json snapshot below --root. |
Structured output declared, but exposes no named fields.
No examples provided.
query_member_evidence ~119
Returns one member's estimate and evidence by exact StableId. Pass analyze_project's analysisId to reuse that immutable snapshot; omit it to analyze current files again.
| Name | Type | Req | Description |
|---|---|---|---|
| analysisId | string|null | – | Optional analysisId returned by analyze_project. Reuses only that exact in-memory snapshot and fails explicitly if unavailable. |
| path | string | yes | Relative or absolute path to a .csproj, .sln, or .slnx file below the configured --root. |
| stableId | string | yes | Exact StableId returned by analyze_project. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Complexity Analysis MCP server?
Complexity Analysis runs locally as a NuGet package, launched with dnx ComplexityAnalysis.Mcp@1.0.1 --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 · ComplexityAnalysis.Mcp
claude mcp add rodri-oliveira-dev-complexity-analysis -- dnx ComplexityAnalysis.Mcp@1.0.1 --yes
What is the Complexity Analysis MCP server?
Complexity Analysis is an MCP server listed in the public MCP registry as io.github.rodri-oliveira-dev/complexity-analysis. Analyze C# complexity, inspect member evidence, and compare deterministic snapshots. This page covers its NuGet package (ComplexityAnalysis.Mcp).
Is the Complexity Analysis MCP server safe to use?
Complexity Analysis scores 87 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 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 Complexity Analysis MCP server expose?
Complexity Analysis exposes 3 tools: analyze_project, query_member_evidence, compare_snapshots. Their descriptions and schemas cost roughly 350 tokens of context every time the server is loaded.
Is the Complexity Analysis MCP server still maintained?
Complexity Analysis is still listed as active in the MCP registry. We last reached this channel on 4 November 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 Complexity Analysis MCP server under?
Complexity Analysis declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.