HostTracker MCPサーバー
コミット 2026年8月30日AIアシスタントをHostTrackerに接続し、ウェブサイトの稼働監視、グローバルチェックの実行、インシデント対応を対話形式で行えます。
別名 HostTracker/mcp, mcp
- スター
- 1
- ツール
- —
- ダウンロード数(30日間)
- —
- 最新バージョン
- 2.1.0
- 最終コミット
- 2026年8月30日
- ライセンス
- MIT
HostTracker MCPとは
HostTrackerはMCPサーバーです。 AIアシスタントをHostTrackerに接続し、ウェブサイトの稼働監視、グローバルチェックの実行、インシデント対応を対話形式で行えます。.
プロジェクトのREADMEから生成された概要
HostTracker MCP server について
HostTrackerを使用すると、Model Context Protocolを通じてAIアシスタントをウェブサイト監視アカウントに接続できます。このサーバーにより、稼働監視の対話的な管理が可能になり、世界300以上の拠点からのライブチェック、モニターの管理、サービスインシデントへの対応が行えます。自然言語を使用して監視インフラを操作したい開発者やサイトリライアビリティエンジニア向けに設計されています。
接続には、簡単なサインイン体験を提供するOAuth 2.1を使用したホスト済みエンドポイント、またはBearer tokenの提供が利用できます。このサーバーは、Claude Desktop、Claude Code、Cursor、VS Codeを含むさまざまなクライアントをサポートしています。連絡先、Webhook、メンテナンスウィンドウ、公開ステータスページを管理するための幅広いツールを提供します。より高いセキュリティやローカル制御が必要な場合は、Dockerまたは.NET SDKを使用してサーバーを独立して実行できます。
できること
- 1グローバルな稼働チェックの実行特定のURLが世界のさまざまな場所からアクセス可能かどうかをアシスタントに確認させます。
- 2監視スケジュールの管理アップデート中の誤アラートを防ぐために、特定のモニターを一時停止または再開するようAIに指示します。
- 3インシデント対応のコミュニケーションサービス中断が発生した際に、アシスタントを使用して公開ステータスページに更新情報を投稿します。
- 4メンテナンスウィンドウの設定不要なアラートが発生しないよう、計画的な作業期間をスケジュールするようAIに指示します。
プロジェクトの README から作成されています。すべてのユースケースは、その引用と照らし合わせて確認されています。
HostTracker MCPのインストール方法
フォーマット検証日 2026年11月10日Cursor に追加Gooseに追加Claude CodeにHostTracker MCPをインストール
$ claude mcp add --transport http mcp https://mcp.host-tracker.com/mcpCursorにHostTracker MCPをインストール
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://mcp.host-tracker.com/mcp"
}
}
}VS CodeにHostTracker MCPをインストール
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "http",
"url": "https://mcp.host-tracker.com/mcp"
}
}
}VS Code CLIにHostTracker MCPをインストール
$ code --add-mcp '{"name":"mcp","type":"http","url":"https://mcp.host-tracker.com/mcp"}'CodexにHostTracker MCPをインストール
$ codex mcp add mcp --url https://mcp.host-tracker.com/mcpCodex config.tomlにHostTracker MCPをインストール
~/.codex/config.toml
[mcp_servers.mcp] url = "https://mcp.host-tracker.com/mcp"
Gemini CLIにHostTracker MCPをインストール
$ gemini mcp add -s user --transport http mcp https://mcp.host-tracker.com/mcpGemini settings.jsonにHostTracker MCPをインストール
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"url": "https://mcp.host-tracker.com/mcp",
"type": "http"
}
}
}設定
HT_AUTHHT_TOKEN
| 名前 | 説明 | 種類 |
|---|---|---|
| HT_AUTH | — | |
| HT_TOKEN | — |
自動チェック
実行日 2026年11月15日完全なレポート →まだ検証されていません。サーバーには80点のスコア、重大な問題がないこと、および検証に必要な十分なデータが必要です。 チェックの仕組み · 点数を上げるための改善点
- ソースリポジトリがリンクされており、アクセス可能hosttracker/mcp is public and reachablegithub.com/hosttracker/mcp ↗合格
- パッケージがこのリポジトリをソースとして指定未チェック
- ビルドの来歴 (Sigstore 証明)未チェック
- オープンソースライセンス (OSI)MITspdx.org/licenses/MIT.html ↗合格
- 過去1年以内にコミットまたはリリースありLast commit or release 2026-08-30github.com/hosttracker/mcp ↗合格
- OpenSSF Scorecard未チェック
- パッケージ名が有名なパッケージに酷似していない未チェック
- パッケージおよびその依存関係に重大な勧告なし未チェック
- モデルへの隠れた指示がない0 tool descriptions and the README read; no override phrases, credential paths or hidden characters合格
- 破壊的なツールがラベル付けされている未チェック
- リモートエンドポイントが MCP ハンドシェイクに応答HTTPS endpoint answered 401 (sign-in required)合格
README
GitHubで見るHostTracker MCP server
Connect an AI assistant to HostTracker over the Model Context Protocol and let it operate your monitoring account in conversation: run a live check from 300+ global locations, see what is down, create or pause a monitor, schedule a maintenance window, review incidents, manage who gets alerted, wire a webhook, publish a status page update.
Endpoint https://mcp.host-tracker.com/mcp
Transport streamable HTTP
Auth OAuth 2.1 (sign in when your client asks) - or Authorization: Bearer <HostTracker API token>
This repository is the public face of that hosted server: the connection metadata
(server.json), the per-client setup guide (CLIENT.md), and the security policy
(SECURITY.md) - and, since 2.0.0, the server's own source code in src/, so you can read
exactly what runs behind the endpoint or run a copy yourself (see "Run it yourself" below).
Connect in two minutes
With OAuth (recommended - Claude.ai, Claude Desktop, Claude Code, ChatGPT and any client with an OAuth-capable connector dialog):
- Add the endpoint
https://mcp.host-tracker.com/mcpas a connector in your client. - Sign in and approve. The client opens HostTracker's sign-in page, then a consent card listing the permissions it asks for (by default: run checks + read monitors). Press Approve. No token ever appears.
- Ask in plain language: "is example.com up right now, checked from Europe and Asia?", "which of my monitors are down?", "pause the staging monitor until tomorrow".
Claude Code
With OAuth (no token needed):
claude mcp add --transport http hosttracker https://mcp.host-tracker.com/mcp
# then, inside Claude Code: /mcp -> hosttracker -> Authenticate (opens the sign-in + consent page)
Or with a bearer token in the header:
.mcp.json in your project (or ~/.claude.json for a user-wide connector):
{
"mcpServers": {
"hosttracker": {
"type": "http",
"url": "https://mcp.host-tracker.com/mcp",
"headers": { "Authorization": "Bearer YOUR_HOSTTRACKER_API_TOKEN" }
}
}
}
Or from the command line:
claude mcp add --transport http hosttracker https://mcp.host-tracker.com/mcp \
--header "Authorization: Bearer YOUR_HOSTTRACKER_API_TOKEN"
Claude.ai and Claude Desktop
Settings -> Connectors -> Add custom connector -> paste https://mcp.host-tracker.com/mcp -> Connect. The
browser opens HostTracker's sign-in + consent page; press Approve and the connector is live. That is the whole
setup.
To use a bearer token instead (for example a long-lived token with a hand-picked scope set), Desktop can also
connect through the mcp-remote bridge. Edit claude_desktop_config.json:
{
"mcpServers": {
"hosttracker": {
"command": "npx",
"args": [
"-y", "mcp-remote", "https://mcp.host-tracker.com/mcp",
"--header", "Authorization:${HT_AUTH}"
],
"env": { "HT_AUTH": "Bearer YOUR_HOSTTRACKER_API_TOKEN" }
}
}
}
The ${HT_AUTH} indirection is deliberate: some mcp-remote builds split an argument on its first space, which
breaks a literal Authorization: Bearer .... Node.js 18 or newer is required.
Cursor
~/.cursor/mcp.json for every project, or .cursor/mcp.json for one:
{
"mcpServers": {
"hosttracker": {
"url": "https://mcp.host-tracker.com/mcp",
"headers": { "Authorization": "Bearer YOUR_HOSTTRACKER_API_TOKEN" }
}
}
}
VS Code (GitHub Copilot agent mode)
.vscode/mcp.json in the workspace. The inputs block keeps the token out of the file, prompting for it once and
storing it in the editor's secret storage:
{
"inputs": [
{
"type": "promptString",
"id": "ht-token",
"description": "HostTracker API token",
"password": true
}
],
"servers": {
"hosttracker": {
"type": "http",
"url": "https://mcp.host-tracker.com/mcp",
"headers": { "Authorization": "Bearer ${input:ht-token}" }
}
}
}
Windsurf
~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"hosttracker": {
"serverUrl": "https://mcp.host-tracker.com/mcp",
"headers": { "Authorization": "Bearer YOUR_HOSTTRACKER_API_TOKEN" }
}
}
}
Run it yourself (Docker)
The hosted endpoint is the normal way to use the server. If you would rather run your own copy - to read the code, audit it, or keep the MCP hop inside your network - the repository builds it from source:
docker build -t hosttracker-mcp https://github.com/HostTracker/mcp.git
docker run --rm -p 8080:8080 hosttracker-mcp
Your copy then answers at http://localhost:8080/mcp and takes exactly the same Authorization: Bearer header:
it is a stateless bridge, so it stores nothing and still talks to the public HostTracker API v2 under your token.
Without Docker, dotnet run --project src does the same on any machine with the .NET 10 SDK.
The same binary also speaks stdio, for clients that launch the server as a child process instead of
connecting to a URL. Add --stdio and pass your token as the HT_TOKEN environment variable (there is no request
header on stdio):
HT_TOKEN=YOUR_HOSTTRACKER_API_TOKEN dotnet run --project src -- --stdio
docker run -i --rm -e HT_TOKEN=YOUR_HOSTTRACKER_API_TOKEN hosttracker-mcp --stdio
Logs go to stderr in that mode, so stdout stays a clean protocol stream.
ChatGPT and other clients
ChatGPT (developer mode -> connectors): add https://mcp.host-tracker.com/mcp; ChatGPT offers its "link
account" step, which opens HostTracker's sign-in + consent page. Any other client with an OAuth-capable connector
dialog works the same way - just the URL.
Any client that can send a static header also works with a bearer token: the endpoint
https://mcp.host-tracker.com/mcp and the header Authorization: Bearer YOUR_HOSTTRACKER_API_TOKEN. Where a
client's connector form offers an API-key or custom-header authentication mode, the token goes there.
A generic, dependency-free bridge for anything that can only launch a command:
npx -y mcp-remote https://mcp.host-tracker.com/mcp --header "Authorization:${HT_AUTH}"
Longer walkthroughs, verification commands and troubleshooting live in CLIENT.md.
What the assistant can do
The server exposes the HostTracker v2 REST API as MCP tools. Every list tool takes limit (maximum 50) and
cursor and returns the next cursor; every timestamp is Unix seconds in both directions; ids are opaque strings.
| Family | What it covers |
|---|---|
| Checks | Run an instant check on any URL from 300+ locations (HTTP/S, ping, TCP port, traceroute, DNS, blacklist, WHOIS, Web Risk, crawl, page speed), fetch its result, list the available check types and devices. |
| Monitors | List, read, create, edit, copy, pause, resume and delete monitors, in single or bulk form, plus the catalogue of monitor types. |
| Results and incidents | Uptime summaries, raw check results, the incident list, one incident in detail, and comments on an incident. |
| Maintenance | List, create, edit and delete maintenance windows so planned work does not raise alerts. |
| Contacts | Manage contacts and contact groups, send and confirm a contact confirmation, and send a test alert to one. |
| Subscriptions | See who is notified for which monitor, and subscribe or unsubscribe a contact. |
| Webhooks | Manage webhook endpoints, send a test delivery, review the delivery log and redeliver a failed one. |
| Status pages | Manage public status pages, publish an incident on one and post follow-up updates. |
| Reports | Generate a report and list the report types available on your plan. |
| Jobs | Poll, wait on, cancel or resume the asynchronous jobs that bulk operations and reports return. |
| Account | Read-only: the account profile, its quota and its current usage. Useful for diagnosing a refused call. |
| Locations | List the checkpoint pools and individual monitoring locations you can target. |
| Generic door | describe_api searches the real v2 operations and api_request calls one, for anything without a dedicated tool. It is not a URL proxy: the operation must exist in the published API description, and the safety policy below still applies. |
| Family | Tools |
|---|---|
| Checks | run_instant_check, get_check_result, list_check_types |
| Monitors | list_monitors, get_monitor, create_monitor, update_monitor, delete_monitor, pause_monitor, resume_monitor, copy_monitor, bulk_create_monitors, bulk_update_monitors, bulk_delete_monitors, list_monitor_types |
| Results and incidents | get_uptime_summary, list_monitor_results, list_incidents, get_incident, comment_incident |
| Maintenance | list_maintenance, create_maintenance, update_maintenance, delete_maintenance |
| Contacts | list_contacts, get_contact, create_contact, update_contact, delete_contact, send_contact_confirmation, confirm_contact, test_contact, list_contact_groups, create_contact_group, update_contact_group, delete_contact_group |
| Subscriptions | list_subscriptions, subscribe_contact, unsubscribe_contact |
| Webhooks | list_webhooks, create_webhook, update_webhook, delete_webhook, test_webhook, list_webhook_deliveries, redeliver_webhook |
| Status pages | list_status_pages, get_status_page, create_status_page, update_status_page, delete_status_page, create_status_page_incident, add_status_page_incident_update |
| Reports | generate_report, list_report_types |
| Jobs | get_job, wait_for_job, cancel_job, resume_job |
| Account | get_account, get_account_quota, get_account_usage |
| Locations | list_locations |
| Generic door | describe_api, api_request |
Three behaviours worth knowing before the first call:
- Bulk operations validate first. A bulk tool returns a validation report; the write needs an explicit second
call with
submit=true. Bulk deletion additionally needsconfirmed=trueand the count the validation pass reported, so a selection that drifted in between is refused. - Bulk operations and reports are asynchronous. They answer with a job id; poll it with
wait_for_job. - Deleting anything is not undoable, so it always takes two calls. A delete tool's first call removes
nothing - it returns the resource so the assistant can show you what is about to go - and only a repeat call
with
confirmed=truedeletes. The API returns a receipt listing what was removed.
Authentication and scopes
Two ways in, same permission model:
- OAuth (connected apps). The client registers itself, you sign in once and approve a scope set on the
consent page, and the server mints short-lived access tokens (1 hour) with rotating refresh tokens (90 days)
behind the scenes. If the client requests no scopes it gets
check+monitor:read. Theaccountfamily is never grantable to a connected app. Every connection is listed under Integrations -> API -> Connected apps, where one click revokes it (the app then has to ask you again). A tool that needs a scope the connection lacks answersmissing_scopenaming what is required - reconnect and approve the wider set. - Bearer tokens. Mint them at Integrations -> API with a
hand-picked scope set, expiration and optional IP allow-list; pass them in the
Authorizationheader.
Scopes are per family with :read and :write leaves that do not imply each other; a bare family name
satisfies every leaf under it.
| You want the assistant to | Scopes |
|---|---|
| Run instant checks | check |
| See monitors, uptime and incidents | monitor:read |
| Create, edit, pause or delete monitors and maintenance | monitor:write |
| See who is notified | contact:read, subs:read |
| Manage contacts and subscriptions | contact:write, subs:write |
| Manage webhooks | webhook:read, webhook:write |
| Manage status pages and publish incidents | statuspage:read, statuspage:write |
| Read quota, usage and limits | account:read (bearer tokens only - not offered to OAuth connections) |
Grant the narrowest set that covers the work. There is never a reason to grant account:write: the server refuses
every write under /account regardless of what the token allows. If a call comes back refused, ask the assistant
to run get_account_quota, which reports the scopes the token actually carries.
Limits and quota
- The endpoint rate-limits each client IP on
/mcp. A limited response carriesRetry-After, which the server passes through as a value; it never sleeps or retries on your behalf, so the assistant decides what to do. - Your API plan quota is enforced against your own token, exactly as it is for direct REST calls.
get_account_usageandget_account_quotareport where you stand. Details in the errors and limits guide. - Application failures (no token, wrong scope, quota exhausted, invalid input) come back as ordinary tool results with an actionable message rather than a protocol error.
Safety
The server is stateless and stores nothing: every call is forwarded to the API under your own token, and all
ownership, quota and rate enforcement happens there. On top of that it refuses, at the server, regardless of the
token: any write under /account, and anything touching payments, plans, passwords, login or the minting of API
tokens. Content that a checked target controls is wrapped in a fenced, length-capped block before it reaches the
model, so a hostile target cannot inject instructions into your assistant. Full policy in
SECURITY.md.
Links
- MCP server overview
- Mint an API token
- API v2 reference and guides
- All integrations
- Official clients: JavaScript · Python · Go · .NET · CLI · OpenAPI description · GitHub Action
- Support: ht2support@host-tracker.com
License
The contents of this repository (documentation and metadata) are released under the MIT license. The hosted MCP server and the HostTracker service itself are proprietary.
HostTracker MCPのよくある質問
HostTracker MCPをClaude Codeに追加するには
ターミナルでclaude mcp add --transport http mcp https://mcp.host-tracker.com/mcpを実行します。すべてのプロジェクトで利用するには--scope userを追加します。
HostTracker MCPをCursorに追加するには
~/.cursor/mcp.jsonを開き、上記のインストールセクションに示すCursor設定を使ってmcpServersの下にサーバーを追加します。
AIアシスタントでHostTrackerにできることは何ですか?
300以上の拠点からライブチェックを実行する、モニターの管理(作成、一時停止、削除)、メンテナンスウィンドウのスケジューリング、インシデントの確認、アラートの管理、ステータスページの更新情報の公開などが可能です。
HostTracker MCP serverの認証方法を教えてください。
クライアントのコネクタダイアログ経由でサインインするOAuth 2.1を使用するか、Authorizationヘッダー経由でBearer tokenを使用できます。
一括操作やレポートは即時に完了しますか?
いいえ、一括操作とレポートは非同期で行われます。ジョブIDが返されるため、wait_for_jobツールを使用して完了を待機してください。
削除を取り消すことはできますか?
いいえ、削除は取り消せません。このサーバーでは2ステップのプロセスを採用しており、最初の呼び出しで削除対象を表示し、確認フラグを伴う2回目の呼び出しで実際の削除を実行します。