Remote MCP · Endpoint

MM7 Company MCP MCP server

No. MM7 Company MCP answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://mcp.mm7.ru/mcp

The last check completed an MCP handshake.

Registry name
ru.mm7.www/company
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
652 ms
Tools exposed
22 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
MM7 public B2B MCP: 1C ITS/RRP, requisites, EDI, cloud trial (GRM/Fresh) for AI agents.
Website
https://www.mm7.ru/agents/
Listing
From the official MCP registry (active).
Recent checks of MM7 Company MCP
CheckedResultHandshake
9 hours agoHandshake completed652 ms
2 days agoHandshake completed473 ms
5 days agoHandshake completed566 ms
7 days agoHandshake completed518 ms
9 days agoHandshake completed483 ms
11 days agoHandshake completed487 ms
13 days agoHandshake completed487 ms
15 days agoHandshake completed483 ms
17 days agoHandshake completed483 ms
19 days agoHandshake completed489 ms
20 days agoHandshake completed514 ms
21 days agoHandshake completed512 ms
23 days agoHandshake completed467 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with MM7 Company MCP and makes no claim about it beyond what these checks measured.