World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Read your own ourpr running history in an AI agent, and put a plan on the week ahead.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 7/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 7/100 |
质量: 基础检查通过 2/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Ourpr MCP Server。按照 https://mcp.popnx.com/i/joeyaflores-ourpr-mcp-server.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 2/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server Ourpr MCP Server,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "ourpr": { "command": "npx", "args": [ "-y", "ourpr-mcp-server" ], "env": { "OURPR_TOKEN": "your-value" } } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) OURPR_TOKEN 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Ourpr MCP Server 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"ourpr": {
"command": "npx",
"args": [
"-y",
"ourpr-mcp-server"
],
"env": {
"OURPR_TOKEN": "your-value"
}
}
}
}只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Ourpr MCP Server 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Ourpr MCP Server,或回答中出现 Ourpr MCP Server 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Ourpr MCP Server
Ourpr MCP Server 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 Ourpr MCP Server 的应用
B · 其他 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要 Ourpr MCP Server 的密钥(在开发者网站创建) · 需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server Ourpr MCP Server,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user ourpr --env OURPR_TOKEN=your-value -- npx -y ourpr-mcp-server 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) OURPR_TOKEN 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Ourpr MCP Server 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
获取密钥的方法见下方开发者的 README
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user ourpr --env OURPR_TOKEN=your-value -- npx -y ourpr-mcp-server按 Enter 前,把“your-value”改成你的密钥
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
应能看到 Ourpr MCP Server 在列表中并显示已连接
用 Ourpr MCP Server 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Ourpr MCP Server,或回答中出现 Ourpr MCP Server 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要 Ourpr MCP Server 的密钥(在开发者网站创建) · 需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server Ourpr MCP Server,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "ourpr": { "command": "npx", "args": [ "-y", "ourpr-mcp-server" ], "env": { "OURPR_TOKEN": "your-value" } } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) OURPR_TOKEN 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Ourpr MCP Server 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
获取密钥的方法见下方开发者的 README
在 Ourpr MCP Server 的设置中,OURPR_TOKEN 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Ourpr MCP Server 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Ourpr MCP Server,或回答中出现 Ourpr MCP Server 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要 Ourpr MCP Server 的密钥(在开发者网站创建) · 需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server Ourpr MCP Server,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "ourpr": { "type": "stdio", "command": "npx", "args": [ "-y", "ourpr-mcp-server" ], "env": { "OURPR_TOKEN": "your-value" } } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) OURPR_TOKEN 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Ourpr MCP Server 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
获取密钥的方法见下方开发者的 README
在 Ourpr MCP Server 的设置中,OURPR_TOKEN 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 Ourpr MCP Server 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Ourpr MCP Server,或回答中出现 Ourpr MCP Server 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user ourpr --env OURPR_TOKEN=your-value -- npx -y ourpr-mcp-serverClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"ourpr": {
"command": "npx",
"args": [
"-y",
"ourpr-mcp-server"
],
"env": {
"OURPR_TOKEN": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"ourpr": {
"command": "npx",
"args": [
"-y",
"ourpr-mcp-server"
],
"env": {
"OURPR_TOKEN": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"ourpr": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"ourpr-mcp-server"
],
"env": {
"OURPR_TOKEN": "your-value"
}
}
}
}OURPR_TOKEN 机密 必填 env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 joeyaflores 验证,该账户拥有此仓库
代码最后更新于2个月前
仓库中没有找到许可证文件
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
OSV.dev 中没有 ourpr-mcp-server@0.5.0 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月16日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/joeyaflores-ourpr-mcp-server)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 2 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:OURPR_TOKEN
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于2个月前,最新版本(0.5.0)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| 本项 Ourpr MCP Server | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 是 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 2/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | – | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
An MCP server that lets an AI agent read your own running history from ourpr, and write one thing back. Ask about your training in plain language, in whatever agent you already use.
Every tool reads. One tool writes, and only that one: ourpr_plan_week puts a plan on a day still ahead. It cannot log a run, edit history, or issue another credential, and it needs a token made with the write scope.
In Claude you do not need this package. Add ourpr. from https://ourpr.app/your-runs: it signs you in once, with no token and nothing to install. This package is for a script or an agent on your own computer.
Reading your own runs is free. Planning is part of ourpr create, $10 a month, cancel any time: ourpr_plan_week answers only on an account that has it. Nothing else in ourpr costs money.
Every authenticated read in ourpr is gated by a session that lives about an hour, so nothing outside a browser could hold one. Personal access tokens changed that, and this is what they were for: your data, in your tools, with a credential you issued to yourself and can revoke.
1. Make a token. In ourpr, go to Settings → ourpr. mcp → Tokens for a script or a local server → New token. Name it after the machine it will live on, and choose Write if you want the agent to plan your week; Read otherwise. Copy it — it is shown once and cannot be recovered. A token lasts 90 days.
2. Point a client at it. The package runs from npm; nothing to clone.
Keep the token out of any file inside a project. A project's .mcp.json, .cursor/mcp.json or .vscode/mcp.json is often committed, and a committed token can be read by anyone who can read the repository. Every setup below keeps the token in a user-level place or in your system's secret store.
Pin the version. Each setup names an exact version, so a new release never runs with your token until you choose it. Change the number to update.
Read the token without echoing it, so it stays out of your shell history, then add the server for your user, not for a project:
printf 'Token: '; read -rs OURPR_TOKEN; echo
claude mcp add --scope user --env OURPR_TOKEN="$OURPR_TOKEN" --transport stdio \ ourpr -- npx -y ourpr-mcp-server@0.5.0 unset OURPR_TOKEN
Claude Code keeps it in ~/.claude.json, which belongs to your user.
Download ourpr.mcpb from the latest release and open it. Claude Desktop asks for the token and keeps it in your system's secret store. This is the recommended way.
Or edit claude_desktop_config.json, which lives in your user folder, not in a project. The token is then plain text in that file:
{
"mcpServers": { "ourpr": { "command": "npx", "args": ["-y", "ourpr-mcp-server@0.5.0"], "env": { "OURPR_TOKEN": "ourpr_pat_..." } } } }
Run MCP: Open User Configuration and add the server there. VS Code asks for the token once, masks it, and keeps it in its secret store:
{
"inputs": [ { "type": "promptString", "id": "ourpr-token", "description": "ourpr personal access token", "password": true } ], "servers": { "ourpr": { "type": "stdio", "command": "npx", "args": ["-y", "ourpr-mcp-server@0.5.0"], "env": { "OURPR_TOKEN": "${input:ourpr-token}" } } } }
Set OURPR_TOKEN in your shell profile or your system's secret manager, and add the server to the global ~/.cursor/mcp.json. The file holds only a reference to the variable:
{
"mcpServers": { "ourpr": { "command": "npx", "args": ["-y", "ourpr-mcp-server@0.5.0"], "env": { "OURPR_TOKEN": "${env:OURPR_TOKEN}" } } } }
Revoke it in Profile → Settings → ourpr. mcp, then make a new one. Revocation is immediate.
git clone https://github.com/joeyaflores/ourpr-mcp-server.git
cd ourpr-mcp-server npm install && npm run build && npm test
The server speaks MCP 2026-07-28, and it still answers a client that opens with the older initialize handshake. It is built on the official TypeScript SDK v2 (@modelcontextprotocol/server), and the tests run each version.
OURPR_TOKEN | Required. Your personal access token. |
OURPR_API_URL | Optional. Defaults to https://ourpr.onrender.com/api. |
The token is an environment variable and not a tool parameter, on purpose: it never changes between calls, so passing it per call would put a live credential into the agent's context, its transcript, and any log of either.
Every tool reads what you imported into ourpr, and what you logged or planned there. Runs that reach ourpr through the Strava sync stay out: Strava's API Policy (2026) keeps its API data out of MCP servers and AI tools. Your Strava bulk export is yours to use anywhere, so import it and every run is here.
ourpr_list_runsYour history between two dates, as a compact table: date, name, type, miles, pace, moving time, elevation, average heart rate.
Start here for almost anything — totals, streaks, trends, finding a run.
"How many miles did I run in July?"
"What was my longest run this spring?" "Show me every run over 15 miles in 2026"
start_date, end_date (YYYY-MM-DD), include_non_runs, limit.
It never truncates silently: if the window holds more than limit, the answer says how many were left out.
ourpr_get_runOne activity in full, with its mile splits, heart rate, cadence, calories and recording device.
"Break down my Boston Marathon splits"
"Did I positive or negative split that half?"
ourpr_run_streamA run resampled onto a fixed 10 metre grid — elevation, elapsed time, and where the watch recorded them, heart rate, power and cadence. Returns summary statistics per channel rather than every sample.
A 404 is a normal answer: indoor runs have no profile.
ourpr_run_lapsThe laps the watch itself recorded — the runner's own button presses, which is what a track session is actually divided by. Different from mile splits: laps follow the workout, splits follow the mile.
ourpr_rep_workoutsEvery interval session ourpr can find in your history, with the reps and their distance. An empty answer says how many activities were read, because "none found" and "none exist" are different claims.
ourpr_detect_repsAsk whether one particular run was an interval session.
ourpr_similar_terrainRuns matching a given distance and climb — how you find what you have already done that resembles a race you are training for.
"What have I run that's like Boston — 26 miles, 800 feet of climb?"
ourpr_training_blocksYour goal race and its Block: race day, distance, goal time, the week of the Block today falls in, and the miles for each week so far. A week that has not begun shows no miles, not zero. Also the Blocks before your past races, each with its result, its weeks and its peak week.
"What week of my Dallas block am I in, and how is my mileage building?"
"How does this block compare with the one before my last marathon?"
past: how many past Blocks, newest first. Three by default.
ourpr_list_racesEvery race ourpr finds in your history, tune-ups included, through the same detector the app's Blocks use. Each row carries the run id for ourpr_get_run. The answer also names the fastest result at 5K, 10K, half marathon and marathon.
"What is my half marathon PR?"
"List every marathon I have run, with the times"
distance, limit.
ourpr_list_plansThe plans already on your week between two dates, two weeks from today by default: the day, the name, the miles or time, the tag, your note, whether a run you logged fulfilled it, and whether ourpr create wrote it. An agent reads this before ourpr_plan_week, so a new plan does not land on a day that already holds one.
"What do I have planned for the next two weeks?"
"Did I do the runs I planned last week?"
start_date, end_date (YYYY-MM-DD).
ourpr_plan_weekThe one write. One planned run, or a week of them, onto days still ahead. Each lands on the runner's week as a plan they can see, edit and remove; the day sheet says it came from ourpr create. It never logs a run.
"Put a 6 mile easy run on Tuesday and 14 long on Saturday"
"Write me next week: three easy days, one workout, one long run"
plans, one to fourteen, each with date (YYYY-MM-DD, after today) and any of miles, minutes, name, note, tag (easy, workout, race), is_long.
Needs a token made with the Write scope, and ourpr create on the account. A Read token, or an account without create, is refused before anything is written. A runner may write 120 plans a day.
By an evaluation, not by listing the API.
Ten questions with verified answers were written first, computed straight from the database by an oracle that shares no code with this server (backend/scripts/mcp_eval_oracle.py). They said what actually matters: nine of ten need the activity window, three need one run in full, two need a second source.
So the window is the tool that has to be excellent — and a training_summary tool that seemed obvious while guessing turned out to answer nothing, and was not built.
Two of those questions are answered through this server, over the protocol, in four tool calls, and both match the oracle exactly:
Q1 peak week : 63.6 oracle 63.6 MATCH
Q2 fastest 10mi: 6:23 oracle 6:23 MATCH
A window can hold 800 runs. Handing an agent 800 full activity objects destroys the context it needs to think with, so ourpr_list_runs returns a compact markdown table and one run in full is a separate tool.
Same for streams: a ten mile run is about 1,600 samples per channel across five channels, so the tool returns min, average, max and coverage rather than 8,000 numbers the agent would only reduce anyway.
The token grants read access to your own runs, your goal race and your plans. On ourpr, every query a token makes is scoped to its owner by construction, and a test refuses a token route that could reach past it. A token made with the write scope, with ourpr create, may also put plans on your own week through one route, and nothing else. No token can log a run, issue another token, revoke your existing ones, or widen its own scope.
Each token may make 60 reads a minute, and a runner may write 120 plans a day. ourpr answers 429 past either, with RateLimit and Retry-After headers, and the tool says how long to wait.
Revoke any token at any time in Profile → Settings → ourpr. mcp. Revocation is immediate and permanent — a revoked token can never be restored.
A run's name and description are free text a person typed, or that arrived from an import. They travel into the same token stream as the agent's instructions, and a model has no boundary between the two.
Two defences, doing different jobs:
The structure is neutralised. Control characters, newlines, zero-width and bidirectional marks are stripped; a | is escaped so the table column it sits in survives; every field is capped. A newline in a name would otherwise end a table row early and shift every column after it — an agent then reads a wrong answer rather than refusing one.
The boundary is named. Runner-authored data is returned inside delimiters with one line saying it is data, not instructions. That reduces how often injection lands. It does not prevent it, and nothing here is written as though it did. The delimiters wrap the text content only; the structured result carries the same neutralised fields without them.
What this deliber