Skip to content

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.

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
  • 236actionsin one signed file
  • 106readlook, never change
  • 90writecreate and update
  • 40wait for a yesdestructive, 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.

    • usernameUptrends API account username (the `UserName` POST /Register returned; not your login email)
    • passwordUptrends 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 callcheck { 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
usernamepassword
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 2026api.uptrends.comuptrends.com
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.

  • 106readlook, never change
  • 90writecreate and update
  • 40destructivewait 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.

ActionWhat it doesEffectSame name in
uptrends.operator.get_all_operatorsGets a list of all operatorsGets a list of all operators.readidentity.user.list474 connectors
uptrends.operator_group.get_all_operator_groupsGets all operator groupsGets all operator groups.readidentity.group.list262 connectors
uptrends.monitor.get_monitorsReturns the definition of all monitors available in the accountReturns the definition of all monitors available in the account.readmonitoring.monitor.list32 connectors
uptrends.operator.create_operatorCreates a new operatorCreates a new operator.writeidentity.user.create262 connectors
uptrends.operator_group.create_operator_groupCreates a new operator groupCreates a new operator group.writeidentity.group.create205 connectors
uptrends.monitor.post_monitorCreates a new monitorCreates a new monitor.writemonitoring.monitor.create27 connectors
uptrends.operator.delete_operatorDeletes an existing operatorDeletes an existing operator.destructiveidentity.user.delete253 connectors
uptrends.alert.get_monitor_alertsReturns alerts for a specific monitorReturns alerts for a specific monitor.readmonitoring.alert.list51 connectors
uptrends.sla.get_slasGets a list of all SLA definitionsGets a list of all SLA definitions.readservice.sla.list12 connectors
uptrends.integration.get_all_integrationsGets a list of all integrationsGets a list of all integrations.readmonitoring.notification_channel.list18 connectors
uptrends.dashboard.get_all_dashboardsReturns data for all dashboardsReturns data for all dashboards.readmonitoring.dashboard.list15 connectors
uptrends.alert_definition.create_alert_definitionCreates a new alert definitionCreates a new alert definition.writemonitoring.notification_rule.create11 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. Readread

    Who has access in Uptrends? List every user and their role.

    callsuptrends.operator.get_all_operators

  2. Writewrite

    Creates a new operator in Uptrends. Show me exactly what you will send before you save it.

    callsuptrends.operator.create_operator

Governance for Uptrends

Destructive actions wait for a yes.

40 Uptrends actions are destructive. The first 10:

  • Deletes an existing operatoruptrends.operator.delete_operator
  • Deletes the specified operator groupuptrends.operator_group.delete_operator_group
  • Deletes the specified monitoruptrends.monitor.delete_monitor
  • Delete the specified dashboarduptrends.dashboard.delete_dashboard
  • Deletes an existing alert definitionuptrends.alert_definition.delete_alert_definition
  • Deletes an existing api useruptrends.api_user.delete_api_user
  • Deletes the specified SLAuptrends.sla.delete_sla
  • Deletes the specified vault itemuptrends.vault.delete_vault_item
  • Delete the specified scheduled reportuptrends.scheduled_report.delete_specified_scheduled_report
  • Deletes the definition of the specified public status pageuptrends.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.

douptrends.operator.delete_operatorconfirm_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: "[email protected]" },    { match: "uptrends.operator_group.delete_operator_group", approver: "[email protected]" },    { match: "uptrends.monitor.delete_monitor", approver: "[email protected]" }  ]}
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.

  • 1upstream call per actionall 236 Uptrends actions
  • 236actions pageeach page of a long list is one call
  • 85reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Uptrends action.

236 actions by area: the id your agent calls, what it does, and its effect.

Alert definition29
  • uptrends.alert_definition.add_integration_to_escalation_levelAdds an integration to a specified escalation levelwrite
  • uptrends.alert_definition.add_monitor_group_to_alert_definitionAdds a monitor group to the specified alert definitionwrite
  • uptrends.alert_definition.add_monitor_to_alert_definitionAdds a monitor to the specified alert definitionwrite
  • uptrends.alert_definition.add_operator_group_to_escalation_levelAdds an operator group to the specified escalation levelwrite
  • uptrends.alert_definition.add_operator_to_escalation_levelAdds an operator to the specified escalation levelwrite
  • uptrends.alert_definition.create_alert_definitionCreates a new alert definitionwrite
  • uptrends.alert_definition.create_authorization_for_alert_definitionCreate authorizations for alert definition If the wanted authorizations requires other authorizations, these will be added as wellwrite
  • uptrends.alert_definition.delete_alert_definitionDeletes an existing alert definitiondestructive
  • uptrends.alert_definition.delete_authorization_for_alert_definitionDelete alert definition authorization for alert definitiondestructive
  • uptrends.alert_definition.get_all_alert_definitionsGets a list of all alert definitionsread
  • uptrends.alert_definition.get_all_escalation_level_integrationsGets all integrations for a specified escalation levelread
  • uptrends.alert_definition.get_all_escalation_levelsGets all escalation level information for the specified alert definitionread
  • uptrends.alert_definition.get_all_membersGets a list of all monitor and monitor group guids for the specified alert definitionread
  • uptrends.alert_definition.get_authorizations_of_alert_definitionGet authorizations of alert definitionread
  • uptrends.alert_definition.get_escalation_levelGets the escalation level information of the specified alert definitionread
  • uptrends.alert_definition.get_escalation_level_integrationGets a single integration for a specified escalation levelread
  • uptrends.alert_definition.get_escalation_level_operatorGets the operator and operator group guids for the specified escalation levelread
  • uptrends.alert_definition.get_specified_alert_definitionsGets the specified alert definitionread
  • uptrends.alert_definition.patch_alert_definitionPartially updates the definition for the specified alert definitionwrite
  • uptrends.alert_definition.patch_alert_definition_escalationPartially updates the escalation level for the specified alert definitionwrite
  • uptrends.alert_definition.put_alert_definitionUpdates the definition for the specified alert definitionwrite
  • uptrends.alert_definition.put_alert_definition_escalationUpdates the escalation level for the specified alert definitionwrite
  • uptrends.alert_definition.remove_integration_from_escalation_levelRemoves an integration from a specified escalation leveldestructive
  • uptrends.alert_definition.remove_monitor_from_alert_definitionRemoves a monitor for the specified alert definitiondestructive
  • uptrends.alert_definition.remove_monitor_group_from_alert_definitionRemoves a monitor group for the specified alert definitiondestructive
  • uptrends.alert_definition.remove_operator_from_escalation_levelRemoves an operator for the specified escalation leveldestructive
  • uptrends.alert_definition.remove_operator_group_from_escalation_levelRemoves an operator group for the specified escalation leveldestructive
  • uptrends.alert_definition.update_integration_for_escalation_with_patchPartially updates an integration for a specified escalation levelwrite
  • uptrends.alert_definition.update_integration_for_escalation_with_putUpdates an integration for a specified escalation levelwrite
Private location20
  • uptrends.private_location.create_authorization_for_private_locationCreate private location authorizations for private location If the wanted authorizations requires other authorizations, these will be added as wellwrite
  • uptrends.private_location.create_private_location_checkpointCreate new checkpoint for the specified private locationwrite
  • uptrends.private_location.create_private_location_checkpoint_for_monitor_groupCreate new checkpoint for the specified private locationwrite
  • uptrends.private_location.delete_authorization_for_private_locationDelete private location authorization for private locationdestructive
  • uptrends.private_location.delete_private_locationDeletes a private locationdestructive
  • uptrends.private_location.delete_private_location_checkpointDelete checkpoint of the specified private locationdestructive
  • uptrends.private_location.get_authorizations_of_private_locationGet private location authorizations of private locationread
  • uptrends.private_location.get_private_locationReturns the definition of the specified private locationread
  • uptrends.private_location.get_private_location_checkpointGets a list of all checkpoint of the specified private locationread
  • uptrends.private_location.get_private_location_checkpointsGets a list of all checkpoint of the specified private locationread
  • uptrends.private_location.get_private_location_healthReturns the health info of the specified private locationread
  • uptrends.private_location.get_private_locationsReturns the definition of all private locations in the accountread
  • uptrends.private_location.get_specified_private_checkpoint_healthReturns the status of the specified private checkpointsread
  • uptrends.private_location.patch_private_locationPartially updates existing private locationwrite
  • uptrends.private_location.patch_private_location_checkpointPartially updates existing private location checkpointwrite
  • uptrends.private_location.post_private_locationCreates a new private locationwrite
  • uptrends.private_location.post_private_location_with_monitor_groupCreates a new private location for the specified monitor groupwrite
  • uptrends.private_location.private_location_healthReturns the status of the private checkpoints in the given locationread
  • uptrends.private_location.put_private_locationUpdates existing private locationwrite
  • uptrends.private_location.put_private_location_checkpointUpdates existing private location checkpointwrite
Monitor18
  • uptrends.monitor.cleanup_maintenance_periodsClears out all one-time maintenance periods for the specified monitor older than the specified datedestructive
  • uptrends.monitor.clone_monitorCreates a clone (duplicate) of the specified monitorwrite
  • uptrends.monitor.create_authorization_for_monitorCreate monitor authorizations for monitor If the wanted authorizations requires other authorizations, these will be added as wellwrite
  • uptrends.monitor.create_maintenance_period_for_monitorSaves the new maintenance period provided for the specified monitorwrite
  • uptrends.monitor.delete_authorization_for_monitorDelete monitor authorization for monitordestructive
  • uptrends.monitor.delete_maintenance_period_from_monitorDeletes the specified maintenance period from the specified monitordestructive
  • uptrends.monitor.delete_monitorDeletes the specified monitordestructive
  • uptrends.monitor.get_all_maintenance_periods_for_monitorFinds all maintenance periods for a monitorread
  • uptrends.monitor.get_authorizations_of_monitorGet monitor authorizations of monitorread
  • uptrends.monitor.get_monitorReturns the definition of the specified monitorread
  • uptrends.monitor.get_monitor_groupsReturns the Guid of each monitor group where the specified monitor is a member ofread
  • uptrends.monitor.get_monitorsReturns the definition of all monitors available in the accountread
  • uptrends.monitor.get_monitors_by_monitor_groupReturns the definition of all monitors available in the account that are a member of the specified monitor groupread
  • uptrends.monitor.patch_monitorPartially updates the definition of the specified monitorwrite
  • uptrends.monitor.post_monitorCreates a new monitorwrite
  • uptrends.monitor.post_monitor_and_add_to_monitor_groupCreates a new monitor and adds it to specified monitor groupwrite
  • uptrends.monitor.put_monitorUpdates the definition of the specified monitorwrite
  • uptrends.monitor.update_maintenance_period_for_monitorUpdates the specified maintenance schedule for the specified monitorwrite
Operator17
  • uptrends.operator.add_duty_period_for_operatorAdds a duty schedule to the specified operatorwrite
  • uptrends.operator.create_operatorCreates a new operatorwrite
  • uptrends.operator.create_operator_and_add_to_operator_groupCreates a new operator and adds it to specified operator groupwrite
  • uptrends.operator.delete_authorization_for_operatorRemoves the specified authorization of this operatordestructive
  • uptrends.operator.delete_duty_schedule_from_operatorDeletes the specified duty schedule of the specified operatordestructive
  • uptrends.operator.delete_operatorDeletes an existing operatordestructive
  • uptrends.operator.get_all_operatorsGets a list of all operatorsread
  • uptrends.operator.get_authorizations_for_operatorGets all authorizations for the specified operatorread
  • uptrends.operator.get_duty_schedule_for_operatorGets the duty schedules for an specified operatorread
  • uptrends.operator.get_newsletter_subscriptionGets the newsletter subscription valuesread
  • uptrends.operator.get_operatorGets the details of the operator with the provided OperatorGuidread
  • uptrends.operator.get_operator_groups_for_operatorGets a list of all operator groups for the specified operatorread
  • uptrends.operator.post_authorization_for_operatorAssigns the specified authorization to this operatorwrite
  • uptrends.operator.update_duty_period_for_operatorUpdates the specified duty schedule of the specified operatorwrite
  • uptrends.operator.update_newsletter_subscriptionUpdate the newsletter subscription values for the specified operatorwrite
  • uptrends.operator.update_operatorUpdates an existing operatorwrite
  • uptrends.operator.update_operator_with_patchUpdates an existing operatorwrite
Monitor group16
  • uptrends.monitor_group.add_maintenance_period_to_all_membersAdds the provided maintenance period to all monitors in the group specifiedwrite
  • uptrends.monitor_group.add_monitor_to_monitor_groupAdds the specified monitor to the monitor groupwrite
  • uptrends.monitor_group.create_authorization_for_monitor_groupCreate monitor authorizations for monitor group If the wanted authorizations requires other authorizations, these will be added as wellwrite
  • uptrends.monitor_group.create_monitor_groupCreates a new monitor groupwrite
  • uptrends.monitor_group.delete_authorization_for_monitor_groupDelete monitor authorization for monitor groupdestructive
  • uptrends.monitor_group.delete_monitor_groupDeletes the specified monitor groupdestructive
  • uptrends.monitor_group.get_all_monitor_groupsGets all monitor groupsread
  • uptrends.monitor_group.get_authorizations_of_monitor_groupGet monitor authorizations of monitor groupread
  • uptrends.monitor_group.get_monitor_groupGets the details of a monitor groupread
  • uptrends.monitor_group.get_monitor_group_membersGets a list of all members of a monitor groupread
  • uptrends.monitor_group.remove_monitor_from_monitor_groupRemoves the specified monitor from the monitor groupdestructive
  • uptrends.monitor_group.start_all_monitor_alerts_in_groupStarts alerting for all monitors that are a member of the monitor group specified by the monitor group GUIDwrite
  • uptrends.monitor_group.start_all_monitors_in_groupStarts all monitors that are a member of the monitor group specified by the monitor group GUIDwrite
  • uptrends.monitor_group.stop_all_monitor_alerts_in_groupStops alerting for all monitors that are a member of the monitor group specified by the monitor group GUIDwrite
  • uptrends.monitor_group.stop_all_monitors_in_groupStops all monitors that are a member of the monitor group specified by the monitor group GUIDwrite
  • uptrends.monitor_group.update_monitor_groupUpdates the monitor group with the Guid specifiedwrite
Monitor result export settings16
  • uptrends.monitor_result_export_settings.create_connection_settingsCreates a new OpenTelemetry connection settings configurationwrite
  • uptrends.monitor_result_export_settings.create_rule_setCreates a new OpenTelemetry rule set configurationwrite
  • uptrends.monitor_result_export_settings.create_settingsCreates a new monitor result export settings configurationwrite
  • uptrends.monitor_result_export_settings.delete_connection_settingsDeletes an OpenTelemetry connection settings configurationdestructive
  • uptrends.monitor_result_export_settings.delete_rule_setDeletes an OpenTelemetry rule set configurationdestructive
  • uptrends.monitor_result_export_settings.delete_settingsDeletes a monitor result export settings configurationdestructive
  • uptrends.monitor_result_export_settings.get_connection_settingsReturns a specific OpenTelemetry connection settings configurationread
  • uptrends.monitor_result_export_settings.get_connection_settings_allReturns all OpenTelemetry connection settingsread
  • uptrends.monitor_result_export_settings.get_rule_setsReturns a specific OpenTelemetry rule set configurationread
  • uptrends.monitor_result_export_settings.get_rule_sets_allReturns all OpenTelemetry rule setsread
  • uptrends.monitor_result_export_settings.get_settingsReturns a specific monitor result export settings configurationread
  • uptrends.monitor_result_export_settings.get_settings_allReturns all monitor result settings for the current operatorread
  • uptrends.monitor_result_export_settings.get_statusReturns the status of the monitor result export settings configurationread
  • uptrends.monitor_result_export_settings.update_connection_settingsUpdates an existing OpenTelemetry connection settings configurationwrite
  • uptrends.monitor_result_export_settings.update_rule_setUpdates an existing OpenTelemetry rule set configurationwrite
  • uptrends.monitor_result_export_settings.update_settingsUpdates an existing monitor result export settings configurationwrite
Operator group15
  • uptrends.operator_group.add_duty_schedule_to_all_membersAdds the provided duty schedule to all operators in the group specifiedwrite
  • uptrends.operator_group.add_operator_to_operator_groupAdds the specified operator to the operator groupwrite
  • uptrends.operator_group.all_operators_in_group_off_dutySet the OnDuty flag to off for all operators that are a member of the operator group specified by the operator group GUIDwrite
  • uptrends.operator_group.all_operators_in_group_on_dutySet the OnDuty flag to on for all operators that are a member of the operator group specified by the operator group GUIDwrite
  • uptrends.operator_group.create_operator_groupCreates a new operator groupwrite
  • uptrends.operator_group.delete_authorization_for_operator_groupRemoves the specified authorization of the operator groupdestructive
  • uptrends.operator_group.delete_operator_groupDeletes the specified operator groupdestructive
  • uptrends.operator_group.get_all_operator_groupsGets all operator groupsread
  • uptrends.operator_group.get_authorizations_for_operator_groupGets all authorizations for the specified operator groupread
  • uptrends.operator_group.get_operator_groupGets the details of an operator groupread
  • uptrends.operator_group.get_operator_group_by_external_idGets the details of an operator groupread
  • uptrends.operator_group.get_operator_group_membersGets a list of all members of an operator groupread
  • uptrends.operator_group.post_authorization_for_operator_groupAssigns the specified authorization to the operator groupwrite
  • uptrends.operator_group.remove_operator_from_operator_groupRemoves the specified operator from the operator groupdestructive
  • uptrends.operator_group.update_operator_groupUpdates the operator group with the Guid specifiedwrite
Monitor check14
  • uptrends.monitor_check.get_account_monitor_checksReturns all monitor check dataread
  • uptrends.monitor_check.get_concurrent_monitor_partial_checksGets all partial checks for a concurrent monitor checkread
  • uptrends.monitor_check.get_console_log_infoReturns console log information for a monitor checkread
  • uptrends.monitor_check.get_filmstripGets the filmstrip for a specified monitor checkread
  • uptrends.monitor_check.get_http_detailsReturns HTTP details for a monitor checkread
  • uptrends.monitor_check.get_monitor_checkReturns monitor check data for a specific monitorread
  • uptrends.monitor_check.get_monitor_group_dataReturns monitor check data for a specific monitor groupread
  • uptrends.monitor_check.get_multistep_detailsReturns Multi-Step API details for a monitor checkread
  • uptrends.monitor_check.get_page_source_infoReturns page source information for a monitor checkread
  • uptrends.monitor_check.get_postman_detailsReturns Postman API details for a monitor checkread
  • uptrends.monitor_check.get_screenshotsGets a specific screenshot for a specified monitor checkread
  • uptrends.monitor_check.get_single_monitor_checkReturns a single monitor checkread
  • uptrends.monitor_check.get_transaction_detailsReturns transaction step details for a monitor checkread
  • uptrends.monitor_check.get_waterfall_infoReturns waterfall information for a monitor checkread
Vault14
  • uptrends.vault.create_authorization_for_vault_sectionCreates a new authorization for the specified vault sectionwrite
  • uptrends.vault.create_new_vault_itemCreates a new vault itemwrite
  • uptrends.vault.create_new_vault_sectionCreates a new vault sectionwrite
  • uptrends.vault.delete_authorization_for_vault_sectionDeletes the specified authorization for the specified vault sectiondestructive
  • uptrends.vault.delete_vault_itemDeletes the specified vault itemdestructive
  • uptrends.vault.delete_vault_sectionDeletes the specified vault sectiondestructive
  • uptrends.vault.get_all_vault_itemsReturns all vault itemsread
  • uptrends.vault.get_all_vault_sectionsReturns all vault sectionsread
  • uptrends.vault.get_authorizations_for_vault_sectionReturns all authorizations for the specified vault sectionread
  • uptrends.vault.get_vault_itemReturns the specified vault itemread
  • uptrends.vault.get_vault_sectionReturns the specified vault sectionread
  • uptrends.vault.partially_update_vault_itemPartially updates the specified vault itemwrite
  • uptrends.vault.update_vault_itemUpdates the specified vault itemwrite
  • uptrends.vault.update_vault_sectionUpdates the specified vault sectionwrite
Sla12
  • uptrends.sla.create_slaCreates a new SLAwrite
  • uptrends.sla.delete_exclusion_periodDeletes the specified exclusion period for the specified SLAdestructive
  • uptrends.sla.delete_slaDeletes the specified SLAdestructive
  • uptrends.sla.get_exclusion_periodGets the specified exclusion period for the specified SLAread
  • uptrends.sla.get_exclusion_periodsGets a list of all exclusion periods for the specified SLAread
  • uptrends.sla.get_slaGets the specified SLA definitionread
  • uptrends.sla.get_slasGets a list of all SLA definitionsread
  • uptrends.sla.patch_exclusion_periodPartially updates the specified exclusion period for the specified SLAwrite
  • uptrends.sla.patch_slaPartially updates the definition of the specified SLAwrite
  • uptrends.sla.post_exclusion_periodCreates a new exclusion period for the specified SLAwrite
  • uptrends.sla.put_exclusion_periodUpdates the specified exclusion period for the specified SLAwrite
  • uptrends.sla.put_slaUpdates the definition of the specified SLAwrite
Integration11
  • uptrends.integration.create_authorization_for_integrationCreate authorizations for integration If the wanted authorizations requires other authorizations, these will be added as wellwrite
  • uptrends.integration.create_custom_integrationCreates a new custom integrationwrite
  • uptrends.integration.delete_authorization_for_integrationDelete integration authorization for integrationdestructive
  • uptrends.integration.delete_custom_integrationDeletes the specified custom integrationdestructive
  • uptrends.integration.delete_integrationDeletes the specified integration. Not all integration types can be deleteddestructive
  • uptrends.integration.get_all_custom_integrationGets a list of all custom integrationsread
  • uptrends.integration.get_all_integrationsGets a list of all integrationsread
  • uptrends.integration.get_authorizations_of_integrationGet authorizations of integrationread
  • uptrends.integration.get_custom_integrationReturns the details of the specified custom integrationread
  • uptrends.integration.get_integrationGets the specified integrationread
  • uptrends.integration.update_custom_integrationUpdates the specified custom integrationwrite
Public status page9
  • uptrends.public_status_page.add_authorization_to_public_status_pageCreates a new authorization for the specified public status pagewrite
  • uptrends.public_status_page.delete_public_status_pageDeletes the definition of the specified public status pagedestructive
  • uptrends.public_status_page.get_authorizations_for_public_status_pageReturns all authorizations for the specified public status pageread
  • uptrends.public_status_page.get_public_status_pageReturns the definition of the specified public status pageread
  • uptrends.public_status_page.get_public_status_pagesReturns the definition of all public status pages available in the accountread
  • uptrends.public_status_page.patch_public_status_pagePartially updates the definition of the specified public status pagewrite
  • uptrends.public_status_page.post_public_status_pageCreates a new public status pagewrite
  • uptrends.public_status_page.put_public_status_pageUpdates the definition of the specified public status pagewrite
  • uptrends.public_status_page.remove_authorization_from_public_status_pageRemoves an authorization from a public status pagedestructive
Checkpoint8
  • uptrends.checkpoint.get_all_checkpoint_regionsReturns all the checkpoint regionsread
  • uptrends.checkpoint.get_all_checkpointsReturns all the checkpoints that are not deletedread
  • uptrends.checkpoint.get_all_server_ipv4_addressesAnonymous call that returns all the IPv4 addresses of all the checkpoint serversread
  • uptrends.checkpoint.get_all_server_ipv6_addressesAnonymous call that returns all the IPv6 addresses of all the checkpoint serversread
  • uptrends.checkpoint.get_checkpointReturns the specified checkpoint, deleted or notread
  • uptrends.checkpoint.get_checkpoint_region_checkpointsReturns the checkpoints for the specified checkpoint regionread
  • uptrends.checkpoint.get_serverReturns the requested checkpoint serverread
  • uptrends.checkpoint.get_specified_checkpoint_regionReturns the specified checkpoint regionread
Rum8
  • uptrends.rum.delete_rum_websiteDeletes the specified RUM websitedestructive
  • uptrends.rum.get_rum_metrics_for_all_websitesReturns all metrics of all RUM websitesread
  • uptrends.rum.get_rum_websiteReturns the definition of the specified RUM website, including the RUM insertion scriptread
  • uptrends.rum.get_rum_website_metricsReturns all metrics of the specified RUM websiteread
  • uptrends.rum.get_rum_websitesReturns the definition of all RUM websites available in the accountread
  • uptrends.rum.patch_rum_websitePartially updates the definition of the specified RUM websitewrite
  • uptrends.rum.post_rum_websiteCreates a new RUM websitewrite
  • uptrends.rum.put_rum_websiteUpdates the definition of the specified RUM websitewrite
API user6
  • uptrends.api_user.create_api_userCreates a new api userwrite
  • uptrends.api_user.delete_api_userDeletes an existing api userdestructive
  • uptrends.api_user.get_all_api_usersGets a list of all api usersread
  • uptrends.api_user.get_all_api_users_for_operatorGets a list of all api users of the specified operatorread
  • uptrends.api_user.get_api_userGets the details of the api user with the provided api userread
  • uptrends.api_user.update_api_userUpdates an existing api userwrite
Dashboard6
  • uptrends.dashboard.clone_dashboardClone the specified dashboardwrite
  • uptrends.dashboard.delete_dashboardDelete the specified dashboarddestructive
  • uptrends.dashboard.get_all_dashboardsReturns data for all dashboardsread
  • uptrends.dashboard.get_one_dashboardReturns data for the specified dashboardread
  • uptrends.dashboard.partially_update_dashboardPartially update the specified dashboardwrite
  • uptrends.dashboard.update_dashboardUpdate the specified dashboardwrite
Scheduled report6
  • uptrends.scheduled_report.create_scheduled_reportCreates a new scheduled reportwrite
  • uptrends.scheduled_report.delete_specified_scheduled_reportDelete the specified scheduled reportdestructive
  • uptrends.scheduled_report.get_all_scheduled_reportsReturns data for all scheduled reportsread
  • uptrends.scheduled_report.get_specified_scheduled_reportReturns data for the specified scheduled reportread
  • uptrends.scheduled_report.partially_update_scheduled_reportPartially update the specified scheduled reportwrite
  • uptrends.scheduled_report.update_scheduled_reportUpdate the specified scheduled reportwrite
Account2
  • uptrends.account.get_account_statisticsReturns the account statisticsread
  • uptrends.account.get_settingsReturns account general settingsread
Alert2
  • uptrends.alert.get_monitor_alertsReturns alerts for a specific monitorread
  • uptrends.alert.get_monitor_group_alertsReturns alerts for a specific monitor groupread
Statistics2
  • uptrends.statistics.get_monitor_group_statisticsGets the monitor group statisticsread
  • uptrends.statistics.get_monitor_statisticsGets the monitor statisticsread
Status2
  • uptrends.status.get_monitor_group_statusGets a list of all monitor group status dataread
  • uptrends.status.get_monitor_statusGets all monitor status dataread
Timezone2
  • uptrends.timezone.get_all_timezonesGets all timezones availableread
  • uptrends.timezone.get_timezone_by_idGets the timezone with the specified Idread
Outgoing phone number1
  • uptrends.outgoing_phone_number.get_all_outgoing_phone_numbersGets a list of all outgoing phone numbers availableread

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.

Give your agent Uptrends today.

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.