← Registry

Marketing

aishnitsa.ru

Automates demo request form preparation by pre-filling visitor details and requiring manual consent before submission.

WebMCP1 endpoint1 known toolsFirst detected September 3, 2026Last detected September 3, 2026

ENDPOINT 1

https://aishnitsa.ru

No auth detected

MCP server metadata

Name
WebMCP
Capabilities
declarative

Known tools 1

request_demo

Prepare a request for a personal AIшница demonstration. Fill in the visitor's name and phone number, then show the visible form. The visitor must personally accept the data processing terms and click the submit button; never submit automatically.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.webmcp]
url = "https://aishnitsa.ru"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "webmcp": {
      "type": "http",
      "url": "https://aishnitsa.ru"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: webmcp
Remote MCP URL: https://aishnitsa.ru

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "webmcp": {
      "url": "https://aishnitsa.ru"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "webmcp": {
      "type": "http",
      "url": "https://aishnitsa.ru"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "webmcp",
  "transport": "streamable-http",
  "url": "https://aishnitsa.ru"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for aishnitsa.ru was fetched 2026-09-23T05:52:51.348Z.

Trust status Neutral

aishnitsa.ru is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.