UpHeron

安装

选择你使用的 AI 应用，然后复制设置。

通过 2/3 项检查 · 你的提问会经过开发者的服务器（upheron.com） · ✓ 命令已检查 2026年11月13日

claude mcp add --transport http --scope user upheron https://upheron.com/mcp

{
  "mcpServers": {
    "upheron": {
      "url": "https://upheron.com/mcp"
    }
  }
}

{
  "servers": {
    "upheron": {
      "type": "http",
      "url": "https://upheron.com/mcp"
    }
  }
}

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档，检查于 2026年11月10日。

通过互联网连接，适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

工具名称和描述与服务器在 2026年11月12日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• check_website

  Checks whether a public website responds right now, from the monitoring service, without an account. Returns status, HTTP code and timings. Free; limited to a few checks a minute.

• get_account

  Plan and its monitor slots (standard in plan_monitors, premium in premium_monitors with their kinds), and the workspace's time zone (workspace.time_zone), which report days follow. Call this first to know whether the plan has room for another monitor.

• list_locations

  Location codes you can pass in a monitor's `locations`.

• list_monitors

  Every monitor with its current status (pending, up, down, degraded), and interval. Free.

• get_monitor

  One monitor with uptime for 24 hours, 7 days and 30 days, its last 90 days, incident totals, its latest results with errors, recent incidents, and route traces from failing locations (Pro and Business: each hop's loss, round trips and jitter over every round). Free.

• get_monitor_results

  A monitor's most recent check results, newest first. Older results may be merged: repeats checks with the same outcome up to last_checked_at. Free.

• get_uptime_history

  A monitor's daily uptime, kept for as long as it exists: checks, successful, failed and average response time per UTC day, oldest first. By default from the first check to today. Free.

• get_sla_report

  Business plans: availability against an SLA target for a range of days in the workspace's time zone (time_zone in get_account; by default this month), with the downtime budget used and left, incidents, MTTR, MTBF and the longest outage, per monitor (lowest availability first) and

• list_incidents

  Outages, newest first, with their status (open, acknowledged, resolved). Free.

• acknowledge_incident

  Marks an open incident as being handled: its repeat alerts and escalation stop. Everyone alerted still hears when it recovers. Free.

• list_escalation_policies

  Business plans: escalation policies, whose id a monitor's escalation_policy_id takes, and their steps. Free.

• list_on_call_schedules

  Business plans: on-call schedules with who is on call now, until when, and who is next. Free.

• get_incident

  One incident with its timeline (detected, acknowledged, comments, status page updates, recovered), root cause and post-mortem, and the status pages its updates go to with their subscriber counts. Free.

• post_incident_update

  Publishes an update on every published status page that shows the incident's monitor and in their RSS and Atom feeds, and on Pro plans emails those pages' subscribers. States: investigating, identified, monitoring, resolved. Write for the page's visitors. Free.

• comment_on_incident

  Adds a comment to the incident's timeline, seen only by the workspace (Pro plans). Use it to record what you found or did. Free.

• open_incident

  Opens an incident for what the checks cannot see: a slow service, a problem a customer reported. With a message it publishes the first update on the status pages that show its monitors (and emails their subscribers on Pro plans); alert pages the monitors' contacts once. It stays

• update_incident

  Changes the title status pages show (public_title) or the root cause (Pro plans) of any incident, and the title, severity and monitors of one opened by hand. Fields left out keep their value. Free.

• resolve_incident

  Resolves an incident opened with open_incident; the contacts it alerted hear so. A message is published as the last update on its status pages. Incidents opened by checks resolve with their checks. Free.

• write_postmortem

  Writes a resolved incident's post-mortem: summary, impact, root cause and follow-ups (one per line), on Pro plans. It stays in the workspace until published: true shows it under the incident on the status pages that show it and in their feeds; false takes it off. Publish only whe

• create_on_call_schedule

  Business plans: a rotation through notification contacts (list_notification_contacts), handing off daily or weekly at a time in a time zone. The first member is on call from now. Free.

• update_on_call_schedule

  Business plans. Fields left out keep their value; changing the members, rotation, handoff or time zone starts the rotation over. Free.

• delete_on_call_schedule

  Deletes a schedule no escalation policy uses. Free.

• add_on_call_override

  Business plans: puts a contact on call in a schedule from starts_at to ends_at (up to 90 days), instead of the rotation. Overrides may not overlap. Free.

• remove_on_call_override

  Removes an override from a schedule (its id is in the schedule's overrides). Free.

• create_escalation_policy

  Business plans: ordered steps, each alerting contacts and whoever is on call in schedules, then waiting for an acknowledgement before the next. Monitors use it with update_monitor's escalation_policy_id. Free.

• update_escalation_policy

  Business plans. Fields left out keep their value; steps replaces them all. Free.

• delete_escalation_policy

  Deletes a policy; its monitors go back to alerting their own contacts. Free.

• get_audit_log

  Who changed what in the workspace, newest first: people, API tokens and agents, with the changed fields and IP (Business plan). Filter by resource_type (monitor, alert_channel, status_page, member, api_token…), action (monitor.updated, or a prefix like monitor.), from and to (YYY

• create_monitor

  Creates a monitor in a free slot of the workspace's plan. Premium monitors (multi-step transactions and code repositories) have slots of their own, on Pro and Business only. When every slot is in use the call fails with monitor_limit_reached: the user can upgrade at https://upher

• update_monitor

  Changes a monitor's settings, within the plan's interval and location limits. Free.

• pause_monitor

  Stops checking a monitor. Free.

• resume_monitor

  Starts checking a paused monitor again. Free.

• delete_monitor

  Deletes a monitor and its history. Frees its plan slot.

• add_notification_contact

  Adds an email address, chat channel, paging service, Jira project, webhook or phone number to alert on outages and recoveries. Email contacts must open a confirmation link before they receive alerts. A phone number texts or calls through the user's own account with a provider, on

• confirm_notification_contact

  Confirms an sms or voice contact, added before they were retired, with the 6-digit code it was texted or told in a call. The code works for 24 hours and 5 tries. Ask the phone's owner for it; never guess.

• list_notification_contacts

  Contacts that receive alerts, whether each is confirmed, and for phone contacts their latest text or call and whether it was delivered.

• test_notification_contact

  Sends a contact a test alert, at most 5 a minute for a workspace. For a phone contact it is a real text or call through the user's account, which counts toward its 6 texts or 3 calls an hour; an error says in words what the provider refused (credentials, a trial account's unverif

• get_vulnerabilities

  For an http or api monitor with vulnerability_alerts on: the vulnerabilities and unsupported releases found in the website's software, actively exploited and most severe first, with the version that fixes each, and the software they were matched on (found by scanning the website,

• import_software

  Tells the monitor what software the website and its server run, so their vulnerabilities are checked. Send a file's contents (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lock, mix.lock, composer.json/.lock, requirements.txt, Pipfile.lock, poetry.lock, Gemfile.

• add_software

  Adds one piece of software the website runs, by name (Debian, nginx, WordPress, Next.js…), package (npm:lodash, composer:vendor/package, pypi:django, wp-plugin:slug) or NVD product (cpe:vendor:product), with its version if known. Replaces a detected or imported entry for the same

• remove_software

  Removes an entry from get_vulnerabilities' software list. Software the scan found is ignored instead, so the next scan does not add it back. Free.

• mark_vulnerability_fixed

  Records that the software behind a finding from get_vulnerabilities was upgraded: to `version`, or by default to the first version that fixes it (the finding's fix_version). The monitor is checked again; findings that no longer apply disappear, and one that still applies stays, m

• get_ports

  For a monitor with port_scan on (Business plans): which of its host's addresses are verified and how to verify the rest (a file each address serves, or reverse DNS under the host with a TXT record), the ports the last weekly scan found open, flagged where the service usually shou

• verify_host

  Looks for the proof of each of the host's addresses from get_ports: the file served at the address, or its reverse DNS (PTR) under the host resolving back to it with the TXT record in place. The TXT record alone proves no address. The proof must stay in place, since every scan ch

• scan_ports

  Scans the verified host's common TCP ports now instead of waiting for the weekly scan, at most once an hour. Takes a minute or two; then read get_ports. Free.

• scan_website_software

  Scans the monitor's website for the software it runs and checks it against the vulnerability sources now, instead of waiting for the next scan. Takes up to a minute; then read get_vulnerabilities. Free.

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月14日

• ! 注意

  作者与仓库一致

  注册中心没有列出源代码仓库，因此无法将发布者（upheron.com）与代码对应起来

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 792 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 46 个工具描述，未发现针对 AI 的隐藏指令

用户评价

还没有评价

用 Google 登录后写评价

与“网络安全”中的其他服务器比较i

• 星标数多于此分类中其他 1059 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 1059 个服务器的 94% 更新
• 基础检查结果等于或优于此分类中其他 1059 个服务器的 46%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

同类别的其他选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Robin: AI-Powered Dark Web OSINT

Dark web OSINT over Tor: search onion engines, scrape pages, report with your own model.

作者：apurvsinghgautam·正在增长·★ 7978·42天前更新

在你的电脑上运行

安装

HOL Guard

Local-first AI agent security evidence and approval workflows through HOL Guard's stdio MCP server.

作者：hashgraph-online·广泛使用·↓ 7083/周·★ 1102·9天前更新

在你的电脑上运行

安装

SonarQube MCP Server

Analyze code quality and security with SonarQube Server or Cloud directly in AI assistants.

作者：SonarSource·正在增长·★ 686·3天前更新

在你的电脑上运行

安装

作者的 README

仓库中没有找到 README