MM7 Company MCP
REMOTE · MCP.MM7.RU
MM7 public B2B MCP: 1C ITS/RRP, requisites, EDI, cloud trial (GRM/Fresh) for AI agents.
Available components
Last scanned (13 hours ago)
Scores higher than 62% of remote servers
Unreachable for 1 day in a row. Last reached 20 Nov 2026.
Category E-commerce
Recent critical change
Authorization (19 Nov 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (3)
- HTTPS
- DNSSEC
- Transport
Checks we could not complete (8)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Authorization: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 19 Nov 26 +2
- Authorization: unverified → fail ▼ critical
- Tool “request_reserve_pin_code” is now declared destructive security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Server version: 0.1.10 → 0.1.12 functional
- “check_1c_product_by_reg” reworded the description of “reg_number” cosmetic
- “check_its_subscription” reworded the description of “reg_number” cosmetic
- “get_cloud_trial_status” reworded the description of “email” cosmetic
- “get_cloud_trial_status” reworded the description of “order_id” cosmetic
- “get_cloud_trial_status” reworded the description of “refresh” cosmetic
- “get_cloud_trial_status” reworded the description of “request_id” cosmetic
- “list_cloud_trial_offers” reworded the description of “category” cosmetic
- “list_cloud_trial_offers” reworded the description of “limit” cosmetic
- “list_cloud_trial_offers” reworded the description of “orderable_only” cosmetic
- “list_cloud_trial_offers” reworded the description of “query” cosmetic
- “lookup_rrp” reworded the description of “limit” cosmetic
- “lookup_rrp” reworded the description of “query” cosmetic
- “lookup_rrp” reworded the description of “vendor” cosmetic
- “quote_its_renewal” reworded the description of “product_sku” cosmetic
- “quote_its_renewal” reworded the description of “reg_number” cosmetic
- “request_cloud_trial” reworded the description of “comment” cosmetic
- “request_cloud_trial” reworded the description of “company_name” cosmetic
- “request_cloud_trial” reworded the description of “contact_name” cosmetic
- “request_cloud_trial” reworded the description of “email” cosmetic
- “request_cloud_trial” reworded the description of “employee_count” cosmetic
- “request_cloud_trial” reworded the description of “inn” cosmetic
- “request_cloud_trial” reworded the description of “kit” cosmetic
- “request_cloud_trial” reworded the description of “phone” cosmetic
- “request_cloud_trial” reworded the description of “portal_login” cosmetic
- “request_cloud_trial” reworded the description of “product_sku” cosmetic
- “request_cloud_trial” reworded the description of “seats” cosmetic
- “request_its_renewal_invoice” reworded the description of “address” cosmetic
- “request_its_renewal_invoice” reworded the description of “comment” cosmetic
- “request_its_renewal_invoice” reworded the description of “contact_phone” cosmetic
- “request_its_renewal_invoice” reworded the description of “delivery_channel” cosmetic
- “request_its_renewal_invoice” reworded the description of “edo_id” cosmetic
- “request_its_renewal_invoice” reworded the description of “email” cosmetic
- “request_its_renewal_invoice” reworded the description of “inn” cosmetic
- “request_its_renewal_invoice” reworded the description of “kpp” cosmetic
- “request_its_renewal_invoice” reworded the description of “name” cosmetic
- “request_its_renewal_invoice” reworded the description of “ogrn” cosmetic
- “request_its_renewal_invoice” reworded the description of “product_sku” cosmetic
- “request_its_renewal_invoice” reworded the description of “reg_number” cosmetic
- “request_license_owner_data” reworded the description of “captcha” cosmetic
- “request_license_owner_data” reworded the description of “captcha_id” cosmetic
- “request_license_owner_data” reworded the description of “email” cosmetic
- “request_license_owner_data” reworded the description of “reg_number” cosmetic
- “request_pin_codes_state” reworded the description of “captcha” cosmetic
- “request_pin_codes_state” reworded the description of “captcha_id” cosmetic
- “request_pin_codes_state” reworded the description of “email” cosmetic
- “request_pin_codes_state” reworded the description of “reg_number” cosmetic
- “request_reserve_pin_code” reworded the description of “captcha” cosmetic
- “request_reserve_pin_code” reworded the description of “captcha_id” cosmetic
- “request_reserve_pin_code” reworded the description of “current_pin_code” cosmetic
- “request_reserve_pin_code” reworded the description of “email” cosmetic
- “request_reserve_pin_code” reworded the description of “reg_number” cosmetic
- “request_service_agreement_edo” reworded the description of “comment” cosmetic
- “request_service_agreement_edo” reworded the description of “contact_email” cosmetic
- “request_service_agreement_edo” reworded the description of “counterparty_inn” cosmetic
- “request_service_agreement_edo” reworded the description of “counterparty_name” cosmetic
- “request_service_agreement_edo” reworded the description of “template” cosmetic
- “submit_counterparty_profile” reworded the description of “acts_on_basis” cosmetic
- “submit_counterparty_profile” reworded the description of “agent_callback_notes” cosmetic
- “submit_counterparty_profile” reworded the description of “agent_mcp_auth_hint” cosmetic
- “submit_counterparty_profile” reworded the description of “agent_mcp_url” cosmetic
- “submit_counterparty_profile” reworded the description of “agent_name” cosmetic
- “submit_counterparty_profile” reworded the description of “agent_role” cosmetic
- “submit_counterparty_profile” reworded the description of “bank_name” cosmetic
- “submit_counterparty_profile” reworded the description of “bik” cosmetic
- “submit_counterparty_profile” reworded the description of “checking_account” cosmetic
- “submit_counterparty_profile” reworded the description of “cloud_trial_request_id” cosmetic
- “submit_counterparty_profile” reworded the description of “company_name” cosmetic
- “submit_counterparty_profile” reworded the description of “contact_email” cosmetic
- “submit_counterparty_profile” reworded the description of “contact_name” cosmetic
- “submit_counterparty_profile” reworded the description of “contact_phone” cosmetic
- “submit_counterparty_profile” reworded the description of “correspondent_account” cosmetic
- “submit_counterparty_profile” reworded the description of “director_name” cosmetic
- “submit_counterparty_profile” reworded the description of “director_title” cosmetic
- “submit_counterparty_profile” reworded the description of “edo_id” cosmetic
- “submit_counterparty_profile” reworded the description of “edo_operator” cosmetic
- “submit_counterparty_profile” reworded the description of “extra_json” cosmetic
- “submit_counterparty_profile” reworded the description of “inn” cosmetic
- “submit_counterparty_profile” reworded the description of “kpp” cosmetic
- “submit_counterparty_profile” reworded the description of “legal_address” cosmetic
- “submit_counterparty_profile” reworded the description of “notes” cosmetic
- “submit_counterparty_profile” reworded the description of “ogrn” cosmetic
- “submit_counterparty_profile” reworded the description of “postal_address” cosmetic
- “submit_counterparty_profile” reworded the description of “purpose” cosmetic
- “subscribe_its_renewal” reworded the description of “comment” cosmetic
- “subscribe_its_renewal” reworded the description of “days_before” cosmetic
- “subscribe_its_renewal” reworded the description of “delivery_channel” cosmetic
- “subscribe_its_renewal” reworded the description of “edo_id” cosmetic
- “subscribe_its_renewal” reworded the description of “email” cosmetic
- “subscribe_its_renewal” reworded the description of “inn” cosmetic
- “subscribe_its_renewal” reworded the description of “name” cosmetic
- “subscribe_its_renewal” reworded the description of “product_sku” cosmetic
- “subscribe_its_renewal” reworded the description of “reg_number” cosmetic
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 8 Nov 26 0
- Stability: 0.97 → pass security
- 7 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 0
- Stability: 0.97 → pass security
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 21 Nov 2026 · Probed https://mcp.mm7.ru/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.mm7.ru. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ru. | DS published | 26734 | 8 | Verified |
| mm7.ru. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.mm7.ru/mcp | Unreachable | ||
| http (plaintext) | http://mcp.mm7.ru/mcp | HTTPS enforced |
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_1c_product_by_reg ~65
Check a 1C product by registration number: whether the number is known and a short ITS contract summary. Same API as «Check product» on mm7.ru.
| Name | Type | Req | Description |
|---|---|---|---|
| reg_number | string | yes | 1C product registration number (reg. №). |
Structured output declared, but exposes no named fields.
No examples provided.
check_its_subscription ~52
Check 1C:ITS subscription status by product registration number. Same Partner API as the form on mm7.ru.
| Name | Type | Req | Description |
|---|---|---|---|
| reg_number | string | yes | 1C product registration number (reg. №). |
Structured output declared, but exposes no named fields.
No examples provided.
get_1c_license_captcha ~56
Fetch a portal.1c.ru captcha image for license PIN / owner requests. Returns captcha_id + image_base64. Then call request_pin_codes_state, request_license_owner_data, or request_reserve_pin_code.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_cloud_trial_status ~129
Poll cloud demo status after request_cloud_trial. Required: email (same as in the order) + request_id (ctr_…) or order_id. Returns ready, demo_url when the base is up, application status, trial dates. Poll every 1–5 minutes while provisioning.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Same email used in request_cloud_trial. | |
| order_id | string | – | Partner API order id (alternative to request_id). |
| refresh | boolean | – | If true, refresh status from Partner API. |
| request_id | string | – | ctr_… id from request_cloud_trial. |
Structured output declared, but exposes no named fields.
No examples provided.
get_company_requisites ~21
Legal and bank requisites of OOO MM7.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_contact_channels ~21
Public contact channels: phone, email, website, support.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_contract_status ~26
Contract status bound to the API key (stub until 1C/B24 wiring).
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_edo_identity ~20
Current EDO operator and identifier for MM7.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_business_activities ~19
Business activities / service lines of MM7.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_cloud_trial_offers ~131
Full catalog of 1C:GRM demo configurations (live Partner API) plus Fresh. Each offer includes description, docs_url (v8.1c.ru / solutions.1c.ru), category, kits, required fields. Filter with query/category. Then call request_cloud_trial.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category filter (e.g. accounting, trade). |
| limit | integer | – | Max offers to return. |
| orderable_only | boolean | – | If true, only offers that can be ordered now. |
| query | string | – | Optional text filter over offer names/descriptions. |
Structured output declared, but exposes no named fields.
No examples provided.
list_its_products ~24
List ITS/KP products available for renewal quotes (RRP floor).
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_mm7_capabilities ~20
List tools available for the current access tier.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
lookup_rrp ~160
Look up recommended retail price (RRP) by product name fragment or code. Covers firm 1C, Bitrix CMS (Управление сайтом), Bitrix24 (cloud+box), and Cleverence Mobile SMARTS «Склад 15». Optional vendor filter: 1c | bitrix-cms | bitrix24-cloud | bitrix24-box | cleverence-wh15. Returns RRP only — never dealer or partner prices.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (1–50). |
| query | string | yes | Product name fragment, code, or barcode. |
| vendor | – | – | Optional vendor filter: 1c | bitrix-cms | bitrix24-cloud | bitrix24-box | cleverence-wh15. |
Structured output declared, but exposes no named fields.
No examples provided.
quote_its_renewal ~64
Quote ITS renewal: check subscription by registration number and return catalog price for product_sku (never below RRP).
| Name | Type | Req | Description |
|---|---|---|---|
| product_sku | string | yes | SKU from list_its_products. |
| reg_number | string | yes | 1C product registration number. |
Structured output declared, but exposes no named fields.
No examples provided.
request_cloud_trial ~270
Order a 1C:GRM cloud demo (or queue Fresh). Required for GRM: product_sku (from list_cloud_trial_offers), inn, phone, email, company_name, contact_name (ФИО). Optional: kit (Файловый/Клиент-серверный), portal_login, employee_count, seats. Creates demo via Partner API /orders/submit; login usually emailed by 1capp.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | Optional comment. |
| company_name | string | yes | Company / org name for the demo. |
| contact_name | string | – | Contact person full name (ФИО). |
| string | yes | Contact email (1capp sends login here). | |
| employee_count | integer | – | Approx. employee count; 0 = omit. |
| inn | string | – | INN (required for GRM auto-provision). |
| kit | string | – | Kit: Файловый or Клиент-серверный (when offered). |
| phone | string | yes | Contact phone in international or RU format. |
| portal_login | string | – | Existing portal.1c.ru login if any. |
| product_sku | string | yes | Offer SKU from list_cloud_trial_offers. |
| seats | integer | – | Requested seats. |
Structured output declared, but exposes no named fields.
No examples provided.
request_its_renewal_invoice ~223
Request an invoice for ITS renewal. Provide registration number, product_sku, and payer requisites. Phase 1 accepts into a queue (no live 1C invoice yet).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Payer legal address. |
| comment | string | – | Optional comment for MM7. |
| contact_phone | string | – | Contact phone. |
| delivery_channel | string | – | email | edo | email_and_edo. |
| edo_id | string | – | EDO id when delivery includes edo. |
| string | – | Email for invoice when delivery includes email. | |
| inn | string | yes | Payer INN (10 or 12 digits). |
| kpp | string | – | Payer KPP (orgs). |
| name | string | yes | Payer legal name. |
| ogrn | string | – | Payer OGRN/OGRNIP. |
| product_sku | string | yes | SKU from list_its_products / quote_its_renewal. |
| reg_number | string | yes | 1C product registration number. |
Structured output declared, but exposes no named fields.
No examples provided.
request_license_owner_data ~109
Request license owner data check via portal.1c.ru. Client API key required. Requires captcha from get_1c_license_captcha. Result is emailed by 1C.
| Name | Type | Req | Description |
|---|---|---|---|
| captcha | string | yes | Captcha text solved from the image. |
| captcha_id | string | yes | captcha_id from get_1c_license_captcha. |
| string | yes | Email where 1C will send owner-data result. | |
| reg_number | string | yes | 1C product registration number. |
Structured output declared, but exposes no named fields.
No examples provided.
request_pin_codes_state ~124
Request current PIN-code state from portal.1c.ru (active/cancelled/free). Client API key required. Requires captcha from get_1c_license_captcha. Result is emailed by 1C — not returned in the tool response body.
| Name | Type | Req | Description |
|---|---|---|---|
| captcha | string | yes | Captcha text solved from the image. |
| captcha_id | string | yes | captcha_id from get_1c_license_captcha. |
| string | yes | Email where 1C will send the PIN state result. | |
| reg_number | string | yes | 1C product registration number. |
Structured output declared, but exposes no named fields.
No examples provided.
request_reserve_pin_code ~133
Request a reserve/additional PIN from portal.1c.ru. Client API key required. Requires captcha + current active PIN. Result is emailed by 1C. Side-effect on the license kit — use carefully.
| Name | Type | Req | Description |
|---|---|---|---|
| captcha | string | yes | Captcha text solved from the image. |
| captcha_id | string | yes | captcha_id from get_1c_license_captcha. |
| current_pin_code | string | yes | Currently active PIN of the license kit. |
| string | yes | Email where 1C will send the reserve PIN. | |
| reg_number | string | yes | 1C product registration number. |
Structured output declared, but exposes no named fields.
No examples provided.
request_service_agreement_edo ~110
Request a template service agreement via EDO. MVP accepts the request into a local queue (no live EDO send).
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | Optional free-text comment. |
| contact_email | string | – | Contact email for the request. |
| counterparty_inn | string | yes | Counterparty INN (10 or 12 digits). |
| counterparty_name | string | yes | Legal name of the counterparty. |
| template | string | – | Agreement template key. Default: service_support. |
Structured output declared, but exposes no named fields.
No examples provided.
submit_counterparty_profile ~448
Leave your organization / agent profile at MM7 for later billing and contact. Send company requisites (INN, address, bank, director, EDO id), who you are, and optionally your own MCP URL for two-way agent callbacks. Stored at MM7 (profile_id). Do not put secret tokens — only https MCP URL + auth hint. Size-capped (~16 KiB); rate-limited.
| Name | Type | Req | Description |
|---|---|---|---|
| acts_on_basis | string | – | Acts on the basis of (Устав / доверенность…). |
| agent_callback_notes | string | – | How MM7 should call back. |
| agent_mcp_auth_hint | string | – | Non-secret auth hint (e.g. header name). |
| agent_mcp_url | string | – | HTTPS MCP URL for callbacks (no secrets). |
| agent_name | string | – | Calling agent / system name. |
| agent_role | string | – | Agent role label. |
| bank_name | string | – | Bank name. |
| bik | string | – | BIK. |
| checking_account | string | – | Settlement account. |
| cloud_trial_request_id | string | – | Optional ctr_… to link a trial. |
| company_name | string | yes | Legal company name. |
| contact_email | string | – | Primary contact email. |
| contact_name | string | – | Contact person name. |
| contact_phone | string | – | Contact phone. |
| correspondent_account | string | – | Correspondent account. |
| director_name | string | – | Director full name. |
| director_title | string | – | Director title (e.g. Генеральный директор). |
| edo_id | string | – | EDO identifier. |
| edo_operator | string | – | EDO operator name. |
| extra_json | string | – | Optional extra JSON object as string (size-capped). |
| inn | string | – | INN (10 or 12 digits). |
| kpp | string | – | KPP. |
| legal_address | string | – | Legal address. |
| notes | string | – | Free-text notes. |
| ogrn | string | – | OGRN/OGRNIP. |
| postal_address | string | – | Postal address. |
| purpose | string | – | Why you leave the profile (default billing). |
Structured output declared, but exposes no named fields.
No examples provided.
subscribe_its_renewal ~166
Subscribe to an ITS renewal reminder. When the subscription is near expiry, MM7 will send an invoice via the chosen channel. Phase 1 stores the preference only.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | Optional comment. |
| days_before | integer | – | Remind this many days before expiry (7–90). |
| delivery_channel | string | – | email | edo | email_and_edo. |
| edo_id | string | – | EDO id when delivery includes edo. |
| string | – | Email when delivery includes email. | |
| inn | string | – | Optional payer INN. |
| name | string | – | Optional payer name. |
| product_sku | string | yes | SKU from list_its_products. |
| reg_number | string | yes | 1C product registration number. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the MM7 Company MCP server?
MM7 Company MCP is a hosted endpoint at https://mcp.mm7.ru/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.mm7.ru
claude mcp add --transport http ru-mm7-www-company 'https://mcp.mm7.ru/mcp'
What is the MM7 Company MCP server?
MM7 Company MCP is listed in the public MCP registry as ru.mm7.www/company. MM7 public B2B MCP: 1C ITS/RRP, requisites, EDI, cloud trial (GRM/Fresh) for AI agents. This page covers its hosted endpoint (https://mcp.mm7.ru/mcp).
Is the MM7 Company MCP server safe to use?
MM7 Company MCP scores 75 out of 100 on VerifyMCP. 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 MM7 Company MCP server expose?
MM7 Company MCP exposes 22 tools: list_mm7_capabilities, get_company_requisites, list_business_activities, get_edo_identity, get_contact_channels, and 17 more. Their descriptions and schemas cost roughly 2,391 tokens of context every time the server is loaded.
Does the MM7 Company MCP server require authentication?
Its publisher declares no required credentials for MM7 Company MCP. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the MM7 Company MCP server still maintained?
MM7 Company MCP is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 20 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the MM7 Company MCP server?
VerifyMCP ran 3 checks on MM7 Company MCP, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about MM7 Company MCP: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.