1c Odata MCP Server

1c-odata-mcp npm v0.4.0 Source verified

Published by evilbruce666 — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

MCP server for 1C:Enterprise (1С) over OData. Ask your accounting database in natural language — debtors, sales, taxes, cash flow — from any MCP client (Claude, Cursor, VS Code, local models…). 55 tools, run with npx, nothing installed inside 1C; read-onl

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 97/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 56

Each tool and what it can reach — statically extracted from the published source.

  • write.sales.create_issued_invoicenetwork egress
  • read.analytics.get_cashflowno sensitive capability
  • read.analytics.get_deal_historyno sensitive capability
  • read.analytics.get_debtorsno sensitive capability
  • read.analytics.get_inventoryno sensitive capability
  • read.analytics.get_payments_breakdownno sensitive capability
  • read.analytics.get_purchases_breakdownno sensitive capability
  • read.analytics.get_salesno sensitive capability
  • read.analytics.get_sales_breakdownno sensitive capability
  • read.analytics.get_taxes_paidno sensitive capability
Show 46 more tools ↓
  • read.counterparty.find_counterpartyno sensitive capability
  • read.counterparty.get_counterpartyno sensitive capability
  • read.counterparty.get_customer_historyno sensitive capability
  • read.counterparty.get_supplier_historyno sensitive capability
  • read.document.get_documentno sensitive capability
  • read.document.search_documentsno sensitive capability
  • read.organization.get_organization_cardno sensitive capability
  • read.schema.describe_entityno sensitive capability
  • read.schema.list_entitiesno sensitive capability
  • read.system.health_checkno sensitive capability
  • read.system.list_databasesno sensitive capability
  • read.system.list_organizationsno sensitive capability
  • write.catalog.create_contractno sensitive capability
  • write.catalog.create_nomenclatureno sensitive capability
  • write.catalog.update_nomenclatureno sensitive capability
  • write.counterparty.create_bank_accountno sensitive capability
  • write.counterparty.create_contact_personno sensitive capability
  • write.counterparty.create_counterpartyno sensitive capability
  • write.counterparty.update_counterpartyno sensitive capability
  • write.document.add_document_lineno sensitive capability
  • write.document.copy_documentno sensitive capability
  • write.document.post_documentno sensitive capability
  • write.document.remove_document_lineno sensitive capability
  • write.document.update_document_linesno sensitive capability
  • write.entity.create_folderno sensitive capability
  • write.entity.mark_for_deletionno sensitive capability
  • write.entity.move_to_folderno sensitive capability
  • write.entity.update_entityno sensitive capability
  • write.money.create_bank_writeoffno sensitive capability
  • write.money.create_cash_paymentno sensitive capability
  • write.money.create_cash_receiptno sensitive capability
  • write.money.create_paymentno sensitive capability
  • write.money.create_payout_orderno sensitive capability
  • write.purchase.create_purchaseno sensitive capability
  • write.purchase.create_received_invoiceno sensitive capability
  • write.purchase.create_supplier_invoiceno sensitive capability
  • write.sales.create_actno sensitive capability
  • write.sales.create_invoiceno sensitive capability
  • write.sales.create_services_actno sensitive capability
  • write.sales.create_shipmentno sensitive capability
  • write.warehouse.create_inventoryno sensitive capability
  • write.warehouse.create_return_from_customerno sensitive capability
  • write.warehouse.create_return_to_supplierno sensitive capability
  • write.warehouse.create_surplusno sensitive capability
  • write.warehouse.create_transferno sensitive capability
  • write.warehouse.create_writeoffno sensitive capability

What this scan could not see

Versions 2

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.4.0 latest A 97/100 0 1.13.0 2026-09-09
v0.3.0 A 97/100 0 1.12.1 2026-08-21

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 97/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/1c-odata-mcp/badge.svg)](https://mcptrustchecker.com/registry/1c-odata-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/1c-odata-mcp"><img src="https://mcptrustchecker.com/registry/1c-odata-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/1c-odata-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan 1c-odata-mcp --online

Use the free API → How scoring works

More in Developer Tools