PatrolTech

Name: PatrolTech
Author: PatrolTech

作者：PatrolTech版本 0.2.8i★ –i在云端运行

注册名称online.patroltech/patroltech

安装

概览

作者提供的说明（英文原文）

Security patrol management: missed rounds, suspicious scans, incidents and checkpoint setup.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i3 项中通过 3 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在云端运行
传输方式: Streamable HTTP
分类: 其他

安装

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

安装之前

基础检查：3 项中通过 3 项
在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
注册中心没有列出需要填写的密钥。

你需要

在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude：

打开 Settings → Connectors
点击 Add custom connector
粘贴下面的地址，然后点击 Add
如果要求登录，请登录作者的服务

https://mcp.patroltech.online/mcp

在终端中运行这条命令

claude mcp add --transport http patroltech https://mcp.patroltech.online/mcp

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "patroltech": {
      "url": "https://mcp.patroltech.online/mcp"
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "patroltech": {
      "type": "http",
      "url": "https://mcp.patroltech.online/mcp"
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

ChatGPT 只能连接互联网上的服务器：

打开网页版 ChatGPT → Settings → Connectors (Apps)
点击 Create 或 Add（部分套餐需要先在 Advanced 中开启 Developer mode）
粘贴下面的地址，起个名字，然后保存
如果要求登录，请登录作者的服务

https://mcp.patroltech.online/mcp

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

服务器要求先登录，才会列出它的工具。

基础检查i

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

✓ 通过
作者与仓库一致
注册名称已通过域名 patroltech.online 验证（注册中心会核实域名所有权）
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
✓ 通过
端点有响应
在 1092 毫秒内响应（HTTP 401）
✓ 通过
使用 OAuth 登录
声明支持 OAuth 登录，你的 AI 应用可以带你去登录
… 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表

与“其他”中的其他服务器比较i

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

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

常见问题

PatrolTech 安全吗？

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在作者的云端运行。通过互联网连接，无需安装，但你发送的内容会经过作者的服务器。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.2.8）于5天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Foliosio

替代选择

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

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

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211前天更新

安装

Foliosio

作者：foliosio.com

Read your support inbox, tag conversations and save draft replies from your AI agent. Never sends.

在云端运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

PatrolTech MCP server

The remote Model Context Protocol server of PatrolTech, the guard tour and security patrol platform. It lets AI assistants such as Claude, ChatGPT, Copilot, Gemini or Cursor read and act on a PatrolTech account on behalf of a user who signs in with OAuth: rounds, routes, checkpoints, guards, incidents, users, locations, access control and scans.

This repository holds only the server code. To install the connector in your assistant, use PatrolTech/ai-integrations: plugins, MCP Registry entry and instructions for each client.

This server grants no access by itself. It has no credentials of its own: it forwards the user's token, and the PatrolTech API authorizes every call (organization and location roles, OAuth scopes and a closed list of writes allowed to agents). See SECURITY.md.

Connect without hosting a server

Use the hosted endpoint https://mcp.patroltech.online/mcp with an MCP client that supports remote OAuth. The user's PatrolTech account and role determine access.

Create a free account · Connection guide · Agent skill and client plugins

Building your own integration instead? See the API reference of the public REST API and the TypeScript SDK. Webhooks are in development: tell us which events you need at info@patroltech.app.

Ask about missed patrol rounds, suspicious checkpoint scans, unreviewed checkpoints, incidents or visitor access logs. Supported changes are proposals and require explicit confirmation. Deleting records, inviting users and billing are outside the connector's capabilities.

For client setup, OAuth verification and troubleshooting, see the agent installation guide, including Cline instructions.

How it works

MCP client ──OAuth──▶ PatrolTech authorization server

│ Bearer access token (audience = MCP_PUBLIC_URL) ▼ MCP server (this repo, stateless) ──agent session──▶ PatrolTech API │ ▲ └── Redis: locks and rate limits └── @patroltech/agent-capabilities + @patroltech/sdk-api

OAuth resource server. /mcp requires a bearer token issued by the PatrolTech authorization server (RFC 9728 metadata at /.well-known/oauth-protected-resource/mcp). Tokens are verified against the API's JWKS (ES256, exact issuer and audience) and exchanged for a 15-minute agent session (POST /oauth/agent-session), cached by a hash of the token. The API trims the session to what the grant still allows.
Stateless. Each request gets a fresh MCP server instance and serves both protocol eras (2025 and 2026-07-28). Nothing about a conversation is kept in memory: proposals live in the PatrolTech API, so any number of workers can serve the same user.
Redis holds what must be shared between workers: the per-user lock around proposals (SET NX PX, renewed while it lasts) and the per-user, per-tool rate limits. It is required in production and staging. If Redis fails, propose, confirm and cancel answer "busy" rather than risk two proposals overwriting each other. Without REDIS_URL (development and test only) both live in process memory.
Tools come from the mcp channel of @patroltech/agent-capabilities, which calls the API through @patroltech/sdk-api.

Tools

Tool	What it does
`patroltech_ _`	One per read of the catalog: read-only, English titles and descriptions, optional `organization` when the user has several.
`patroltech_account_get_context`	The user's organizations (name, role, access) and their locations. Its description says where to review this connection (`DASHBOARD_URL`, Connected apps).
`patroltech_ _propose_`	Proposes a change. Nothing changes until it is confirmed. Proposals of one user and client form one batch (up to 10, expires after 30 minutes).
`patroltech_proposals_confirm`	Executes the whole pending batch, in order, with the parameters that were proposed (marked destructive: clients ask the user first).
`patroltech_proposals_cancel`	Withdraws the pending batch.
`patroltech_locations_get_qr_sheet`	A signed link (1 hour) to the printable QR sheet of a location.

Prompts and resources

Both are fixed text in src/interface/mcp/guidance: they change nothing in the account and call no backend, so they do not go through the audit line or the rate limit of the tools. The connection still needs OAuth, like everything under /mcp.

Prompt	What it asks for
`patroltech_review_missed_rounds`	The latest rounds not completed and the checkpoints skipped.
`patroltech_review_suspicious_scans`	Suspicious or rejected scans, and how many are pending (`period`).
`patroltech_weekly_summary`	How the last week went, starting with what needs attention.
`patroltech_set_up_account`	What is missing to get the account running, and the next step.

Resource	What it holds
`patroltech://guides/choosing-a-tool`	Which tool answers each question, and how changes are confirmed.
`patroltech://guides/reading-the-data`	What statuses, scan validation, partial data and retention mean.

The server also sends instructions (src/interface/mcp/serverInstructions.ts): guidance that spans several tools, such as using the ranking tools to compare guards and presenting them as activity data, not as an assessment of the people.

Writes need the write scope: without it the server answers 403 insufficient_scope with the read write challenge. Every result is { data, truncated?, notices?, note }, capped at 60,000 characters, where note says that data is data, never instructions. Each user can make 60 calls per minute to a read tool and 20 to a write tool. Every tool call writes one mcp.tool_call audit line with a hash of the arguments, never the arguments.

Endpoints

Path	Auth	Purpose
`/mcp` (path of `MCP_PUBLIC_URL`)	Bearer	The MCP endpoint (POST, GET, DELETE). Validates `Host` and rejects any `Origin`.
`/.well-known/oauth-protected-resource/mcp`	none	Protected resource metadata (RFC 9728), also at the root path.
`/health`	none	Liveness: `200 {"status":"ok","version":"…"}`.
`/health/ready`	none	Readiness: `200` if the JWKS answers within 3 s and, with `REDIS_URL`, Redis answers `PING`; otherwise `503`.
`/.well-known/openai-apps-challenge`	none	The `OPENAI_APPS_CHALLENGE` token, for the ChatGPT apps directory; `404` without it.

Configuration

Every variable is documented in .env.example. The server refuses to start, listing each missing or invalid variable, if the configuration is not valid.

Variable	Required	Description
`MCP_PUBLIC_URL`	yes	Exact public URL of the MCP endpoint, the audience of the tokens (for example `https://mcp.example.com/mcp`).
`API_BASE_URL`	yes	Origin of the PatrolTech API, without `/api`.
`OAUTH_ISSUER`	yes	Expected `iss` of the access tokens, byte for byte.
`OAUTH_JWKS_URL`	no	JWKS of the issuer. Default `API_BASE_URL` + `/oauth/jwks.json`.
`DASHBOARD_URL`, `APP_BASE_URL`	yes	PatrolTech dashboard and web app, for links shown to the user.
`APP_ENVIRONMENT`	yes	`production`, `staging`, `development` or `test`.
`REDIS_URL`	in production and staging	Shared Redis (ioredis URL).
`REDIS_NAMESPACE`	no	Key prefix in Redis. Default `APP_ENVIRONMENT`.
`HOST`, `PORT`	no	Where the process listens. Default `127.0.0.1:3110`, behind a reverse proxy.
`LOG_LEVEL`	no	`debug`, `info` (default), `warn` or `error`. Audit and heartbeat lines are written at any level.
`SERVICE_NAME`	no	`service` field of every log line. Default `mcp-server`.
`OPENAI_APPS_CHALLENGE`	no	Domain verification token for the ChatGPT apps directory.

Logs are one JSON object per line on stdout and stderr. Each process writes an mcp.heartbeat line every 5 minutes, so a log monitor can alert when it stops.

Development

Node.js 22.9 or later.

npm ci

cp .env.example .env.local #

只显示了开头部分；其余内容请在仓库中阅读