# com.googleapis.monitoring/mcp (remote · monitoring.googleapis.com) Gain visibility into the performance, availability, and health of your apps and infrastructure. - Trust score: 67/100 (medium) - Change this week: +5 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-08-04 ## Components - remote · `monitoring.googleapis.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/com-googleapis-monitoring-mcp/monitoring.md), [page](https://verifymcp.io/servers/com-googleapis-monitoring-mcp/monitoring) ## Channel facts - Endpoint: `https://monitoring.googleapis.com/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `1.0.0` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-08-04. - **Endpoint Security**: 63/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. - HSTS check failed: the Strict-Transport-Security header is absent. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 61/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 2381 tokens (~264/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 30/100 - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - Structured output schemas are declared (100% of tools); any adoption earns full credit. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## Install ### Claude ```bash claude mcp add --transport http com-googleapis-monitoring-mcp https://monitoring.googleapis.com/mcp ``` ### Codex ```toml [mcp_servers.com-googleapis-monitoring-mcp] url = "https://monitoring.googleapis.com/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "com-googleapis-monitoring-mcp": { "type": "remote", "url": "https://monitoring.googleapis.com/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add com-googleapis-monitoring-mcp --url https://monitoring.googleapis.com/mcp --transport streamable-http ``` ### Hermes ```yaml mcp_servers: com-googleapis-monitoring-mcp: url: "https://monitoring.googleapis.com/mcp" ``` ### Other ```json { "mcpServers": { "com-googleapis-monitoring-mcp": { "type": "http", "url": "https://monitoring.googleapis.com/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-08-04 (score 67, +1) No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-08-02 (score 66, +1) No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-07-31 (score 65, +1) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-30 (score 64, +1) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-29 (score 63, +1) No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-07-27 (score 62, +1) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-26 (score 61) First indexed and scored. ## MCP tools (9) ### `list_timeseries` (~467 tokens) Lists time series data from the Google Cloud Monitoring API Input parameters: - `aggregation`: Specifies the alignment of data points in individual time series as well as how to combine the retrieved time series across specified labels. By default (if no `aggregation` is explicitly specified),… - `filter` (string, required): Required. A [monitoring filter](https://cloud.google.com/monitoring/api/v3/filters) that specifies which time series should be returned. The filter must specify a single metric type, and can addition… - `interval` (required): Required. The time interval for which results should be returned. Only time series that contain data points in the specified interval are included in the response. - `name` (string, required): Required. The [project](https://cloud.google.com/monitoring/api/v3#project_name), organization or folder on which to execute the request. The format is: projects/[PROJECT_ID_OR_NUMBER] organizations/… - `orderBy` (string): Unsupported: must be left blank. The points in each time series are currently returned in reverse time order (most recent to oldest). - `pageSize` (integer): A positive number that is the maximum number of results to return. If `page_size` is empty or more than 100,000 results, the effective `page_size` is 100,000 results. If `view` is set to `FULL`, this… - `pageToken` (string): If this field is not empty then it must contain the `nextPageToken` value returned by a previous call to this method. Using this field causes the method to return additional results from the previous… - `secondaryAggregation`: Apply a second aggregation after `aggregation` is applied. May only be specified if `aggregation` is specified. - `view` (string, required): Required. Specifies which information is returned about the time series. Output parameters: - `executionErrors` (array): Query execution errors that may have caused the time series data returned to be incomplete. - `nextPageToken` (string): If there are more results than have been returned, then this field is set to a non-empty value. To see the additional results, use that value as `page_token` in the next call to this method. - `timeSeries` (array): One or more time series that match the filter included in the request. - `unit` (string): The unit in which all `time_series` point values are reported. `unit` follows the UCUM format for units as seen in https://unitsofmeasure.org/ucum.html. If different `time_series` have different unit… - `unreachable` (array): Cloud regions that were unreachable which may have caused incomplete data to be returned. ### `query_range` (~333 tokens) Evaluate a PromQL query in a range of time Input parameters: - `end` (string): The end time to evaluate the query for. Either floating point UNIX seconds or RFC3339 formatted timestamp. - `location` (string): Location of the resource information. Has to be "global" now. - `name` (string, required): Required. The project on which to execute the request. Data associcated with the project's workspace stored under the The format is: projects/[PROJECT_ID_OR_NUMBER]. Open source API but used as a req… - `query` (string): A PromQL query string. Query language documentation: https://prometheus.io/docs/prometheus/latest/querying/basics/. - `start` (string): The start time to evaluate the query for. Either floating point UNIX seconds or RFC3339 formatted timestamp. - `step` (string): The resolution of query result. Either a Prometheus duration string (https://prometheus.io/docs/prometheus/latest/querying/basics/#time-durations) or floating point seconds. This non-standard encodin… - `timeout` (string): An upper bound timeout for the query. Either a Prometheus duration string (https://prometheus.io/docs/prometheus/latest/querying/basics/#time-durations) or floating point seconds. This non-standard e… Output parameters: - `data` (object): The Prometheus API response payload. Typically present when status is 'success'. - `error` (string): The error message. Present when status is 'error'. - `errorType` (string): The type of error (e.g., 'bad_data', 'timeout'). Present when status is 'error'. - `status` (string): Indicates if the API call was successful or resulted in an error. - `warnings` (array): A list of warnings that occurred while processing the request. ### `get_alert_policy` (~91 tokens) Use this as the primary tool to get information about a specific alerting policy. Alerting policies define the conditions under which you want to be notified about issues with your services. This is useful for understanding the details of a specific alert configuration. Input parameters: - `name` (string, required): Required. The alerting policy to retrieve. The format is: projects/[PROJECT_ID_OR_NUMBER]/alertPolicies/[ALERT_POLICY_ID] Output parameters: - `alertStrategy`: Control over how this alerting policy's notification channels are notified. - `combiner` (string): How to combine the results of multiple conditions to determine if an incident should be opened. If `condition_time_series_query_language` is present, this must be `COMBINE_UNSPECIFIED`. - `conditions` (array): A list of conditions for the policy. The conditions are combined by AND or OR according to the `combiner` field. If the combined conditions evaluate to true, then an incident is created. A policy can… - `creationRecord`: A read-only record of the creation of the alerting policy. If provided in a call to create or update, this field will be ignored. - `displayName` (string): A short name or phrase used to identify the policy in dashboards, notifications, and incidents. To avoid confusion, don't use the same display name for multiple policies in the same project. The name… - `documentation`: Documentation that is included with notifications and incidents related to this policy. Best practice is for the documentation to include information to help responders understand, mitigate, escalate… - `enabled` (boolean): Whether or not the policy is enabled. On write, the default interpretation if unset is that the policy is enabled. On read, clients should not make any assumption about the state if it has not been p… - `mutationRecord`: A read-only record of the most recent change to the alerting policy. If provided in a call to create or update, this field will be ignored. - `name` (string): Identifier. Required if the policy exists. The resource name for this policy. The format is: projects/[PROJECT_ID_OR_NUMBER]/alertPolicies/[ALERT_POLICY_ID] `[ALERT_POLICY_ID]` is assigned by Cloud M… - `notificationChannels` (array): Identifies the notification channels to which notifications should be sent when incidents are opened or closed or when new violations occur on an already opened incident. Each element of this array c… - `severity` (string): Optional. The severity of an alerting policy indicates how important incidents generated by that policy are. The severity level will be displayed on the Incident detail page and in notifications. - `userLabels` (object): User-supplied key/value data to be used for organizing and identifying the `AlertPolicy` objects. The field can contain up to 64 entries. Each key and value is limited to 63 Unicode characters or 128… - `validity`: Read-only description of how the alerting policy is invalid. This field is only set when the alerting policy is invalid. An invalid alerting policy will not generate incidents. ### `list_alert_policies` (~353 tokens) Use this as the primary tool to list the alerting policies in a Google Cloud project. Alerting policies define the conditions under which you want to be notified about issues with your services. This is useful for understanding what alerts are currently configured. Input parameters: - `filter` (string): Optional. If provided, this field specifies the criteria that must be met by alert policies to be included in the response. For more details, see [sorting and filtering](https://cloud.google.com/moni… - `name` (string, required): Required. The [project](https://cloud.google.com/monitoring/api/v3#project_name) whose alert policies are to be listed. The format is: projects/[PROJECT_ID_OR_NUMBER] Note that this field names the p… - `orderBy` (string): Optional. A comma-separated list of fields by which to sort the result. Supports the same set of field references as the `filter` field. Entries can be prefixed with a minus sign to sort by the field… - `pageSize` (integer): Optional. The maximum number of results to return in a single response. - `pageToken` (string): Optional. If this field is not empty then it must contain the `nextPageToken` value returned by a previous call to this method. Using this field causes the method to return more results from the prev… Output parameters: - `alertPolicies` (array): The returned alert policies. - `nextPageToken` (string): If there might be more results than were returned, then this field is set to a non-empty value. To see the additional results, use that value as `page_token` in the next call to this method. - `totalSize` (integer): The total number of alert policies in all pages. This number is only an estimate, and may change in subsequent pages. https://aip.dev/158 ### `get_alert` (~96 tokens) Use this as the primary tool to get information about a specific alert. An alert is the representation of a violation of an alert policy. This is useful for understanding the details of a specific alert. Input parameters: - `name` (string, required): Required. The name of the alert. The format is: projects/[PROJECT_ID_OR_NUMBER]/alerts/[ALERT_ID] The `[ALERT_ID]` is a system-assigned unique identifier for the alert. Output parameters: - `closeTime` (string): The time when the alert was closed. - `log`: The log information associated with the alert. This field is only populated for log-based alerts. - `metadata`: The metadata of the monitored resource. - `metric`: The metric type and any metric labels preserved from the incident's generating condition. - `name` (string): Identifier. The name of the alert. The format is: projects/[PROJECT_ID_OR_NUMBER]/alerts/[ALERT_ID] The `[ALERT_ID]` is a system-assigned unique identifier for the alert. - `openTime` (string): The time when the alert was opened. - `policy`: The snapshot of the alert policy that generated this alert. - `resource`: The monitored resource type and any monitored resource labels preserved from the incident's generating condition. - `state` (string): Output only. The current state of the alert. ### `list_alerts` (~310 tokens) Use this as the primary tool to list the alerts in a Google Cloud project. An alert is the representation of a violation of an alert policy. This is useful for understanding current and past violations of an alert policy. Input parameters: - `filter` (string): Optional. An alert is returned if there is a match on any fields belonging to the alert or its subfields. - `orderBy` (string): Optional. A comma-separated list of fields in `Alert` to use for sorting. The default sort direction is ascending. To specify descending order for a field, add a `desc` modifier. The following fields… - `pageSize` (integer): Optional. The maximum number of results to return in a single response. If not set to a positive number, at most 50 alerts will be returned. The maximum value is 1000; values above 1000 will be coerc… - `pageToken` (string): Optional. If non-empty, `page_token` must contain a value returned as the `next_page_token` in a previous response to request the next set of results. - `parent` (string, required): Required. The name of the project to list alerts for. Output parameters: - `alerts` (array): The list of alerts. - `nextPageToken` (string): If not empty, indicates that there may be more results that match the request. Use the value in the `page_token` field in a subsequent request to fetch the next set of results. The token is encrypted… - `totalSize` (integer): The estimated total number of matching results for this query. ### `list_metric_descriptors` (~422 tokens) Use this as the primary tool to discover the types of metrics available in a Google Cloud project. This is a good first step to understanding what data is available for monitoring and building dashboards or alerts. Input parameters: - `activeOnly` (boolean): Optional. If true, only metrics and monitored resource types that have recent data (within roughly 25 hours) will be included in the response. - If a metric descriptor enumerates monitored resource t… - `filter` (string): Optional. If this field is empty, all custom and system-defined metric descriptors are returned. Otherwise, the [filter](https://cloud.google.com/monitoring/api/v3/filters) specifies which metric des… - `name` (string, required): Required. The [project](https://cloud.google.com/monitoring/api/v3#project_name) on which to execute the request. The format is: projects/[PROJECT_ID_OR_NUMBER] - `pageSize` (integer): Optional. A positive number that is the maximum number of results to return. The default and maximum value is 10,000. If a page_size <= 0 or > 10,000 is submitted, will instead return a maximum of 10… - `pageToken` (string): Optional. If this field is not empty then it must contain the `nextPageToken` value returned by a previous call to this method. Using this field causes the method to return additional results from th… Output parameters: - `metricDescriptors` (array): The metric descriptors that are available to the project and that match the value of `filter`, if present. - `nextPageToken` (string): If there are more results than have been returned, then this field is set to a non-empty value. To see the additional results, use that value as `page_token` in the next call to this method. ### `list_dashboards` (~175 tokens) Use this as the primary tool to retrieve a list of existing custom monitoring dashboards in a Google Cloud project. Custom monitoring dashboards let users view and analyze data from different sources in the same context. This is useful for understanding what custom dashboards are currently configured and available in a given project. Input parameters: - `pageSize` (integer): A positive number that is the maximum number of results to return. If unspecified, a default of 1000 is used. - `pageToken` (string): Optional. If this field is not empty then it must contain the `nextPageToken` value returned by a previous call to this method. Using this field causes the method to return additional results from th… - `parent` (string, required): Required. The scope of the dashboards to list. The format is: projects/[PROJECT_ID_OR_NUMBER] Output parameters: - `dashboards` (array): The list of requested dashboards. - `nextPageToken` (string): If there are more results than have been returned, then this field is set to a non-empty value. To see the additional results, use that value as `page_token` in the next call to this method. ### `get_dashboard` (~134 tokens) Use this as the primary tool to retrieve a single specific custom monitoring dashboard from a Google Cloud project using the resource name of the requested dashboard. Custom monitoring dashboards let users view and analyze data from different sources in the same context. This is often used as a follow on to list_dashboards to get full details on a specific dashboard. Input parameters: - `name` (string, required): Required. The resource name of the Dashboard. The format is one of: - `dashboards/[DASHBOARD_ID]` (for system dashboards) - `projects/[PROJECT_ID_OR_NUMBER]/dashboards/[DASHBOARD_ID]` (for custom das… Output parameters: - `annotations`: Configuration for event annotations to display on this dashboard. - `columnLayout`: The content is divided into equally spaced columns and the widgets are arranged vertically. - `dashboardFilters` (array): Filters to reduce the amount of data charted based on the filter criteria. - `displayName` (string): Required. The mutable, human-readable name. - `etag` (string): `etag` is used for optimistic concurrency control as a way to help prevent simultaneous updates of a policy from overwriting each other. An `etag` is returned in the response to `GetDashboard`, and u… - `gridLayout`: Content is arranged with a basic layout that re-flows a simple list of informational elements like widgets or tiles. - `labels` (object): Labels applied to the dashboard - `mosaicLayout`: The content is arranged as a grid of tiles, with each content widget occupying one or more grid blocks. - `name` (string): Identifier. The resource name of the dashboard. - `rowLayout`: The content is divided into equally spaced rows and the widgets are arranged horizontally. ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-googleapis-monitoring-mcp/monitoring#diagnostics ## Score history - 2026-08-04: 67 - 2026-08-03: 66 - 2026-08-02: 66 - 2026-08-01: 65 - 2026-07-31: 65 - 2026-07-30: 64 - 2026-07-29: 63 - 2026-07-28: 62 - 2026-07-27: 62 - 2026-07-26: 61 ## Links - Remote endpoint: https://monitoring.googleapis.com/mcp - Changelog RSS feed: https://verifymcp.io/servers/com-googleapis-monitoring-mcp/monitoring/changelog.xml - Changelog JSON feed: https://verifymcp.io/servers/com-googleapis-monitoring-mcp/monitoring/changelog.json - HTML version of this page: https://verifymcp.io/servers/com-googleapis-monitoring-mcp/monitoring