Getmonitor MCP Server

@getmonitor/mcp npm v0.3.1

Published by @getmonitor — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

GetMonitor API MCP server — full management access to all GetMonitor resources

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 95/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 5 = 95. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 2

medium Tool "unlink_monitor_from_status_page" can modify the filesystemMTC-CAP-002

Tool "unlink_monitor_from_status_page" can write, overwrite or delete files (keyword "unlink" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool unlink_monitor_from_status_page

low Mutating tool "unlink_monitor_from_status_page" declares no destructiveHintMTC-CAP-005

Tool "unlink_monitor_from_status_page" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool unlink_monitor_from_status_page

Tools 200

Each tool and what it can reach — statically extracted from the published source.

  • unlink_monitor_from_status_pagewrites files
  • accept_invitationno sensitive capability
  • acknowledge_oncall_alertno sensitive capability
  • add_incident_serviceno sensitive capability
  • add_incident_timeline_noteno sensitive capability
  • add_maintenance_updateno sensitive capability
  • add_organization_team_memberno sensitive capability
  • add_related_incidentno sensitive capability
  • add_rotation_memberno sensitive capability
  • ai_draft_notebookno sensitive capability
Show 190 more tools ↓
  • assign_incident_roleno sensitive capability
  • assign_incident_typeno sensitive capability
  • backfill_organization_teamsno sensitive capability
  • cancel_invitationno sensitive capability
  • cancel_maintenanceno sensitive capability
  • check_organization_slugno sensitive capability
  • check_status_page_domain_availabilityno sensitive capability
  • check_status_page_domain_verificationno sensitive capability
  • close_incidentno sensitive capability
  • complete_maintenanceno sensitive capability
  • confirm_subscriptionno sensitive capability
  • create_component_groupno sensitive capability
  • create_custom_field_definitionno sensitive capability
  • create_destination_configno sensitive capability
  • create_heartbeatno sensitive capability
  • create_incidentno sensitive capability
  • create_incident_actionno sensitive capability
  • create_incident_escalationno sensitive capability
  • create_incident_notebookno sensitive capability
  • create_incident_typeno sensitive capability
  • create_installationno sensitive capability
  • create_maintenanceno sensitive capability
  • create_notebookno sensitive capability
  • create_oncall_routeno sensitive capability
  • create_organizationno sensitive capability
  • create_organization_teamno sensitive capability
  • create_projectno sensitive capability
  • create_rotationno sensitive capability
  • create_schedule_overrideno sensitive capability
  • create_source_map_tokenno sensitive capability
  • create_static_componentno sensitive capability
  • create_status_pageno sensitive capability
  • create_status_page_subscriptionno sensitive capability
  • create_status_page_updateno sensitive capability
  • create_uptime_monitorno sensitive capability
  • delete_component_groupno sensitive capability
  • delete_custom_field_definitionno sensitive capability
  • delete_destination_configno sensitive capability
  • delete_heartbeatno sensitive capability
  • delete_incident_actionno sensitive capability
  • delete_incident_typeno sensitive capability
  • delete_maintenanceno sensitive capability
  • delete_oncall_routeno sensitive capability
  • delete_organizationno sensitive capability
  • delete_organization_teamno sensitive capability
  • delete_projectno sensitive capability
  • delete_rotationno sensitive capability
  • delete_schedule_overrideno sensitive capability
  • delete_static_componentno sensitive capability
  • delete_status_pageno sensitive capability
  • delete_status_page_updateno sensitive capability
  • delete_uptime_monitorno sensitive capability
  • disable_installationno sensitive capability
  • draft_incident_status_updateno sensitive capability
  • export_status_page_subscribersno sensitive capability
  • get_grouped_status_page_monitorsno sensitive capability
  • get_heartbeatno sensitive capability
  • get_incidentno sensitive capability
  • get_incident_custom_field_valuesno sensitive capability
  • get_incident_notebookno sensitive capability
  • get_incidents_overview_statsno sensitive capability
  • get_installationno sensitive capability
  • get_installation_healthno sensitive capability
  • get_integration_appno sensitive capability
  • get_invitationno sensitive capability
  • get_managed_status_pageno sensitive capability
  • get_management_maintenanceno sensitive capability
  • get_monitorno sensitive capability
  • get_monitor_aggregationsno sensitive capability
  • get_notebookno sensitive capability
  • get_oncall_alerts_statsno sensitive capability
  • get_oncall_scheduleno sensitive capability
  • get_organizationno sensitive capability
  • get_organization_monitor_statisticsno sensitive capability
  • get_organization_onboarding_progressno sensitive capability
  • get_organization_statusno sensitive capability
  • get_projectno sensitive capability
  • get_static_component_overrideno sensitive capability
  • get_status_page_badgeno sensitive capability
  • get_status_page_badge_configno sensitive capability
  • get_status_page_component_treeno sensitive capability
  • get_status_page_customizationno sensitive capability
  • get_status_page_maintenance_itemno sensitive capability
  • get_status_page_monitor_statisticsno sensitive capability
  • get_status_page_monitorsno sensitive capability
  • get_status_page_statusno sensitive capability
  • get_status_page_subscription_analyticsno sensitive capability
  • get_status_page_updateno sensitive capability
  • get_subscription_verificationno sensitive capability
  • get_uptime_logsno sensitive capability
  • get_uptime_monitorno sensitive capability
  • get_uptime_monitor_statisticsno sensitive capability
  • get_user_organization_rolesno sensitive capability
  • get_who_is_on_callno sensitive capability
  • invite_organization_memberno sensitive capability
  • join_incidentno sensitive capability
  • leave_incidentno sensitive capability
  • link_monitor_to_status_pageno sensitive capability
  • list_all_monitorsno sensitive capability
  • list_component_groupsno sensitive capability
  • list_custom_field_definitionsno sensitive capability
  • list_destination_configsno sensitive capability
  • list_guest_access_organizationsno sensitive capability
  • list_heartbeatsno sensitive capability
  • list_incident_actionsno sensitive capability
  • list_incident_escalationsno sensitive capability
  • list_incident_participantsno sensitive capability
  • list_incident_timelineno sensitive capability
  • list_incident_typesno sensitive capability
  • list_incidentsno sensitive capability
  • list_installationsno sensitive capability
  • list_integration_appsno sensitive capability
  • list_managed_status_pagesno sensitive capability
  • list_management_maintenanceno sensitive capability
  • list_management_status_page_updatesno sensitive capability
  • list_notebooksno sensitive capability
  • list_oncall_alertsno sensitive capability
  • list_oncall_routesno sensitive capability
  • list_oncall_schedulesno sensitive capability
  • list_organization_invitationsno sensitive capability
  • list_organization_membersno sensitive capability
  • list_organization_teamsno sensitive capability
  • list_organizationsno sensitive capability
  • list_projectsno sensitive capability
  • list_related_incidentsno sensitive capability
  • list_rotationsno sensitive capability
  • list_schedule_overridesno sensitive capability
  • list_source_map_tokensno sensitive capability
  • list_static_componentsno sensitive capability
  • list_status_page_maintenanceno sensitive capability
  • list_status_page_subscribersno sensitive capability
  • list_status_page_updatesno sensitive capability
  • list_status_page_uptime_monitorsno sensitive capability
  • list_subscription_plansno sensitive capability
  • list_uptime_monitorsno sensitive capability
  • move_component_groupno sensitive capability
  • move_monitor_to_groupno sensitive capability
  • pause_heartbeatno sensitive capability
  • publish_incident_status_updateno sensitive capability
  • regenerate_heartbeat_tokenno sensitive capability
  • remove_incident_roleno sensitive capability
  • remove_incident_serviceno sensitive capability
  • remove_organization_memberno sensitive capability
  • remove_organization_team_memberno sensitive capability
  • remove_related_incidentno sensitive capability
  • remove_rotation_memberno sensitive capability
  • remove_status_page_domainno sensitive capability
  • remove_status_page_subscriberno sensitive capability
  • reorder_component_groupsno sensitive capability
  • reorder_static_componentsno sensitive capability
  • reorder_status_page_monitorsno sensitive capability
  • reset_status_page_customizationno sensitive capability
  • resolve_incidentno sensitive capability
  • resolve_oncall_alertno sensitive capability
  • resolve_organization_by_slugno sensitive capability
  • resolve_status_pageno sensitive capability
  • revoke_source_map_tokenno sensitive capability
  • rotate_project_ingestion_keyno sensitive capability
  • set_incident_custom_field_valueno sensitive capability
  • set_status_page_domainno sensitive capability
  • start_maintenanceno sensitive capability
  • summarize_incidentno sensitive capability
  • unpause_heartbeatno sensitive capability
  • unsubscribeno sensitive capability
  • update_component_groupno sensitive capability
  • update_destination_configno sensitive capability
  • update_heartbeatno sensitive capability
  • update_incidentno sensitive capability
  • update_incident_actionno sensitive capability
  • update_incident_typeno sensitive capability
  • update_installation_configno sensitive capability
  • update_maintenanceno sensitive capability
  • update_notebookno sensitive capability
  • update_oncall_scheduleno sensitive capability
  • update_organizationno sensitive capability
  • update_organization_languageno sensitive capability
  • update_organization_member_roleno sensitive capability
  • update_organization_teamno sensitive capability
  • update_projectno sensitive capability
  • update_rotationno sensitive capability
  • update_rotation_memberno sensitive capability
  • update_static_componentno sensitive capability
  • update_status_pageno sensitive capability
  • update_status_page_customizationno sensitive capability
  • update_status_page_monitorno sensitive capability
  • update_status_page_updateno sensitive capability
  • update_uptime_monitorno sensitive capability
  • upsert_static_component_overrideno sensitive capability
  • verify_status_page_domainno sensitive capability
  • verify_subscription_tokenno sensitive capability

What this scan could not see

Versions 3

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.3.1 latest A 95/100 2 1.13.0 2026-09-09
v0.3.0 A 95/100 2 1.13.0 2026-08-29
v0.2.3 A 95/100 2 1.12.1 2026-08-20

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/getmonitor-mcp/badge.svg)](https://mcptrustchecker.com/registry/getmonitor-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/getmonitor-mcp"><img src="https://mcptrustchecker.com/registry/getmonitor-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/getmonitor-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @getmonitor/mcp --online

Use the free API → How scoring works

More in Developer Tools