3,400+ MCP servers ready to use
Vinkius

Bring Uptime Monitoring
to Claude Code

Learn how to connect Dotcom-Monitor to Claude Code and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

Get Device DetailsGet Device Monitoring HistoryList Alert GroupsList Available PlatformsList Monitoring DevicesList Monitoring Locations
Use with Your AI Agent
Ask AI about this MCP Server
ChatGPT Claude Perplexity

What is the Dotcom-Monitor MCP Server?

Connect your Dotcom-Monitor monitoring account to any AI agent and simplify how you oversee your website uptime, server performance, and global monitoring locations through natural conversation.

What you can do

  • Device Oversight — List all configured monitoring devices (uptime, speed, API) and retrieve detailed configuration metadata.
  • Performance Tracking — Query historical status data and response times to identify latency trends via AI.
  • Global Monitoring — List available geographic locations and verify where your checks are running from.
  • Alert Management — Query configured alert groups and notification teams to ensure your incident response is ready.
  • Platform Analysis — List available monitoring platforms (ServerView, UserView, WebAPI) to coordinate your checks.
  • Operational Monitoring — Check real-time device health and verify system connectivity directly from the agent.

How it works

1. Subscribe to this server
2. Enter your Dotcom-Monitor API Key (found in your account settings)
3. Start monitoring your digital assets from Claude, Cursor, or any MCP client

Who is this for?

  • DevOps & SREs — quickly retrieve historical performance logs and verify device statuses via simple AI commands.
  • IT Managers — monitor global uptime and verify alert group configurations directly from the workspace.
  • Web Developers — check response times and verify platform availability via the AI assistant.

Built-in capabilities (6)

get_device_details

Get details for a specific device

get_device_monitoring_history

Get historical status for a device

list_alert_groups

List configured alert groups

list_available_platforms

). List monitoring platforms

list_monitoring_devices

List monitoring devices

list_monitoring_locations

List geographic monitoring locations

Why Claude Code?

Claude Code registers Dotcom-Monitor as an MCP server in a single terminal command. Once connected, Claude Code discovers all 6 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where Dotcom-Monitor data drives decisions without human intervention.

  • —

    Single-command setup: claude mcp add registers the server instantly. no config files to edit or applications to restart

  • —

    Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks

  • —

    Claude Code runs headlessly, enabling unattended batch processing using Dotcom-Monitor tools in cron jobs or deployment scripts

  • —

    Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features

See it in action

Dotcom-Monitor in Claude Code

AI Agent→Vinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Dotcom-Monitor and 3,400+ other MCP servers. One platform. One governance layer.

Teams that connect Dotcom-Monitor to Claude Code through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

3,400+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself3,400+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Use with Your AI Agent View step-by-step setup guide for Claude Code →
Enterprise Security

Why teams choose Vinkius for Dotcom-Monitor in Claude Code

The Dotcom-Monitor MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 6 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in Claude Code only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Use with Your AI Agent View full Dotcom-Monitor details →
Dotcom-Monitor
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures Dotcom-Monitor for Claude Code

Every tool call from Claude Code to the Dotcom-Monitor MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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

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

02

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.

03

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.

04

How do I add an MCP server to Claude Code?

Run claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.

05

Can Claude Code run MCP tools in headless mode?

Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.

06

How do I list all connected MCP servers?

Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.

07

Command not found: claude

Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code

08

Connection timeout

Check your internet connection and verify the Edge URL is reachable