
Rigby's Cloud Grants Feed
io.github.MaxxSomers1220由 GitHub 帳號 MaxxSomers1220 發布v1.0.0更新於 Nov 19, 2026
US grants research, 4 read-only tools. From $1 once / 90 days from redemption. Free delayed search.
概覽
託管式遠端 MCP 伺服器,提供唯讀的美國科研補助資料來源:搜尋機會、讀取紀錄、追蹤研究關聯並依主題彙整。
- 可以做什麼
- 在已發布的補助資料來源中搜尋美國補助機會
- 讀取完整機會紀錄及其證據標記與來源時間戳
- 查詢機會與 NIH 獎助、OpenAlex 論文之間已儲存的關聯
- 依研究主題彙整有來源依據的組合檢視
- 免費層僅提供延遲搜尋,不含評分與摘要
- 適用情境
- 適合需要查詢美國補助機會及其科研背景的情境,例如瀏覽 Grants.gov 公告,或查看某主題相關的獎助與論文。只有在你已持有 Rigby's Cloud API 金鑰,或願意使用受限的免費延遲搜尋時,才值得加入。
- 執行需求
- 遠端 Streamable HTTP 端點 mcp.rigbyscloud.com,不需本機套件。必須在 Authorization 標頭提供 Bearer API 金鑰,金鑰可透過提供方的兌換頁面兌換 Gumroad 授權取得。付費存取為限時通行證;免費層每天 20 次搜尋。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Rigby's Cloud Grants Feed,將其新增到工作區。
- 連接 Authorization token 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
交給代理程式安裝
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/io.github.MaxxSomers1220%2Frigbys-cloud/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"rigby-s-cloud-grants-feed": {
"type": "http",
"url": "https://mcp.rigbyscloud.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}README
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
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 /:
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 namerigbys-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_searchonly, 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 consulting-first — pre-sell before building. One paid pass is the validation signal.
- Employer IP / conflict check: the source constitution records it as unverified and says do not sell until checked. Maxx states this project is definitely not part of what he does for work; no broader clearance is claimed.
- Dropped directions stay dropped: research-ops, governance/catalog, adherence.
- No trials in v1. No subscriptions for now. Secrets in env vars only.
來源:README.md,提交 28d6e07
工具
0版本歷史
1- v1.0.0最新Nov 19, 2026
評分
已滿足適用檢查項的 75%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通必需25 分
- 已宣告認證方式必需10 分
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分
請在儲存庫或註冊中心條目中宣告授權條款。