mcp-newbuild
PYPI · ATOMNO-MCP-NEWBUILD · SCANNED SEP 20
New-build MCP on the client's EISZHS contract. Spec is closed.
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 22 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 15 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability56
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 484 tokens (~80/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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 mcp-newbuild server?
mcp-newbuild runs locally as a PyPI package, launched with uvx atomno-mcp-newbuild. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · atomno-mcp-newbuild
claude mcp add atomno-mcp-mcp-newbuild -- uvx atomno-mcp-newbuild
{
"mcpServers": {
"atomno-mcp-mcp-newbuild": {
"command": "uvx",
"args": [
"atomno-mcp-newbuild"
]
}
}
} {
"servers": {
"atomno-mcp-mcp-newbuild": {
"command": "uvx",
"args": [
"atomno-mcp-newbuild"
]
}
}
} codex mcp add atomno-mcp-mcp-newbuild -- uvx atomno-mcp-newbuild
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"atomno-mcp-mcp-newbuild": {
"type": "local",
"command": [
"uvx",
"atomno-mcp-newbuild"
],
"enabled": true
}
}
} openclaw mcp add atomno-mcp-mcp-newbuild --command uvx --arg atomno-mcp-newbuild
mcp_servers:
atomno-mcp-mcp-newbuild:
command: "uvx"
args: ["atomno-mcp-newbuild"] {
"McpServers": {
"atomno-mcp-mcp-newbuild": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"atomno-mcp-newbuild"
]
}
}
} assistant mcp add atomno-mcp-mcp-newbuild -t stdio -c uvx -a atomno-mcp-newbuild
{
"mcpServers": {
"atomno-mcp-mcp-newbuild": {
"command": "uvx",
"args": [
"atomno-mcp-newbuild"
]
}
}
} 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.
- 19 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.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 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.
- 12 Sept 26 −2
- Stability: pass → 0.83 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed pypi/atomno-mcp-newbuild@0.1.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 22 packages
| Packages resolved | 22 |
|---|---|
| Stale | 1 |
| 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 →
check_construction_permit ~52
Разрешение на строительство: ключ ЕИСЖС клиента или честный отказ. Описание методов закрыто.
| Name | Type | Req | Description |
|---|---|---|---|
| object_id | string | yes | Идентификатор объекта в ЕИСЖС. |
Structured output declared, but exposes no named fields.
No examples provided.
check_developer ~61
Карточка застройщика: ключ ЕИСЖС клиента или честный отказ. Описание методов закрыто — запрос не выдумываем.
| Name | Type | Req | Description |
|---|---|---|---|
| ident | string | yes | ИНН или ОГРН застройщика (юрлица). |
Structured output declared, but exposes no named fields.
No examples provided.
check_escrow ~50
Эскроу: ключ ЕИСЖС клиента или честный отказ. Описание методов закрыто.
| Name | Type | Req | Description |
|---|---|---|---|
| object_id | string | yes | Идентификатор объекта в ЕИСЖС. |
Structured output declared, but exposes no named fields.
No examples provided.
get_developer_risk_summary ~47
Сводка риска: ключ ЕИСЖС клиента или честный отказ. Описание методов закрыто.
| Name | Type | Req | Description |
|---|---|---|---|
| inn | string | yes | ИНН застройщика. |
Structured output declared, but exposes no named fields.
No examples provided.
get_project_declaration ~60
Проектная декларация: ключ ЕИСЖС клиента или честный отказ. Описание методов закрыто.
| Name | Type | Req | Description |
|---|---|---|---|
| object_id | string | yes | Идентификатор объекта (строящегося дома/ЖК) в ЕИСЖС. |
Structured output declared, but exposes no named fields.
No examples provided.
list_new_buildings ~142
Каталог объектов: ключ ЕИСЖС клиента или честный отказ. Описание методов закрыто.
| Name | Type | Req | Description |
|---|---|---|---|
| commissioning_year | – | – | Год планируемого ввода в эксплуатацию. |
| developer_inn | – | – | ИНН застройщика — все объекты его портфеля. |
| escrow | – | – | Только объекты через эскроу (true) / без эскроу (false). |
| limit | integer | – | Максимум результатов. |
| region | – | – | Регион/субъект РФ для фильтрации. |
| stage | – | – | Этап строительства (напр. «котлован», «монтаж этажей»). |
Structured output declared, but exposes no named fields.
No examples provided.
What is the mcp-newbuild server?
mcp-newbuild is listed in the public MCP registry as io.github.atomno-mcp/mcp-newbuild. New-build MCP on the client's EISZHS contract. Spec is closed. This page covers its PyPI package (atomno-mcp-newbuild).
Is the mcp-newbuild server safe to use?
mcp-newbuild scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 mcp-newbuild server expose?
mcp-newbuild exposes 6 tools: check_developer, get_project_declaration, check_escrow, check_construction_permit, list_new_buildings, get_developer_risk_summary. Their descriptions and schemas cost roughly 412 tokens of context every time the server is loaded.
Is the mcp-newbuild server still maintained?
mcp-newbuild is still listed as active in the MCP registry. We last reached this channel on 20 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 mcp-newbuild server under?
mcp-newbuild declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.