updated 2026-09-26 06:32 UTC

SharpLens

pzalutski-pixel/sharplens-mcp

Roslyn-powered MCP server for AI-driven C# semantic analysis, refactoring, and code generation

MCP Servers C# Listed MIT

Is SharpLens safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.2 / 10
Provenance None
Signed commits 0%
Last push 41d ago
Compare SharpLens

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: SharpLens scores 49.6/100 (Grade D), ranked #948 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.2/10; recent commits are unsigned; last pushed 2026-08-16. Every point is earned from checkable signals — never paid placement. How scoring works →

How SharpLens compares in MCP Servers

  1. #544 Withings Health Data 49.6 ±0
  2. #545 CVE MCP Server 49.6 ±0
  3. #546 SharpLens 49.6 this agent
  4. #547 MCP Turso Cloud 49.6 ±0
  5. #548 MCP Document Reader 49.6 ±0

Bars show each HVTrust score; the tick marks SharpLens’s 49.6.

Where the 49.6 comes from

HVTrust dimensions vs the MCP Servers average

49.6 / 100 · 100.0% confidence

SharpLens MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.3 / 25
5.0 below avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
12.1 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
9.3 / 20
2.8 below avg 12.1
AdoptionLog-scaled stars · package downloads
6.1 / 20
1.1 below avg 7.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-25
Rank Moved
Rank dropped 15 spots (#933 → #948)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 181 spots (#1110 → #929)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.2/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 41 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for SharpLens View MCP Servers Report missing data
33.1
Activity sub-score · out of 100
#546
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed 41 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
35
Forks
8
Last Push
2026-08-16
41 days ago
Commits (4 wk)
0
Downloads (7d)
63
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
=
was #948

Analysis

Activity Inputs

33.1 / 100
StarsRepository reach
9.3 / 30
FreshnessLast push recency
19.3 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
4.4 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.2 / 10
OpenSSF Scorecard · scanned Sep 25, 2026
Signed Commits
0%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests -1
CII-Best-Practices 0
Code-Review 0
Contributors 0
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 10

Common questions about SharpLens

Public trust evidence for SharpLens is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does SharpLens publish package provenance?
No published build provenance is currently detected for SharpLens. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does SharpLens have an OpenSSF Scorecard?
SharpLens has an OpenSSF Scorecard score of 4.2/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is SharpLens actively maintained?
Slowing down. Last push was 41 days ago — keep an eye on whether activity resumes.
What license does SharpLens use?
SharpLens ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are SharpLens's commits signed?
0% of the last 100 commits to SharpLens are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
medium confidence
Implemented
SharpLens appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to SharpLens's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain SharpLens?

For maintainers

HVTrust scores SharpLens from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 24HVTrust 3Grade 3Listed 2Scorecard 1Delisted 1MCP 1
2026-09-25
Rank Moved
Rank dropped 15 spots (#933 → #948)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 181 spots (#1110 → #929)
2026-09-23
HVTrust Changed
HVTrust up 27.9pts (21.9 → 49.8)
2026-09-22
Newly Listed
First tracked at rank #1110
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-19
Grade Changed
Trust grade D → C
2026-09-18
Grade Changed
Trust grade C → D
2026-09-16
Rank Moved
Rank dropped 28 spots (#892 → #920)
2026-09-15
Rank Moved
Rank dropped 29 spots (#863 → #892)
2026-09-13
Rank Moved
Rank dropped 12 spots (#857 → #869)
2026-09-11
Rank Moved
Rank dropped 13 spots (#835 → #848)
2026-09-09
Rank Moved
Rank dropped 17 spots (#817 → #834)
2026-09-07
Rank Moved
Rank dropped 74 spots (#735 → #809)
2026-09-06
Rank Moved
Rank dropped 12 spots (#723 → #735)
2026-09-05
Rank Moved
Rank dropped 101 spots (#622 → #723)
2026-09-04
Rank Moved
Rank dropped 30 spots (#592 → #622)
2026-09-03
Grade Changed
Trust grade D → C
2026-09-03
Rank Moved
Rank rose 476 spots (#1068 → #592)
2026-09-03
HVTrust Changed
HVTrust up 19.5pts (35.7 → 55.2)
2026-09-02
Rank Moved
Rank dropped 44 spots (#1024 → #1068)
2026-09-01
Rank Moved
Rank dropped 43 spots (#981 → #1024)
2026-08-31
Rank Moved
Rank dropped 35 spots (#946 → #981)
2026-08-30
Rank Moved
Rank dropped 44 spots (#902 → #946)
2026-08-29
Rank Moved
Rank dropped 47 spots (#855 → #902)
2026-08-28
Rank Moved
Rank dropped 29 spots (#826 → #855)
2026-08-27
Rank Moved
Rank dropped 21 spots (#805 → #826)
2026-08-26
Scorecard Added
OSSF Scorecard: 4.2/10
2026-08-26
Rank Moved
Rank rose 247 spots (#1052 → #805)
2026-08-26
HVTrust Changed
HVTrust up 15.5pts (20.5 → 36.0)
2026-08-19
Rank Moved
Rank dropped 10 spots (#1040 → #1050)
2026-08-17
Rank Moved
Rank rose 12 spots (#1056 → #1044)
2026-08-16
Rank Moved
Rank dropped 14 spots (#1042 → #1056)
2026-08-10
Rank Moved
Rank dropped 59 spots (#982 → #1041)
2026-08-08
Newly Listed
First tracked at rank #975
GitHub → npm: sharplens-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 49.6 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/sharplens.svg)](https://hvtracker.net/agents/sharplens)
HTML:
<a href="https://hvtracker.net/agents/sharplens"><img src="https://hvtracker.net/badge/sharplens.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON