Marketing

vivaia.jp

An MCP server that subscribes an email address to the VIVAIA newsletter and reports whether the subscription succeeded or the address was already subscribed.

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

ENDPOINT 1

https://vivaia.jp

No auth detected

MCP server metadata

Name: WebMCP

Capabilities

declarative

Known tools 1

subscribe_newsletter

Subscribe an email address to the VIVAIA newsletter. Ask the customer for their email address first, then submit this form with it. Returns whether the subscription succeeded or the address was already subscribed.

Potential side effects

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://vivaia.jp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "webmcp": {
      "type": "http",
      "url": "https://vivaia.jp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: webmcp
Remote MCP URL: https://vivaia.jp

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://vivaia.jp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "webmcp": {
      "type": "http",
      "url": "https://vivaia.jp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "webmcp",
  "transport": "streamable-http",
  "url": "https://vivaia.jp"
}

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 vivaia.jp was fetched 2026-10-01T23:41:26.226Z.

Trust status RestrictedContent

vivaia.jp is assessed as RestrictedContent: Domain runs gambling-related technology.

Indexed

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