Is MCP 1c Platform Tools safe to use?

MCP 1c Platform Tools has an HVTrust score of 54.0/100 (Grade C), ranked #817 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP 1c Platform Tools?

MCP 1c Platform Tools scores 54.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 37 GitHub stars and is categorized under MCP Servers.

MCP 1c Platform Tools

yellow-hammer/mcp-1c-platform-tools

MCP-сервер расширения 1C: Platform Tools для агентов Visual Studio Code (Cursor) по IPC.

MCP Servers TypeScript Listed MIT

Is MCP 1c Platform Tools safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 5.9 / 10

Provenance None

Signed commits 34%

Last push 2d ago

Compare MCP 1c Platform Tools

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP 1c Platform Tools scores 54.0/100 (Grade C), ranked #817 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.9/10; 34% of recent commits are signed; last pushed 2026-09-24. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP 1c Platform Tools compares in MCP Servers

#456 MCP Baepsae 54.2 +0.2
#457 MCP Fns Check 54.1 +0.1
#458 MCP 1c Platform Tools 54.0 this agent
#459 RU Marketplace MCP 54.0 ±0
#460 SeedanceMCP 54.0 ±0

Bars show each HVTrust score; the tick marks MCP 1c Platform Tools’s 54.0.

Where the 54.0 comes from

HVTrust dimensions vs the MCP Servers average

54.0 / 100 · 100.0% confidence

MCP 1c Platform Tools MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

9.1 / 25

1.2 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

13.5 / 17

1.3 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

17.8 / 20

5.7 above avg 12.1

AdoptionLog-scaled stars · package downloads

3.8 / 20

3.4 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

Grade Changed

Trust grade D → C

2026-09-25

Rank Moved

Rank rose 411 spots (#1230 → #819)

2026-09-25

HVTrust Changed

HVTrust up 18.3pts (35.7 → 54.0)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.9/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.

Compare with another agent Get email alerts for MCP 1c Platform Tools View MCP Servers Report missing data

57.0

Activity sub-score · out of 100

#458

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 C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-24

2 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲2

was #819

Analysis

Activity Inputs

57.0 / 100

StarsRepository reach

9.5 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

18.4 / 25

CommunityFork signal

4.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.9 / 10

OpenSSF Scorecard · scanned Sep 22, 2026

Signed Commits

34%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 8

CII-Best-Practices 0

Code-Review 0

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 3

SAST 10

Security-Policy 0

Signed-Releases 0

Token-Permissions 9

Vulnerabilities 10

Common questions about MCP 1c Platform Tools

Public trust evidence for MCP 1c Platform Tools 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 MCP 1c Platform Tools publish package provenance?

No published build provenance is currently detected for MCP 1c Platform Tools. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does MCP 1c Platform Tools have an OpenSSF Scorecard?

MCP 1c Platform Tools has an OpenSSF Scorecard score of 5.9/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 MCP 1c Platform Tools actively maintained?

Actively maintained. The repository was pushed to within the last 2 day(s).

What license does MCP 1c Platform Tools use?

MCP 1c Platform Tools ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MCP 1c Platform Tools's commits signed?

34% of the last 100 commits to MCP 1c Platform Tools 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

Declared

MCP support appears present, but direct server implementation is less certain.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

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

N/A

No package source configured

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 MCP 1c Platform Tools'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 → declared

Maintain MCP 1c Platform Tools?

For maintainers

HVTrust scores MCP 1c Platform Tools 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

2026-09-25

Grade Changed

Trust grade D → C

2026-09-25

Rank Moved

Rank rose 411 spots (#1230 → #819)

2026-09-25

HVTrust Changed

HVTrust up 18.3pts (35.7 → 54.0)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Rank Moved

Rank dropped 462 spots (#776 → #1238)

2026-09-23

HVTrust Changed

HVTrust up 5.9pts (29.3 → 35.2)

2026-09-22

Newly Listed

First tracked at rank #776

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-09

Rank Moved

Rank dropped 12 spots (#1224 → #1236)

2026-09-08

Rank Moved

Rank dropped 13 spots (#1211 → #1224)

2026-09-07

Rank Moved

Rank dropped 18 spots (#1193 → #1211)

2026-09-06

Rank Moved

Rank dropped 16 spots (#1177 → #1193)

2026-09-05

Scorecard Added

OSSF Scorecard: 5.8/10

2026-09-05

Rank Moved

Rank rose 135 spots (#1312 → #1177)

2026-09-05

HVTrust Changed

HVTrust up 19.3pts (15.8 → 35.1)

2026-08-29

Rank Moved

Rank dropped 13 spots (#1278 → #1291)

2026-08-28

Rank Moved

Rank dropped 16 spots (#1262 → #1278)

2026-08-26

Rank Moved

Rank dropped 23 spots (#1231 → #1254)

2026-08-17

Rank Moved

Rank rose 16 spots (#1239 → #1223)

2026-08-16

Rank Moved

Rank dropped 28 spots (#1211 → #1239)

2026-08-10

Rank Moved

Rank dropped 74 spots (#1136 → #1210)

2026-08-08

Newly Listed

First tracked at rank #1133

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/mcp-1c-platform-tools.svg)](https://hvtracker.net/agents/mcp-1c-platform-tools)
            
HTML:
            <a href="https://hvtracker.net/agents/mcp-1c-platform-tools"><img src="https://hvtracker.net/badge/mcp-1c-platform-tools.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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