@drumbeats-io
Basic information
Operate Drumbeats monitoring from any AI client — create cron/heartbeat and uptime monitors, triage incidents, and run HTTP/SSL/DNS diagnostics (no account needed for diagnostics).
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"drumbeats": {
"command": "npx",
"args": [
"-y",
"@drumbeats/mcp"
],
"env": {
"DRUMBEATS_API_KEY": "dk_your_key"
}
}
}
}List all Drumbeats projects the configured account API key can access. Returns each project id, name, plan, and basic metadata — use it to find the target project id before creating or querying monitors. Pass include=["channels","groups"] to also return each project's notification channels and groups, whose ids are needed to wire alerts when creating a monitor.
Create a Drumbeats monitor. One tool for all four types, chosen via "type": - JOB_CRON: a job that should run on a cron schedule (schedule = cron expression). - JOB_BASIC: a job expected on a fixed interval (schedule = interval, e.g. "5m"). - JOB_HEARTBEAT: a passive endpoint your job pings (schedule = expected interval). - UPTIME_HTTP: Drumbeats polls a URL (schedule = poll interval; requires uptime_url). All uptime_* fields are only valid when type is UPTIME_HTTP. Wire alerts at create time with notification_channel_ids / notification_group_ids (UUIDs discoverable via list_projects include=channels,groups). Notification channel types: EMAIL, SLACK, TELEGRAM, DISCORD, WEBHOOK, PAGERDUTY, SMS, PUSH.
List all monitors in a Drumbeats project (jobs and uptime checks), with their type, status, and schedule metadata. Requires a project_id from list_projects. Use it to find a monitor id before fetching details, history, or incidents.
Get a single Drumbeats monitor by id, including its type, status, schedule, and alerting metadata.
Update an existing Drumbeats monitor. Provide monitor_id plus only the fields to change. Set status to PAUSED or UP to pause/resume (or use pause_monitor / resume_monitor). The uptime_* fields apply to UPTIME_HTTP monitors.
Pause a monitor by id. It stops running checks and sending alerts until resumed.
Resume a paused monitor by id.
Fetch a monitor's recent history. One tool with a "kind" argument: pings | warnings | checks | response_times. Defaults to pings. Use it to answer "what happened with this monitor lately?".
Get the project-level uptime / SLA summary across all of a project's uptime monitors: overall uptime percentage plus per-monitor uptime, check counts, and response times over a look-back window. The answer to "what is my uptime this month?".
List incidents for a Drumbeats project (downtime / missed-run events), newest first and paginated. Requires a project_id from list_projects. Filter by status (OPEN, ACKNOWLEDGED, RESOLVED) or a single monitor.
Triage a Drumbeats incident: get its details, acknowledge it, or resolve it. One tool with an "action" argument.
Check whether an http(s) URL is reachable and report its status code and response time. Works with no Drumbeats account or API key — handy for a quick "is this site up?" before signing up.
Inspect a host's TLS/SSL certificate — validity, expiry date, and issuer. Works with no Drumbeats account or API key — useful for "is my SSL certificate about to expire?".
Resolve a hostname and report its DNS records (what the domain points to). Works with no Drumbeats account or API key — useful for "what does this domain resolve to?".
The official MCP server for Drumbeats — cron, uptime, and heartbeat monitoring plus status pages, operated from Claude, Cursor, VS Code, or any MCP client.
Configure as a remote server (OAuth, no API key) via streamable HTTP: claude mcp add --transport http drumbeats https://api.drumbeats.io/mcp. Or run locally with npx: npx -y @drumbeats/mcp and set DRUMBEATS_API_KEY in the environment. Omit the API key to use only the diagnostics tools.
It provides tools for monitor creation (`create_monitor`, `list_monitors`, etc.), observation (`get_monitor_history`, `get_uptime_summary`, `list_incidents`), and ad‑hoc diagnostics (`check_http`, `check_ssl`, `check_dns`).
No. The hosted version uses OAuth with no API key. For local use you can provide a `DRUMBEATS_API_KEY`, or omit it entirely to use only the free diagnostics tools.
Streamable HTTP (for hosted OAuth) and standard stdio (for local npm installation).
Get a free API key from your Drumbeats account at https://drumbeats.io.
Yes, the source is available on GitHub under the Apache‑2.0 license.
Senso MCP turns a Joomla 5 or 6 site into a remote MCP server. It runs inside Joomla itself (no extra server, no Node.js bridge) and is secured with OAuth 2.1 and Joomla's own ACL. The free pack lets an AI assistant crea
A curated list of references for MLOps
不止于 CSS
Connect your AI assistant to your own YOUB endurance training account. Read recorded activities with full analysis, planned sessions, race goals, wellness (HRV, sleep, resting HR) and your athletic profile. Create or mov
This open-source curriculum introduces the fundamentals of Model Context Protocol (MCP) through real-world, cross-language examples in .NET, Java, TypeScript, JavaScript, Rust and Python. Designed for developers, it focuses on practical techniques for building modular, scalable,
Comments