--- title: "Uptrends MCP server for AI agents - actionlake" description: "Give Claude 236 Uptrends actions through one MCP server: alert definition, private location. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/uptrends updated: 2026-10-23 --- Connectors · Observability & analytics # Uptrends MCP server for AI agents. actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Uptrends and the rest of your systems. It gives your agent 236 Uptrends actions (106 reads, 90 writes and 40 that wait for a confirmation) and holds the Uptrends credential itself, so the agent never does. It paces Uptrends's limits and records every call. [Connect Uptrends free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) 100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you. `claude mcp add --transport http actionlake https://connect.actionlake.com/mcp` the first call ``` do { action: "uptrends.operator.get_all_operators", intent: "check which Uptrends account is connected" } # Gets a list of all operators · read · 1 upstream call ``` - 236 actions in one signed file - 106 read look, never change - 90 write create and update - 40 wait for a yes destructive, confirmed first Set up ## Connect Uptrends in three steps. 1. 01 ### Add actionlake to Claude. Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us. `https://connect.actionlake.com/mcp` 2. 02 ### Connect Uptrends. Username and secret. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key. - `username` Uptrends API account username (the `UserName` POST /Register returned; not your login email) - `password` Uptrends API account password (the `Password` POST /Register returned) ``` account { op: "connections.requirements", service: "uptrends" } # free: exactly what to paste, and what is found for you ``` 3. 03 ### Make the first call. Check before a write. Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free. ``` do { action: "uptrends.operator.get_all_operators" } # gets a list of all operators · read · 1 upstream call check { action: "uptrends.operator.create_operator", input: { … } } # free: inputs, permissions, cost and confirmations, nothing sent ``` Uptrends at a glance **Sign-in** Username and secret. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. **You provide** `username` `password` **Limits we pace to** 5 calls a second, per connection **API covered** Uptrends API v4 (Swagger 2.0, 1.0.0)`api.uptrends.com/v4` **Built from** Uptrends's documentation, read 23 October 2026[api.uptrends.com](https://api.uptrends.com/v4/swagger/v1/swagger.json) [uptrends.com](https://www.uptrends.com/support/kb/api) **Service file** Version 1.0.0, signed (Ed25519) **Cached reads** 85 of 106 reads, for up to 5 minutes; a write clears what it affects **Shared entities** 4, so ask can line Uptrends up with your other systems **Data** Processed and stored in Sydney, Australia. No US region yet Capabilities ## What an AI agent can do in Uptrends. 236 actions in 23 areas. Every one carries its effect, so a key can allow the reads and hold the rest. - **106** read look, never change - **90** write create and update - **40** destructive wait for a confirmation 1. ### Alert definition 29 9 read · 13 write · 7 destructive Creates a new alert definition · Gets a list of all alert definitions · Partially updates the definition for the specified alert definition · Gets the specified alert definition 2. ### Private location 20 8 read · 9 write · 3 destructive Create private location authorizations for private location If the wanted authorizations requires other authorizations, these will be added as well · Create new checkpoint for the specified private location · Create new checkpoint for the specified private location · Get private location authorizations of private location 3. ### Monitor 18 6 read · 8 write · 4 destructive Returns the definition of all monitors available in the account · Creates a new monitor · Returns the definition of the specified monitor · Partially updates the definition of the specified monitor 4. ### Operator 17 6 read · 8 write · 3 destructive Gets a list of all operators · Creates a new operator · Gets the details of the operator with the provided OperatorGuid · Updates an existing operator 5. ### Monitor group 16 4 read · 9 write · 3 destructive Adds the provided maintenance period to all monitors in the group specified · Adds the specified monitor to the monitor group · Create monitor authorizations for monitor group If the wanted authorizations requires other authorizations, these will be added as well · Creates a new monitor group 6. ### Monitor result export settings 16 7 read · 6 write · 3 destructive Creates a new OpenTelemetry connection settings configuration · Creates a new OpenTelemetry rule set configuration · Creates a new monitor result export settings configuration · Returns all OpenTelemetry connection settings 7. ### Operator group 15 5 read · 7 write · 3 destructive Gets all operator groups · Creates a new operator group · Gets the details of an operator group · Updates the operator group with the Guid specified 8. ### Monitor check 14 14 read · 0 write · 0 destructive Returns all monitor check data · Returns a single monitor check · Gets all partial checks for a concurrent monitor check · Returns monitor check data for a specific monitor **15 more areas · 91 actions** - Vault **14** - Sla **12** - Integration **11** - Public status page **9** - Checkpoint **8** - Rum **8** - API user **6** - Dashboard **6** - Scheduled report **6** - Account **2** - Alert **2** - Statistics **2** - Status **2** - Timezone **2** - Outgoing phone number **1** Top actions ## The Uptrends API, shaped for agents. The ids your agent types, what each does, and the one name it shares with other systems. 54 of Uptrends's 54 action names are shared with at least one other connector, so an agent learns them once. | Action | What it does | Effect | Same name in | | --- | --- | --- | --- | | `uptrends.operator.get_all_operators` Gets a list of all operators | Gets a list of all operators. | read | `identity.user.list` 474 connectors | | `uptrends.operator_group.get_all_operator_groups` Gets all operator groups | Gets all operator groups. | read | `identity.group.list` 262 connectors | | `uptrends.monitor.get_monitors` Returns the definition of all monitors available in the account | Returns the definition of all monitors available in the account. | read | `monitoring.monitor.list` 32 connectors | | `uptrends.operator.create_operator` Creates a new operator | Creates a new operator. | write | `identity.user.create` 262 connectors | | `uptrends.operator_group.create_operator_group` Creates a new operator group | Creates a new operator group. | write | `identity.group.create` 205 connectors | | `uptrends.monitor.post_monitor` Creates a new monitor | Creates a new monitor. | write | `monitoring.monitor.create` 27 connectors | | `uptrends.operator.delete_operator` Deletes an existing operator | Deletes an existing operator. | destructive | `identity.user.delete` 253 connectors | | `uptrends.alert.get_monitor_alerts` Returns alerts for a specific monitor | Returns alerts for a specific monitor. | read | `monitoring.alert.list` 51 connectors | | `uptrends.sla.get_slas` Gets a list of all SLA definitions | Gets a list of all SLA definitions. | read | `service.sla.list` 12 connectors | | `uptrends.integration.get_all_integrations` Gets a list of all integrations | Gets a list of all integrations. | read | `monitoring.notification_channel.list` 18 connectors | | `uptrends.dashboard.get_all_dashboards` Returns data for all dashboards | Returns data for all dashboards. | read | `monitoring.dashboard.list` 15 connectors | | `uptrends.alert_definition.create_alert_definition` Creates a new alert definition | Creates a new alert definition. | write | `monitoring.notification_rule.create` 11 connectors | Try it ## Prompts to paste into Claude. Each one names the Uptrends actions it will call, so you know what it reads and what it changes before you send it. 1. Read read Who has access in Uptrends? List every user and their role. calls `uptrends.operator.get_all_operators` 2. Write write Creates a new operator in Uptrends. Show me exactly what you will send before you save it. calls `uptrends.operator.create_operator` Governance for Uptrends ## Destructive actions wait for a yes. 40 Uptrends actions are destructive. The first 10: - Deletes an existing operator `uptrends.operator.delete_operator` - Deletes the specified operator group `uptrends.operator_group.delete_operator_group` - Deletes the specified monitor `uptrends.monitor.delete_monitor` - Delete the specified dashboard `uptrends.dashboard.delete_dashboard` - Deletes an existing alert definition `uptrends.alert_definition.delete_alert_definition` - Deletes an existing api user `uptrends.api_user.delete_api_user` - Deletes the specified SLA `uptrends.sla.delete_sla` - Deletes the specified vault item `uptrends.vault.delete_vault_item` - Delete the specified scheduled report `uptrends.scheduled_report.delete_specified_scheduled_report` - Deletes the definition of the specified public status page `uptrends.public_status_page.delete_public_status_page` A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after. do uptrends.operator.delete_operator confirm_policy: **human** Deletes an existing operator? **intent:** the user asked me to deletes an existing operator run suspended · waiting for a named person · key _uptrends-agent_ cannot confirm itself In the console, or from an emailed signed link. a key for this connector ``` account { op: "keys.create", name: "uptrends-agent", allowed_actions: ["uptrends.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "uptrends.operator.delete_operator", approver: "lead@example.com" }, { match: "uptrends.operator_group.delete_operator_group", approver: "lead@example.com" }, { match: "uptrends.monitor.delete_monitor", approver: "lead@example.com" } ] } ``` Illustrative. Scoped to Uptrends only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person. Cost ## What Uptrends costs on actionlake. Every Uptrends action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call Uptrends refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. - 1 upstream call per action all 236 Uptrends actions - 236 actions page each page of a long list is one call - 85 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every Uptrends action. 236 actions by area: the id your agent calls, what it does, and its effect. **Alert definition 29** - `uptrends.alert_definition.add_integration_to_escalation_level` Adds an integration to a specified escalation level write - `uptrends.alert_definition.add_monitor_group_to_alert_definition` Adds a monitor group to the specified alert definition write - `uptrends.alert_definition.add_monitor_to_alert_definition` Adds a monitor to the specified alert definition write - `uptrends.alert_definition.add_operator_group_to_escalation_level` Adds an operator group to the specified escalation level write - `uptrends.alert_definition.add_operator_to_escalation_level` Adds an operator to the specified escalation level write - `uptrends.alert_definition.create_alert_definition` Creates a new alert definition write - `uptrends.alert_definition.create_authorization_for_alert_definition` Create authorizations for alert definition If the wanted authorizations requires other authorizations, these will be added as well write - `uptrends.alert_definition.delete_alert_definition` Deletes an existing alert definition destructive - `uptrends.alert_definition.delete_authorization_for_alert_definition` Delete alert definition authorization for alert definition destructive - `uptrends.alert_definition.get_all_alert_definitions` Gets a list of all alert definitions read - `uptrends.alert_definition.get_all_escalation_level_integrations` Gets all integrations for a specified escalation level read - `uptrends.alert_definition.get_all_escalation_levels` Gets all escalation level information for the specified alert definition read - `uptrends.alert_definition.get_all_members` Gets a list of all monitor and monitor group guids for the specified alert definition read - `uptrends.alert_definition.get_authorizations_of_alert_definition` Get authorizations of alert definition read - `uptrends.alert_definition.get_escalation_level` Gets the escalation level information of the specified alert definition read - `uptrends.alert_definition.get_escalation_level_integration` Gets a single integration for a specified escalation level read - `uptrends.alert_definition.get_escalation_level_operator` Gets the operator and operator group guids for the specified escalation level read - `uptrends.alert_definition.get_specified_alert_definitions` Gets the specified alert definition read - `uptrends.alert_definition.patch_alert_definition` Partially updates the definition for the specified alert definition write - `uptrends.alert_definition.patch_alert_definition_escalation` Partially updates the escalation level for the specified alert definition write - `uptrends.alert_definition.put_alert_definition` Updates the definition for the specified alert definition write - `uptrends.alert_definition.put_alert_definition_escalation` Updates the escalation level for the specified alert definition write - `uptrends.alert_definition.remove_integration_from_escalation_level` Removes an integration from a specified escalation level destructive - `uptrends.alert_definition.remove_monitor_from_alert_definition` Removes a monitor for the specified alert definition destructive - `uptrends.alert_definition.remove_monitor_group_from_alert_definition` Removes a monitor group for the specified alert definition destructive - `uptrends.alert_definition.remove_operator_from_escalation_level` Removes an operator for the specified escalation level destructive - `uptrends.alert_definition.remove_operator_group_from_escalation_level` Removes an operator group for the specified escalation level destructive - `uptrends.alert_definition.update_integration_for_escalation_with_patch` Partially updates an integration for a specified escalation level write - `uptrends.alert_definition.update_integration_for_escalation_with_put` Updates an integration for a specified escalation level write **Private location 20** - `uptrends.private_location.create_authorization_for_private_location` Create private location authorizations for private location If the wanted authorizations requires other authorizations, these will be added as well write - `uptrends.private_location.create_private_location_checkpoint` Create new checkpoint for the specified private location write - `uptrends.private_location.create_private_location_checkpoint_for_monitor_group` Create new checkpoint for the specified private location write - `uptrends.private_location.delete_authorization_for_private_location` Delete private location authorization for private location destructive - `uptrends.private_location.delete_private_location` Deletes a private location destructive - `uptrends.private_location.delete_private_location_checkpoint` Delete checkpoint of the specified private location destructive - `uptrends.private_location.get_authorizations_of_private_location` Get private location authorizations of private location read - `uptrends.private_location.get_private_location` Returns the definition of the specified private location read - `uptrends.private_location.get_private_location_checkpoint` Gets a list of all checkpoint of the specified private location read - `uptrends.private_location.get_private_location_checkpoints` Gets a list of all checkpoint of the specified private location read - `uptrends.private_location.get_private_location_health` Returns the health info of the specified private location read - `uptrends.private_location.get_private_locations` Returns the definition of all private locations in the account read - `uptrends.private_location.get_specified_private_checkpoint_health` Returns the status of the specified private checkpoints read - `uptrends.private_location.patch_private_location` Partially updates existing private location write - `uptrends.private_location.patch_private_location_checkpoint` Partially updates existing private location checkpoint write - `uptrends.private_location.post_private_location` Creates a new private location write - `uptrends.private_location.post_private_location_with_monitor_group` Creates a new private location for the specified monitor group write - `uptrends.private_location.private_location_health` Returns the status of the private checkpoints in the given location read - `uptrends.private_location.put_private_location` Updates existing private location write - `uptrends.private_location.put_private_location_checkpoint` Updates existing private location checkpoint write **Monitor 18** - `uptrends.monitor.cleanup_maintenance_periods` Clears out all one-time maintenance periods for the specified monitor older than the specified date destructive - `uptrends.monitor.clone_monitor` Creates a clone (duplicate) of the specified monitor write - `uptrends.monitor.create_authorization_for_monitor` Create monitor authorizations for monitor If the wanted authorizations requires other authorizations, these will be added as well write - `uptrends.monitor.create_maintenance_period_for_monitor` Saves the new maintenance period provided for the specified monitor write - `uptrends.monitor.delete_authorization_for_monitor` Delete monitor authorization for monitor destructive - `uptrends.monitor.delete_maintenance_period_from_monitor` Deletes the specified maintenance period from the specified monitor destructive - `uptrends.monitor.delete_monitor` Deletes the specified monitor destructive - `uptrends.monitor.get_all_maintenance_periods_for_monitor` Finds all maintenance periods for a monitor read - `uptrends.monitor.get_authorizations_of_monitor` Get monitor authorizations of monitor read - `uptrends.monitor.get_monitor` Returns the definition of the specified monitor read - `uptrends.monitor.get_monitor_groups` Returns the Guid of each monitor group where the specified monitor is a member of read - `uptrends.monitor.get_monitors` Returns the definition of all monitors available in the account read - `uptrends.monitor.get_monitors_by_monitor_group` Returns the definition of all monitors available in the account that are a member of the specified monitor group read - `uptrends.monitor.patch_monitor` Partially updates the definition of the specified monitor write - `uptrends.monitor.post_monitor` Creates a new monitor write - `uptrends.monitor.post_monitor_and_add_to_monitor_group` Creates a new monitor and adds it to specified monitor group write - `uptrends.monitor.put_monitor` Updates the definition of the specified monitor write - `uptrends.monitor.update_maintenance_period_for_monitor` Updates the specified maintenance schedule for the specified monitor write **Operator 17** - `uptrends.operator.add_duty_period_for_operator` Adds a duty schedule to the specified operator write - `uptrends.operator.create_operator` Creates a new operator write - `uptrends.operator.create_operator_and_add_to_operator_group` Creates a new operator and adds it to specified operator group write - `uptrends.operator.delete_authorization_for_operator` Removes the specified authorization of this operator destructive - `uptrends.operator.delete_duty_schedule_from_operator` Deletes the specified duty schedule of the specified operator destructive - `uptrends.operator.delete_operator` Deletes an existing operator destructive - `uptrends.operator.get_all_operators` Gets a list of all operators read - `uptrends.operator.get_authorizations_for_operator` Gets all authorizations for the specified operator read - `uptrends.operator.get_duty_schedule_for_operator` Gets the duty schedules for an specified operator read - `uptrends.operator.get_newsletter_subscription` Gets the newsletter subscription values read - `uptrends.operator.get_operator` Gets the details of the operator with the provided OperatorGuid read - `uptrends.operator.get_operator_groups_for_operator` Gets a list of all operator groups for the specified operator read - `uptrends.operator.post_authorization_for_operator` Assigns the specified authorization to this operator write - `uptrends.operator.update_duty_period_for_operator` Updates the specified duty schedule of the specified operator write - `uptrends.operator.update_newsletter_subscription` Update the newsletter subscription values for the specified operator write - `uptrends.operator.update_operator` Updates an existing operator write - `uptrends.operator.update_operator_with_patch` Updates an existing operator write **Monitor group 16** - `uptrends.monitor_group.add_maintenance_period_to_all_members` Adds the provided maintenance period to all monitors in the group specified write - `uptrends.monitor_group.add_monitor_to_monitor_group` Adds the specified monitor to the monitor group write - `uptrends.monitor_group.create_authorization_for_monitor_group` Create monitor authorizations for monitor group If the wanted authorizations requires other authorizations, these will be added as well write - `uptrends.monitor_group.create_monitor_group` Creates a new monitor group write - `uptrends.monitor_group.delete_authorization_for_monitor_group` Delete monitor authorization for monitor group destructive - `uptrends.monitor_group.delete_monitor_group` Deletes the specified monitor group destructive - `uptrends.monitor_group.get_all_monitor_groups` Gets all monitor groups read - `uptrends.monitor_group.get_authorizations_of_monitor_group` Get monitor authorizations of monitor group read - `uptrends.monitor_group.get_monitor_group` Gets the details of a monitor group read - `uptrends.monitor_group.get_monitor_group_members` Gets a list of all members of a monitor group read - `uptrends.monitor_group.remove_monitor_from_monitor_group` Removes the specified monitor from the monitor group destructive - `uptrends.monitor_group.start_all_monitor_alerts_in_group` Starts alerting for all monitors that are a member of the monitor group specified by the monitor group GUID write - `uptrends.monitor_group.start_all_monitors_in_group` Starts all monitors that are a member of the monitor group specified by the monitor group GUID write - `uptrends.monitor_group.stop_all_monitor_alerts_in_group` Stops alerting for all monitors that are a member of the monitor group specified by the monitor group GUID write - `uptrends.monitor_group.stop_all_monitors_in_group` Stops all monitors that are a member of the monitor group specified by the monitor group GUID write - `uptrends.monitor_group.update_monitor_group` Updates the monitor group with the Guid specified write **Monitor result export settings 16** - `uptrends.monitor_result_export_settings.create_connection_settings` Creates a new OpenTelemetry connection settings configuration write - `uptrends.monitor_result_export_settings.create_rule_set` Creates a new OpenTelemetry rule set configuration write - `uptrends.monitor_result_export_settings.create_settings` Creates a new monitor result export settings configuration write - `uptrends.monitor_result_export_settings.delete_connection_settings` Deletes an OpenTelemetry connection settings configuration destructive - `uptrends.monitor_result_export_settings.delete_rule_set` Deletes an OpenTelemetry rule set configuration destructive - `uptrends.monitor_result_export_settings.delete_settings` Deletes a monitor result export settings configuration destructive - `uptrends.monitor_result_export_settings.get_connection_settings` Returns a specific OpenTelemetry connection settings configuration read - `uptrends.monitor_result_export_settings.get_connection_settings_all` Returns all OpenTelemetry connection settings read - `uptrends.monitor_result_export_settings.get_rule_sets` Returns a specific OpenTelemetry rule set configuration read - `uptrends.monitor_result_export_settings.get_rule_sets_all` Returns all OpenTelemetry rule sets read - `uptrends.monitor_result_export_settings.get_settings` Returns a specific monitor result export settings configuration read - `uptrends.monitor_result_export_settings.get_settings_all` Returns all monitor result settings for the current operator read - `uptrends.monitor_result_export_settings.get_status` Returns the status of the monitor result export settings configuration read - `uptrends.monitor_result_export_settings.update_connection_settings` Updates an existing OpenTelemetry connection settings configuration write - `uptrends.monitor_result_export_settings.update_rule_set` Updates an existing OpenTelemetry rule set configuration write - `uptrends.monitor_result_export_settings.update_settings` Updates an existing monitor result export settings configuration write **Operator group 15** - `uptrends.operator_group.add_duty_schedule_to_all_members` Adds the provided duty schedule to all operators in the group specified write - `uptrends.operator_group.add_operator_to_operator_group` Adds the specified operator to the operator group write - `uptrends.operator_group.all_operators_in_group_off_duty` Set the OnDuty flag to off for all operators that are a member of the operator group specified by the operator group GUID write - `uptrends.operator_group.all_operators_in_group_on_duty` Set the OnDuty flag to on for all operators that are a member of the operator group specified by the operator group GUID write - `uptrends.operator_group.create_operator_group` Creates a new operator group write - `uptrends.operator_group.delete_authorization_for_operator_group` Removes the specified authorization of the operator group destructive - `uptrends.operator_group.delete_operator_group` Deletes the specified operator group destructive - `uptrends.operator_group.get_all_operator_groups` Gets all operator groups read - `uptrends.operator_group.get_authorizations_for_operator_group` Gets all authorizations for the specified operator group read - `uptrends.operator_group.get_operator_group` Gets the details of an operator group read - `uptrends.operator_group.get_operator_group_by_external_id` Gets the details of an operator group read - `uptrends.operator_group.get_operator_group_members` Gets a list of all members of an operator group read - `uptrends.operator_group.post_authorization_for_operator_group` Assigns the specified authorization to the operator group write - `uptrends.operator_group.remove_operator_from_operator_group` Removes the specified operator from the operator group destructive - `uptrends.operator_group.update_operator_group` Updates the operator group with the Guid specified write **Monitor check 14** - `uptrends.monitor_check.get_account_monitor_checks` Returns all monitor check data read - `uptrends.monitor_check.get_concurrent_monitor_partial_checks` Gets all partial checks for a concurrent monitor check read - `uptrends.monitor_check.get_console_log_info` Returns console log information for a monitor check read - `uptrends.monitor_check.get_filmstrip` Gets the filmstrip for a specified monitor check read - `uptrends.monitor_check.get_http_details` Returns HTTP details for a monitor check read - `uptrends.monitor_check.get_monitor_check` Returns monitor check data for a specific monitor read - `uptrends.monitor_check.get_monitor_group_data` Returns monitor check data for a specific monitor group read - `uptrends.monitor_check.get_multistep_details` Returns Multi-Step API details for a monitor check read - `uptrends.monitor_check.get_page_source_info` Returns page source information for a monitor check read - `uptrends.monitor_check.get_postman_details` Returns Postman API details for a monitor check read - `uptrends.monitor_check.get_screenshots` Gets a specific screenshot for a specified monitor check read - `uptrends.monitor_check.get_single_monitor_check` Returns a single monitor check read - `uptrends.monitor_check.get_transaction_details` Returns transaction step details for a monitor check read - `uptrends.monitor_check.get_waterfall_info` Returns waterfall information for a monitor check read **Vault 14** - `uptrends.vault.create_authorization_for_vault_section` Creates a new authorization for the specified vault section write - `uptrends.vault.create_new_vault_item` Creates a new vault item write - `uptrends.vault.create_new_vault_section` Creates a new vault section write - `uptrends.vault.delete_authorization_for_vault_section` Deletes the specified authorization for the specified vault section destructive - `uptrends.vault.delete_vault_item` Deletes the specified vault item destructive - `uptrends.vault.delete_vault_section` Deletes the specified vault section destructive - `uptrends.vault.get_all_vault_items` Returns all vault items read - `uptrends.vault.get_all_vault_sections` Returns all vault sections read - `uptrends.vault.get_authorizations_for_vault_section` Returns all authorizations for the specified vault section read - `uptrends.vault.get_vault_item` Returns the specified vault item read - `uptrends.vault.get_vault_section` Returns the specified vault section read - `uptrends.vault.partially_update_vault_item` Partially updates the specified vault item write - `uptrends.vault.update_vault_item` Updates the specified vault item write - `uptrends.vault.update_vault_section` Updates the specified vault section write **Sla 12** - `uptrends.sla.create_sla` Creates a new SLA write - `uptrends.sla.delete_exclusion_period` Deletes the specified exclusion period for the specified SLA destructive - `uptrends.sla.delete_sla` Deletes the specified SLA destructive - `uptrends.sla.get_exclusion_period` Gets the specified exclusion period for the specified SLA read - `uptrends.sla.get_exclusion_periods` Gets a list of all exclusion periods for the specified SLA read - `uptrends.sla.get_sla` Gets the specified SLA definition read - `uptrends.sla.get_slas` Gets a list of all SLA definitions read - `uptrends.sla.patch_exclusion_period` Partially updates the specified exclusion period for the specified SLA write - `uptrends.sla.patch_sla` Partially updates the definition of the specified SLA write - `uptrends.sla.post_exclusion_period` Creates a new exclusion period for the specified SLA write - `uptrends.sla.put_exclusion_period` Updates the specified exclusion period for the specified SLA write - `uptrends.sla.put_sla` Updates the definition of the specified SLA write **Integration 11** - `uptrends.integration.create_authorization_for_integration` Create authorizations for integration If the wanted authorizations requires other authorizations, these will be added as well write - `uptrends.integration.create_custom_integration` Creates a new custom integration write - `uptrends.integration.delete_authorization_for_integration` Delete integration authorization for integration destructive - `uptrends.integration.delete_custom_integration` Deletes the specified custom integration destructive - `uptrends.integration.delete_integration` Deletes the specified integration. Not all integration types can be deleted destructive - `uptrends.integration.get_all_custom_integration` Gets a list of all custom integrations read - `uptrends.integration.get_all_integrations` Gets a list of all integrations read - `uptrends.integration.get_authorizations_of_integration` Get authorizations of integration read - `uptrends.integration.get_custom_integration` Returns the details of the specified custom integration read - `uptrends.integration.get_integration` Gets the specified integration read - `uptrends.integration.update_custom_integration` Updates the specified custom integration write **Public status page 9** - `uptrends.public_status_page.add_authorization_to_public_status_page` Creates a new authorization for the specified public status page write - `uptrends.public_status_page.delete_public_status_page` Deletes the definition of the specified public status page destructive - `uptrends.public_status_page.get_authorizations_for_public_status_page` Returns all authorizations for the specified public status page read - `uptrends.public_status_page.get_public_status_page` Returns the definition of the specified public status page read - `uptrends.public_status_page.get_public_status_pages` Returns the definition of all public status pages available in the account read - `uptrends.public_status_page.patch_public_status_page` Partially updates the definition of the specified public status page write - `uptrends.public_status_page.post_public_status_page` Creates a new public status page write - `uptrends.public_status_page.put_public_status_page` Updates the definition of the specified public status page write - `uptrends.public_status_page.remove_authorization_from_public_status_page` Removes an authorization from a public status page destructive **Checkpoint 8** - `uptrends.checkpoint.get_all_checkpoint_regions` Returns all the checkpoint regions read - `uptrends.checkpoint.get_all_checkpoints` Returns all the checkpoints that are not deleted read - `uptrends.checkpoint.get_all_server_ipv4_addresses` Anonymous call that returns all the IPv4 addresses of all the checkpoint servers read - `uptrends.checkpoint.get_all_server_ipv6_addresses` Anonymous call that returns all the IPv6 addresses of all the checkpoint servers read - `uptrends.checkpoint.get_checkpoint` Returns the specified checkpoint, deleted or not read - `uptrends.checkpoint.get_checkpoint_region_checkpoints` Returns the checkpoints for the specified checkpoint region read - `uptrends.checkpoint.get_server` Returns the requested checkpoint server read - `uptrends.checkpoint.get_specified_checkpoint_region` Returns the specified checkpoint region read **Rum 8** - `uptrends.rum.delete_rum_website` Deletes the specified RUM website destructive - `uptrends.rum.get_rum_metrics_for_all_websites` Returns all metrics of all RUM websites read - `uptrends.rum.get_rum_website` Returns the definition of the specified RUM website, including the RUM insertion script read - `uptrends.rum.get_rum_website_metrics` Returns all metrics of the specified RUM website read - `uptrends.rum.get_rum_websites` Returns the definition of all RUM websites available in the account read - `uptrends.rum.patch_rum_website` Partially updates the definition of the specified RUM website write - `uptrends.rum.post_rum_website` Creates a new RUM website write - `uptrends.rum.put_rum_website` Updates the definition of the specified RUM website write **API user 6** - `uptrends.api_user.create_api_user` Creates a new api user write - `uptrends.api_user.delete_api_user` Deletes an existing api user destructive - `uptrends.api_user.get_all_api_users` Gets a list of all api users read - `uptrends.api_user.get_all_api_users_for_operator` Gets a list of all api users of the specified operator read - `uptrends.api_user.get_api_user` Gets the details of the api user with the provided api user read - `uptrends.api_user.update_api_user` Updates an existing api user write **Dashboard 6** - `uptrends.dashboard.clone_dashboard` Clone the specified dashboard write - `uptrends.dashboard.delete_dashboard` Delete the specified dashboard destructive - `uptrends.dashboard.get_all_dashboards` Returns data for all dashboards read - `uptrends.dashboard.get_one_dashboard` Returns data for the specified dashboard read - `uptrends.dashboard.partially_update_dashboard` Partially update the specified dashboard write - `uptrends.dashboard.update_dashboard` Update the specified dashboard write **Scheduled report 6** - `uptrends.scheduled_report.create_scheduled_report` Creates a new scheduled report write - `uptrends.scheduled_report.delete_specified_scheduled_report` Delete the specified scheduled report destructive - `uptrends.scheduled_report.get_all_scheduled_reports` Returns data for all scheduled reports read - `uptrends.scheduled_report.get_specified_scheduled_report` Returns data for the specified scheduled report read - `uptrends.scheduled_report.partially_update_scheduled_report` Partially update the specified scheduled report write - `uptrends.scheduled_report.update_scheduled_report` Update the specified scheduled report write **Account 2** - `uptrends.account.get_account_statistics` Returns the account statistics read - `uptrends.account.get_settings` Returns account general settings read **Alert 2** - `uptrends.alert.get_monitor_alerts` Returns alerts for a specific monitor read - `uptrends.alert.get_monitor_group_alerts` Returns alerts for a specific monitor group read **Statistics 2** - `uptrends.statistics.get_monitor_group_statistics` Gets the monitor group statistics read - `uptrends.statistics.get_monitor_statistics` Gets the monitor statistics read **Status 2** - `uptrends.status.get_monitor_group_status` Gets a list of all monitor group status data read - `uptrends.status.get_monitor_status` Gets all monitor status data read **Timezone 2** - `uptrends.timezone.get_all_timezones` Gets all timezones available read - `uptrends.timezone.get_timezone_by_id` Gets the timezone with the specified Id read **Outgoing phone number 1** - `uptrends.outgoing_phone_number.get_all_outgoing_phone_numbers` Gets a list of all outgoing phone numbers available read Questions ## The Uptrends MCP server, answered. **Is there an Uptrends MCP server for Claude?** Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 236 Uptrends actions across alert definition, private location, monitor and operator, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Uptrends. **What do I need to connect Uptrends?** Uptrends API account username (the `UserName` POST /Register returned; not your login email) and Uptrends API account password (the `Password` POST /Register returned). The free call account { op: "connections.requirements", service: "uptrends" } lists exactly what to paste. **Can an AI agent delete or change things in Uptrends?** Only if its key allows it, and only with an explicit confirmation. 40 Uptrends actions are destructive, including deletes an existing operator, deletes the specified operator group and deletes the specified monitor. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it. **Will an AI agent use up my Uptrends API limit?** actionlake paces every call to the limits in the Uptrends service file: 5 calls a second per connection. Repeated reads are answered from cache (85 Uptrends actions can be), which never reaches Uptrends. **What does an Uptrends action cost?** One upstream call, the only unit actionlake bills. A list that pages bills one call per page (236 Uptrends actions page). Cache hits, searches, dry runs and calls Uptrends refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. **Which Uptrends API does it cover?** The Uptrends API v4 (Swagger 2.0, 1.0.0) at api.uptrends.com/v4. It is built from Uptrends's documentation as read on 23 October 2026. 236 actions in 23 areas, each one in the signed service file (version 1.0.0). **Does actionlake keep my Uptrends data, and where?** actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Uptrends credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models. **Which AI clients can use it?** Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names. ## More connectors like Uptrends Shares the most action names with - [New Relic 24](https://actionlake.com/connectors/new-relic) - [Axiom 20](https://actionlake.com/connectors/axiom) - [IBM NS1 Connect 18](https://actionlake.com/connectors/ibm-ns1-connect) - [Sentry 16](https://actionlake.com/connectors/sentry) - [Databricks 14](https://actionlake.com/connectors/databricks) - [Honeybadger 14](https://actionlake.com/connectors/honeybadger) Joins with, on shared entities - [HaloPSA 3](https://actionlake.com/connectors/halopsa) - [Site24x7 3](https://actionlake.com/connectors/site24x7) - [ilert 3](https://actionlake.com/connectors/ilert) - [Zabbix 3](https://actionlake.com/connectors/zabbix) - [Slack 2](https://actionlake.com/connectors/slack) - [Microsoft 365 Users 2](https://actionlake.com/connectors/microsoft-365-users) Browse - [All Observability & analytics connectors](https://actionlake.com/connectors/category/observability-and-analytics) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) actionlake is independent. It is not made or endorsed by Uptrends; the name is the vendor's own. Counts are from the Uptrends service file, version 1.0.0. ## Give your agent Uptrends today. [Connect Uptrends free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/uptrends More: https://actionlake.com/llms.txt