1C OData MCP
NPM · ONEC-ODATA-MCP · SCANNED SEP 22
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 → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 103 dependencies flagged as unhealthy. 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 45 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the 1C OData MCP server?
1C OData MCP runs locally as an npm package, launched with npx -y onec-odata-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · onec-odata-mcp
claude mcp add alexgrebeshok-coder-onec-odata-mcp -- npx -y onec-odata-mcp
{
"mcpServers": {
"alexgrebeshok-coder-onec-odata-mcp": {
"command": "npx",
"args": [
"-y",
"onec-odata-mcp"
]
}
}
} {
"servers": {
"alexgrebeshok-coder-onec-odata-mcp": {
"command": "npx",
"args": [
"-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": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"onec-odata-mcp"
]
}
}
} assistant mcp add alexgrebeshok-coder-onec-odata-mcp -t stdio -c npx -a -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.
- 22 Sept 26 0
- Stability: 0.97 → pass security
- 21 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 20 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
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 22 Sept 2026 · Analysed npm/onec-odata-mcp@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 103 packages
| Packages resolved | 103 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
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.
What is the 1C OData MCP server?
1C OData MCP is listed in the public MCP registry as io.github.alexgrebeshok-coder/onec-odata-mcp. Read-only MCP server for 1C:Enterprise via OData with metadata and query builder tools. This page covers its npm package (onec-odata-mcp).
Is the 1C OData MCP server safe to use?
1C OData MCP scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the 1C OData MCP server expose?
1C OData MCP exposes 8 tools: odata_config, odata_list_entities, odata_metadata, odata_explain_entity, odata_build_query, and 3 more. Their descriptions and schemas cost roughly 448 tokens of context every time the server is loaded.
Is the 1C OData MCP server still maintained?
1C OData MCP is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the 1C OData MCP server under?
1C OData MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.