1C OData MCP
NPM · ONEC-ODATA-MCP · SCANNED AUG 3
Read-only MCP server for 1C:Enterprise via OData with metadata and query builder tools.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (102 of 106), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (102 of 106), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 14 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 448 tokens (~56/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 71% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · onec-odata-mcp
claude mcp add alexgrebeshok-coder-onec-odata-mcp -- npx -y onec-odata-mcp
codex mcp add alexgrebeshok-coder-onec-odata-mcp -- npx -y onec-odata-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"alexgrebeshok-coder-onec-odata-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"onec-odata-mcp"
],
"enabled": true
}
}
} openclaw mcp add alexgrebeshok-coder-onec-odata-mcp --command npx --arg -y --arg onec-odata-mcp
mcp_servers:
alexgrebeshok-coder-onec-odata-mcp:
command: "npx"
args: ["-y", "onec-odata-mcp"] {
"mcpServers": {
"alexgrebeshok-coder-onec-odata-mcp": {
"command": "npx",
"args": [
"-y",
"onec-odata-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +44
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Stability: unverified → 0.23 ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Schema quality: unverified → fair ▲ functional
- License: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: MIT functional
- 1 Aug 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 +3
- Malware scan: pass → unverified ▼ security
- Tool coverage: unverified → 100 ▲ functional
- 30 Jul 26 −21
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 45
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 102 packages
102 packages in the resolved dependency tree · 102 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
odata_build_query ~114
Build validated OData query parameters from structured intent (filters, date period, sort, top). Returns params for odata_query + human explanation.
| Name | Type | Req | Description |
|---|---|---|---|
| datePeriod | object | — | — |
| entity | string | yes | Target entity name |
| expand | array | — | — |
| filters | array | — | Structured filters: field, operator (eq/ne/gt/ge/lt/le/contains/startswith), value |
| orderBy | array | — | — |
| select | array | — | — |
| top | number | — | — |
No output schema declared.
No examples provided.
odata_config ~21
Check 1С OData configuration status and setup instructions
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
odata_count ~42
Count records in an OData entity, optionally with filter
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | Entity name |
| filter | string | — | OData $filter expression |
No output schema declared.
No examples provided.
odata_explain_entity ~43
Describe entity fields, types, keys and navigation properties from metadata
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | Entity name (e.g. Catalog_Контрагенты) |
No output schema declared.
No examples provided.
odata_financial_summary ~38
Auto-detect common 1С financial entities (счета, реализации, контрагенты, заявки) and show counts
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
odata_list_entities ~21
List all available OData entities from 1С
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
odata_metadata ~40
Get entity types and entity sets from 1С metadata (cached, TTL default 1h)
| Name | Type | Req | Description |
|---|---|---|---|
| refresh | boolean | — | Force refresh metadata cache |
No output schema declared.
No examples provided.
odata_query ~129
Query 1С OData entity with filter, select, top, orderBy, expand. Example: entity="Catalog_Контрагенты" filter="Description eq 'ООО Ромашка'"
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | Entity name (e.g. Catalog_Контрагенты) |
| expand | string | — | Navigation properties ($expand) |
| filter | string | — | OData $filter expression |
| orderBy | string | — | Sort field ($orderby) |
| select | string | — | Comma-separated fields ($select) |
| top | number | — | Max records ($top) |
No output schema declared.
No examples provided.