mcp-newbuild is an MCP client project for verifying new residential buildings in Russia (новостройки). Its main goal is to conduct due diligence on new residential complexes and developers based on the client's own contract keys with ЕИСЖС (Unified Housing Construction Information System), covering developer verification, escrow accounts, construction permits, and 214-ФЗ compliance, among other matters.
In terms of purpose, the project is used for checking new residential buildings and developers, with verification work premised on the client's own contract keys with ЕИСЖС. The project explicitly states that it does not have access to ЕИСЖС and has not verified data exchange on the client's real keys. Its list of methods is contract-bound and will not send fictitious requests with mismatched credentials. The project also states that it does not constitute investment advice and is not affiliated with ДОМ.РФ or ЕИСЖС.
In terms of main capabilities, according to the available information, the project's current functional status is as follows: it accepts the MCP_NEWBUILD_EISZHS_CLIENT_ID and MCP_NEWBUILD_EISZHS_CLIENT_SECRET environment variables from the ЕИСЖС API offer (бизнес.дом.рф). When there are no account credentials, it returns an honest refusal result indicating that access is not configured, rather than returning a blank "object not found" card. When an account is configured, it returns a spec_closed refusal because the method specification must be provided after signing a contract, and the relevant paths and fields do not exist in public channels. Once the method description is available, the relevant methods will be enabled. The materials do not provide a list of verification methods that are actually available.
In terms of usage, the project configures the ЕИСЖС client ID and secret via environment variables. Obtaining an account requires submitting an application through https://бизнес.дом.рф/api-еисжс and accepting the offer, and is intended for legal entities. The project itself does not have this contract. The project's own deployment is a separate independent service, uses MCP_NEWBUILD_API_KEY, and does not replace the ЕИСЖС keys. The materials do not provide specific installation commands, code examples, or invocation steps.
In terms of applicable scenarios, it is suitable for institutions or developers that need to verify Russian new residential buildings and developers under the condition of the client's own ЕИСЖС contract keys, for example due diligence needs involving escrow accounts, construction permits, and 214-ФЗ compliance. Because the project currently does not yet have a usable data source connection, the range of verification that can actually be performed is limited.
In terms of limitations, the materials explicitly list the following items that are not connected: live calls to ЕИСЖС methods (the description is not public); bypassing наш.дом.рф portal protections without a contract. In addition, neither ЕИСЖС nor наш.дом.рф is connected, the project does not hold ЕИСЖС access rights, and it has not verified exchange on the client's real keys. The method specification is closed-source and must be obtained after signing a contract. The materials do not provide information such as fees, prices, platform support scope, or actual results.
