io.github.yellow-hammer/mcp-1c-platform-tools

Name: io.github.yellow-hammer/mcp-1c-platform-tools
Author: io.github.yellow-hammer

MCPcommunity

v0.1.5io.github.yellow-hammerUnknownUpdated 5mo agonpm GitHub

MCP для команд 1c-platform-tools. Нужно расширение 1c-platform-tools с включённым IPC.

MCP-сервер предоставляет инструменты Model Context Protocol для запуска команд расширения 1c-platform-tools через агентов Cursor/VS Code. 1. Установите расширение 1c-platform-tools и расширение 1C: Platform Tools MCP. 2. Включите IPC: настройка = . 3. Откройте проект 1С (папка с ). В VS Code дополнительная настройка не нужна: расширение само регистрирует MCP. Достаточно установить оба расширения…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

5mo agoLast update

Package

Authorio.github.yellow-hammer

LicenseUnknown

Version0.1.5

Sourcemcp-registry

npmmcp-1c-platform-tools

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

Trust Status

10/100Untrusted

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

—CVE scan · not run+0/30

→ Our scan didn't complete — a retry is queued. Nothing to fix on your side.

—Static analysis · clean+0/20

→ Our scan didn't complete — a retry is queued. Nothing to fix on your side.

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

DependenciesNot audited

Tool surface—

Security scanScan failedvunknown · 2d ago

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Keywords

mcp