原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚 登录

Rigby's Cloud Grants Feed

作者:MaxxSomers1220版本 1.0.1i★ 0i在云端运行代码仓库 ↗
注册名称io.github.MaxxSomers1220/rigbys-cloud

安装方法

能做什么

US grants research, 4 read-only tools. From $1 once / 90 days from redemption. Free delayed search.

作者提供的原文

  • 连接方式 在云端运行
  • 账号或密钥 需要 Authorization
  • 分类 搜索与 AI 记忆

可搭配使用

教 AI 做这类工作的 Skill,可与本项一起使用

timesfm

TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.

作者:google-research★ 35,6421 个 skill

Skill · 操作手册

Shadowbroker

Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…

作者:BigBodyCobain★ 11,6081 个 skill

Skill · 操作手册

google-maps-scraper

scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place

作者:gosom★ 8,2561 个 skill

Skill · 操作手册

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度0/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应8/8上次检查时云端端点有响应
使用分20/100

质量: 基础检查通过 4/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

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

用一句话让 AI 帮你安装

请帮我安装 Rigby's Cloud Grants Feed。按照 https://mcp.popnx.com/i/maxxsomers1220-rigbys-cloud.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 4/5 项检查 · 你的提问会经过开发者的服务器(mcp.rigbyscloud.com) · ✓ 命令已检查 2026年11月20日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 5 分钟

需要 Rigby's Cloud Grants Feed 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 注册并创建 Rigby's Cloud Grants Feed 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    打开 Rigby's Cloud Grants Feed 网站 ↗

  2. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  3. 点击“Add” → “Custom” → “Web”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称Rigby's Cloud Grants Feed
    Remote MCP server URL · 地址https://mcp.rigbyscloud.com/mcp

    在 Request headers 下添加这个名称和值

    Header 名称Authorization
    值Bearer <在这里粘贴你的密钥>

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

    在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add

  4. 在聊天中开启

    +ConnectorsRigby's Cloud Grants Feed

  5. 试一试

    用 Rigby's Cloud Grants Feed 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 Rigby's Cloud Grants Feed,或回答中出现 Rigby's Cloud Grants Feed 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

ChatGPT 暂时无法连接 Rigby's Cloud Grants Feed

Rigby's Cloud Grants Feed 连接时需要你自己的密钥,但 OpenAI 帮助页面只说明了 OAuth 登录,没有我们能核实的填密钥方式

你可以改用这些方式

A · 使用能连接 Rigby's Cloud Grants Feed 的应用

  • 需要 Rigby's Cloud Grants Feed 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
  • 需要 Rigby's Cloud Grants Feed 的密钥(在开发者网站创建)
  • 需要 Rigby's Cloud Grants Feed 的密钥(在开发者网站创建)
  • 需要 Rigby's Cloud Grants Feed 的密钥(在开发者网站创建)

B · 搜索与 AI 记忆 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

可连接 Claude Code · 约 5 分钟

需要 Rigby's Cloud Grants Feed 的密钥(在开发者网站创建)

  1. 注册并创建 Rigby's Cloud Grants Feed 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    打开 Rigby's Cloud Grants Feed 网站 ↗

  2. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  3. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user rigbys-cloud https://mcp.rigbyscloud.com/mcp --header 'Authorization: Bearer your-value'

    按 Enter 前,把“your-value”改成你的密钥

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

  4. 在 Claude Code 中输入 /mcp

    应能看到 Rigby's Cloud Grants Feed 在列表中并显示已连接

  5. 试一试

    用 Rigby's Cloud Grants Feed 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 Rigby's Cloud Grants Feed,或回答中出现 Rigby's Cloud Grants Feed 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 5 分钟

需要 Rigby's Cloud Grants Feed 的密钥(在开发者网站创建)

  1. 注册并创建 Rigby's Cloud Grants Feed 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    打开 Rigby's Cloud Grants Feed 网站 ↗

  2. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  3. 填写你的密钥

    在 Rigby's Cloud Grants Feed 的设置中,Authorization 还是空的,填入你的密钥并保存

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

  4. 在 Cursor 中以 Agent 模式打开 AI 聊天

  5. 试一试

    用 Rigby's Cloud Grants Feed 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 Rigby's Cloud Grants Feed,或回答中出现 Rigby's Cloud Grants Feed 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 5 分钟

需要 Rigby's Cloud Grants Feed 的密钥(在开发者网站创建)

  1. 注册并创建 Rigby's Cloud Grants Feed 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    打开 Rigby's Cloud Grants Feed 网站 ↗

  2. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  3. 填写你的密钥

    在 Rigby's Cloud Grants Feed 的设置中,Authorization 还是空的,填入你的密钥并保存

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

  4. 在 VS Code 中以 Agent 模式打开 AI 聊天

  5. 试一试

    用 Rigby's Cloud Grants Feed 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 Rigby's Cloud Grants Feed,或回答中出现 Rigby's Cloud Grants Feed 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://mcp.rigbyscloud.com/mcp

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Rigby's Cloud Grants Feed 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

claude mcp add --transport http --scope user rigbys-cloud https://mcp.rigbyscloud.com/mcp --header 'Authorization: Bearer your-value'

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "rigbys-cloud": {
      "url": "https://mcp.rigbyscloud.com/mcp",
      "headers": {
        "Authorization": "Bearer your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "rigbys-cloud": {
      "type": "http",
      "url": "https://mcp.rigbyscloud.com/mcp",
      "headers": {
        "Authorization": "Bearer your-value"
      }
    }
  }
}

需要你填写的值

  • Authorization 机密 必填 HTTP header
    输入 Bearer 后跟您的 Rigby's Cloud API 密钥。
    查看英文原文Enter Bearer followed by your Rigby's Cloud API key.

说明为自动翻译,变量名保持原样;不确定时请查看原文。

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

一览

每周下载量i
不在 npm/PyPI 上
许可证i
未注明许可证
连接方式
在云端运行
传输方式
streamable-http
最新版本i
1.0.1
发布到注册中心i
2026年11月20日
代码最后更新i
2026年11月20日
最近检查
2026年11月20日
作者
MaxxSomers1220
注册状态
活跃

哪些应用可以使用它

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

通过互联网连接,适用于

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

全部应用及其优缺点 →

它能做什么

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

基础检查i

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

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 MaxxSomers1220 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于今天

  • ✕ 未通过

    有许可证

    仓库中没有找到许可证文件

  • ✓ 通过

    端点有响应

    在 161 毫秒内响应(HTTP 401)

  • ✓ 通过

    使用 OAuth 登录

    声明支持 OAuth 登录,你的 AI 应用可以带你去登录

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查;我们会在检查端点时读取工具列表

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/maxxsomers1220-rigbys-cloud.svg)](https://mcp.popnx.com/en/servers/maxxsomers1220-rigbys-cloud)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“搜索与 AI 记忆”中的其他服务器比较i

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

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

常见问题

Rigby's Cloud Grants Feed 安全吗?

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

它需要哪些密钥或代码?

你需要填写:Authorization

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

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

它还在维护吗?

GitHub 仓库最后更新于今天,最新版本(1.0.1)于今天进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

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

OpenSEO

Keyword research, site audits, rank tracking and AI visibility for your AI agent.

作者:every-app广泛使用★ 2.8万6天前更新

在云端运行✓ everyapp.com

Exa

Official Exa MCP for web search, content fetching, and multi-step research.

作者:exa-labs广泛使用★ 5245今天更新

在云端运行✓ 服务方 · exa.aiPopNx 团队已实际试用

Microsoft Learn MCP

Official Microsoft Learn MCP Server – real-time, trusted docs & code samples for AI and LLMs.

作者:MicrosoftDocs广泛使用★ 200012个月前更新

在云端运行✓ 服务方 · microsoft.comPopNx 团队已实际试用

Docs

Search and read Empryo's documentation. Read-only, no auth, no local access.

作者:proxysoul正在增长★ 16282个月前更新

在云端运行✓ empryo.com
与相似项目对比
本项
Rigby's Cloud Grants Feed
OpenSEOExaMicrosoft Learn MCPDocsCOTAL actions (cotal.ai)
运行位置在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥是否否否否否
可在 Claude 中按 + 添加否是是是否否
基础检查4/55/52/44/44/44/4
许可证–MITMITCC-BY-4.0NOASSERTIONApache-2.0
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

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

Rigby's Cloud — Remote MCP Server (Spec Kit project)

The live Gumroad MCP pass starts at $1 USD before tax, with 90 days of access from redemption. The November 18 deployment notes below record the earlier draft.

Converted Nov 12, 2026 from Rigbys_Cloud_Remote_MCP_Spec_v1.md. Phases 1–3 implemented and locally verified on 2026-11-17. Phase 4 production service and scheduled feed verified on 2026-11-18; all three deployment checks passed. Live Gumroad verification is untested.

This folder is a Spec Kit project, ready for Codex. It follows GitHub Spec Kit layout: a constitution, one feature spec, a plan, and a task list.

Setup draft restored from the supplied README PDF on 2026-11-12. The final buyer-facing README is a Phase 6 deliverable. The HTTPS service and real production feed are live; buyer client verification has not started. All four Open Decisions were confirmed in chat on 2026-11-12 and recorded in the spec and plan. Correction recorded 2026-11-17: as of 2026-11-16, no paid pass has been sold; presale is still no. Maxx states this project is definitely not part of what he does for work. No broader employer IP clearance is claimed. All four Phase 0 setup checks passed on 2026-11-12. Phases 1–3 were explicitly authorized and their local checks are complete. Phase 4 is authorized; deployment and feed/schedule checks have passed, and the runbook check has passed. See the evidence in the plan and tasks.

Phase 4 deployment — 2026-11-18

The Railway application is connected to this repository's main branch and serves https://mcp.rigbyscloud.com/mcp and /redeem over HTTPS. A clean client verified unauthenticated MCP 401, redeem 200 with a Secure cookie, and health 200/version 1.0.0. /health now reports a real successful production feed, not a stub or seeded data.

Production collection retrieved 805 posted Grants.gov opportunities, 14,561 NIH awards and 138,849 OpenAlex papers. The published feed contains 786 opportunities, 14,371 award edges and 147,794 paper edges; 160 opportunities have confirmed research links. Evidence flags and neutral scores remain visible; missing coverage is not a funding-gap finding. The latest verified feed timestamp is 2026-11-18T18:10:23.488529+00:00.

The separate feed-builder service uses 6 GB memory, 2 vCPU and a 5 GB raw-data volume; Postgres also has 5 GB storage. Daily cron is 0 6 * * * UTC: 01:00 Eastern during standard time and 02:00 during daylight saving time. A manually triggered cron execution completed successfully (EXITED, 204 seconds), proving fresh Grants.gov retrieval and weekly research-cache reuse. The next timer run is 2026-11-19 at 06:00UTC (01:00 America/New_York); that future occurrence is not claimed as observed. The schedule is enabled in the deployed configuration.

261 tests pass, retaining all 227 Phase 3 tests. T4.1–T4.3 passed; the four-procedure operations runbook is reviewed and complete. No production test keys, license submissions, real buyer sales or synthetic feed/history data were used. Genuine free-search history must age seven days before delayed results exist.

The existing $99 MCP-pass Gumroad draft is unpublished with licensing saved. Its supplied product ID is configured only in Railway; no second product was created. Real-sale verification remains untested. No paid pass has been sold and T6.3 stays unchecked. Phase 5 and Phase 6 have not started.

Deploy check · Feed and cron check · Operations runbook. Earlier readiness/bootstrap reports and phase handoffs below are historical.

Phase 3 handoff — 2026-11-17

The local /redeem page accepts a Gumroad license and matching email, verifies the configured one-time $99 pass, and shows a new paid API key exactly once beside the Codex/Claude Code commands. Only key/license hashes, support prefix and allowed metadata persist. Expiry is exactly 90 days from original redemption.

Explicit replacement at /redeem/rotate immediately revokes the old key and preserves the original expiry and daily quotas. /health now reads real feed-run status, including last good timestamp and per-source statuses, with server1.0.0. There are still exactly four read-only MCP tools; none of their evidence flags or feed data was changed.

All 227 tests pass, including the existing 110. Independent local HTTP checks and a smoke test against the real 789-record local feed passed. Every Gumroad success was an injected synthetic fixture, not a real license check or sale. Temporary test credentials were cleaned up and local test listeners stopped.

Updated Gumroad status — 2026-11-18: Maxx confirms the existing $99 MCP-pass product is an unpublished draft with licensing saved. Its supplied product ID is now configured in the Railway application environment; do not create a second product. Live verification remains untested: no real license or sale is used in Phase 4. Missing or invalid configuration fails closed. No paid pass has been sold; T6.3 remains unchecked.

Local runbook and exact verification · Phase 3 evidence. Stop before Phase 4. No deployment, Railway schedule activation or later-phase work was performed. Earlier handoffs below are historical checkpoints.

Phase 2 handoff — 2026-11-17

The local FastAPI/FastMCP service is implemented: rigbys-cloud version 1.0.0, stateless Streamable HTTP JSON at /mcp, exactly four read-only tools. Search, full-record reads, stored edges and source-backed portfolio aggregation pass their seeded Postgres checks. Neutral evidence flags and source timestamps are retained; neutral placeholders are never turned into gap findings.

Bearer verification, redemption-based expiry, immediate revocation, free-tier restrictions and atomic daily quotas are verified over real HTTP. Immutable basic search snapshots implement genuine seven-day delay. The current real snapshot is not old enough yet: free search returns delayed_feed_unavailable rather than backdating data or falling back to current rows. Synthetic aged-snapshot tests verify the eventual allowed response has no scores or summaries.

All 110 automated tests pass, including the original 52. Authenticated MCP Inspector initializes the server, lists exactly four tools and calls all four against the real 789-record Phase 1 feed. Test credentials/redemptions are synthetic and are not sales; they were removed afterward. No paid pass has been sold and T6.3 remains unchecked.

Local setup and contracts · Phase 2 evidence. Stop before Phase 3: there is no redemption/key-issuance/rotation page, HTTP health endpoint, public deployment or later-phase client verification. Railway remains unchanged. The Phase 1 handoff below is the historical feed checkpoint.

Phase 1 handoff — 2026-11-17

The feed builder, source clients, cleaning, exact-identifier joins, versioned scoring, extractive summaries, Postgres migrations and daily job are implemented. Run/setup instructions: feed operations. Data meaning: data contract and scoring methodology.

Live source collection: 828 posted Grants.gov records, 14,601 NIH awards and 138,804 OpenAlex papers. The isolated workspace Postgres feed contains 789 current/rolling opportunities (39 expired or unresolved records excluded), 14,411 award links and 147,744 paper links. All 789 carry the five pipeline layers, traceability and methodology version. SC-002 data spot-check: 10/10, with all 10 source pages HTTP 200. Automated checks: 52 passed.

Coverage is not complete research intelligence: 165 opportunities have confirmed research links; 756 records have explicitly flagged neutral score placeholders because evidence is insufficient. Only 33 have observed descriptive proxy scores. Missing NIH/OpenAlex coverage does not mean an opportunity is underfunded. See evidence for task checks and sampled source proof.

This is a local Postgres validation using live public data; Railway production was not accessed or deployed and the host schedule is not activated. No Phase 2 MCP/auth code or later-phase redemption/client work has started. No paid pass has been sold as of 2026-11-16; T6.3 remains unchecked. Maxx states this project is definitely not part of what he does for work; no broader clearance is claimed.

Layout

rigbys-cloud-mcp/

├── README.md ← this file ├── .specify/ │ └── memory/ │ └── constitution.md ← governing rules (v1.0.0) — outranks the spec on conflict ├── specs/ │ └── 001-remote-mcp-server/ │ ├── spec.md ← what to build (user stories, FR-001–FR-015, success criteria) │ ├── plan.md ← how to build it (stack, data model, deployment, testing) │ └── tasks.md ← phased checklist for $speckit-implement └── .agents/ └── skills/ └── rigbys-cloud-grants/ └── SKILL.md ← skill file to ship with the server (draft in tasks Phase 6)

The diagram includes the planned Phase 6 skill path; it has not been created during setup.

How to use it with Codex

Spec Kit supports Codex CLI in skills mode — the commands start with $, not /:

# 1. From this project folder, in Codex:

(if you haven't installed the Spec Kit skills for Codex yet)

specify init . --ai codex --ai-skills

— or, on newer Spec Kit: specify init . --integration codex --integration-options="--skills"

2. Review the constitution + spec first:

$spec-kit-constitution # read .specify/memory/constitution.md

(or just open the files — the point is Codex works from these, not from chat)

3. When the Open Decisions in plan.md are resolved, build it:

$speckit-implement

— works through specs/001-remote-mcp-server/tasks.md, phase by phase.

Do not skip Phase 1 (feed) — the MCP server is a thin read over a working feed.

Do not run $speckit-implement until the four Open Decisions in plan.md are resolved. Confirmed 2026-11-12: $99 one-time / 90 days from redemption; paid 1,000 tool calls/day and free 20 searches/day; Railway; Python 3.12 + FastAPI + FastMCP. These decisions do not waive the constitution or the remaining phase checks. Stop after each phase and show its passed checks before moving on.

What this is

  • Product: Rigby's Cloud Grants Feed #1, served as a hosted remote MCP server.
  • Server: Streamable HTTP at https://mcp.rigbyscloud.com/mcp, server name rigbys-cloud.
  • Auth: one Bearer API key per buyer, from a Gumroad license redeemed at https://mcp.rigbyscloud.com/redeem. Maxx confirmed on 2026-11-12 that MCP and redemption share this hostname; root/apex routing is not a v1 prerequisite.
  • Tools (4 only): opportunity_search, opportunity_get, opportunity_links, gap_for_topic. Read-only.
  • Pay: timed MCP pass (from $1 one-time / 90 days from redemption) + $99 one-time snapshot file (separate product). No subscriptions for now.
  • Free tier: opportunity_search only, 7-day-delayed, no scores/summaries; 20 searches/day (confirmed 2026-11-12).

Source specs (the pre-Spec Kit versions)

  • ../../files/Rigbys_Cloud_Remote_MCP_Spec_v1.md — the MCP spec this was converted from
  • ../../files/Rigbys_Cloud_Grants_Feed_API_Spec_v1.md — unified record + API reads
  • ../../files/Rigbys_Cloud_AI_Enhanced_Feeds_Product_Definition.md — product definition, five layers, pay layer
  • ../../files/Gumroad_Snapshot_Listing_Draft.md — snapshot listing (separate product, still live)

These are historical references from the supplied README PDF; those original source files are not present in this checkout.

Guardrails (from the constitution)

  • Outside chance only, narrow and consul

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