An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Dotcom-Monitor to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Manage global uptime and performance through your AI agent.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 6 capabilities

We ship only the actions that matter.

Capability set01 / 02

01-03

3 capabilities in this set.

Part of 6 available through Dotcom-Monitor.

  1. 01

    List alert groups

    This capability lists all your configured alert groups. Use it to see who is being notified during an incident.

  2. 02

    List monitoring devices

    This capability retrieves a list of all your monitoring devices. It covers uptime, speed, and API checks.

  3. 03

    List monitoring locations

    This capability shows the geographic locations where your monitoring checks are currently running.

Capability set02 / 02

04-06

3 capabilities in this set.

Part of 6 available through Dotcom-Monitor.

  1. 04

    Get device details

    This capability pulls specific configuration metadata for a single monitoring device.

  2. 05

    Get device monitoring history

    This capability fetches historical status and response time data for a specific device.

  3. 06

    List available platforms

    This capability lists the monitoring platforms available, such as ServerView or UserView.

Real work

What teams actually run

01

Latency Troubleshooting

Ask your agent to pull historical response times for a specific device to find when a slowdown started.

02

Incident Readiness

Verify that your alert groups and notification teams are correctly configured before a deployment.

03

Global Health Checks

Confirm that your monitoring checks are active in the specific geographic locations you require.

04

Device Auditing

Quickly list all monitoring devices to ensure your entire infrastructure is covered.

Automate a task

Put Dotcom-Monitor to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Dotcom-Monitor works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put Dotcom-Monitor to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

893ms average. Fast in production.

Dotcom-Monitor is checked daily against the live service.

Daily averagePeak 1128ms
Oct 3Today
Fastest day
762ms
Slowest day
1128ms
14-day trend
Stable+4%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 6 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Dotcom-Monitor, so you can see the experience inside your AI.

It does not authenticate your account with Dotcom-Monitor. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Dotcom-Monitor Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_GqGj3Rlz734elQvwGWsaDwAQaGs3sdeIJxtIggc7/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Dotcom-Monitor capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "dotcom-monitor-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_GqGj3Rlz734elQvwGWsaDwAQaGs3sdeIJxtIggc7/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Dotcom-Monitor in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Dotcom-Monitor owners hand off.

This MCP is built for technical teams managing distributed web infrastructure.

  • 01

    DevOps & SREs

    They use the agent to pull historical performance logs and check device status quickly.

  • 02

    IT Managers

    They monitor global uptime and verify alert group setups from their workspace.

  • 03

    Web Developers

    They check response times and platform availability through the AI client.

FAQ

Questions Dotcom-Monitor owners ask.

  • 01

    How do I connect this MCP to my AI client?

    You subscribe to the MCP on Vinkius and enter your Dotcom-Monitor API Key. Once connected, you can use it immediately in Claude, Cursor, or Windsurf.

  • 02

    Which AI clients are compatible?

    This MCP works with any MCP-compatible client, including Claude, Cursor, Windsurf, and VS Code.

  • 03

    Can I check my website speed through the AI?

    Yes, you can ask your agent to retrieve response times and historical performance data for your monitoring devices.

  • 04

    Where do I find my API key?

    Your API key is located within your Dotcom-Monitor account settings.

  • 05

    Does this MCP host my data?

    No, Vinkius hosts the MCP and manages the connection, but the data comes directly from your Dotcom-Monitor account.

  • 06

    Can I check the uptime status of a specific device via AI?

    Yes! Use the get_device_details capability and provide the Device ID. Your agent will retrieve the current operational status and basic performance metrics.

  • 07

    How do I see the history of response times for a monitor?

    Run the get_device_monitoring_history query with your Device ID. The agent will retrieve a historical log of success/failure states and latency data.

  • 08

    Is it possible to list all geographic monitoring locations via AI?

    Absolutely. Use the list_monitoring_locations query. The agent will retrieve the complete list of worldwide regions where Dotcom-Monitor agents are available.

Explore

More in Industry Titans

Suggestions

Connect Dotcom-Monitor to Claude, Cursor, ChatGPT & more