io.github.theYahia/1c-rest-mcp

MCPcommunity
v1.2.1io.github.theYahiaUnknownUpdated 5mo agonpmGitHub

MCP server for 1C Enterprise — ERP catalogs, documents via REST API (Russia)

MCP server for 1C:Enterprise REST API via OData 3.0 — catalogs, documents, registers, reports. 9 tools. HTTP Basic auth. Stdio + Streamable HTTP transports. If you starred or used v1.x, the v2.0.0 release introduces a few breaking changes: HTTP transport env var renamed: → . Removed separate HTTP binary: is gone. Use or instead. Single entrypoint: is no longer published. Internal client: now…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
11GitHub stars
5Forks
5mo agoLast update
Package
Authorio.github.theYahia
LicenseUnknown
Version1.2.1
Sourcemcp-registry
npm@theyahia/1c-rest-mcp
GitHubtheYahia/1c-rest-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓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 · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface9 tools · none privileged
Security scan✓ Cleanv3.0.0 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

9 tools · none privileged
Statically extracted from the published packagev3.0.0 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

list_entitiesNo description published

This tool published no description. Forge does not invent one.

get_document_by_numberNo description published

This tool published no description. Forge does not invent one.

get_catalogsNo description published

This tool published no description. Forge does not invent one.

get_documentsNo description published

This tool published no description. Forge does not invent one.

create_documentNo description published

This tool published no description. Forge does not invent one.

update_documentNo description published

This tool published no description. Forge does not invent one.

get_registerNo description published

This tool published no description. Forge does not invent one.

get_reportNo description published

This tool published no description. Forge does not invent one.

odata_queryNo description published

This tool published no description. Forge does not invent one.

0 of 9 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for 1C:Enterprise REST API via OData 3.0 — catalogs, documents, registers, reports. 9 tools. HTTP Basic auth. Stdio + Streamable HTTP transports. If you starred or used v1.x, the v2.0.0 release introduces a few breaking changes: HTTP transport env var renamed: → . Removed separate HTTP binary: is gone. Use or instead. Single entrypoint: is no longer published. Internal client: now extends 's with . The exported functional API () is unchanged, so tool code keeps working. Tool errors:…

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

9 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.