RSS.com MCP by usefulapi
Read podcasts and episodes; create and edit episodes, chapters and transcripts in RSS.com.
作者提供的说明(英文原文)
MCP adapter for the Paxaver school community platform. Streamable HTTP, OAuth 2.1, capability auth.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://mcp.paxaver.com/mcp在终端中运行这条命令
claude mcp add --transport http paxaver https://mcp.paxaver.com/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"paxaver": {
"url": "https://mcp.paxaver.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"paxaver": {
"type": "http",
"url": "https://mcp.paxaver.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://mcp.paxaver.com/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
注册名称已通过 GitHub 账户 Smartoire 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
在 78 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(2.7.7)于6天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:RSS.com MCP by usefulapi, Castos MCP by usefulapi, Orah MCP by usefulapi
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Read podcasts and episodes; create and edit episodes, chapters and transcripts in RSS.com.
Read podcasts and episodes; create and update episodes; manage private subscribers in Castos.
Read students, rolls and attendance; create and update students, contacts and houses in Orah.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
AI-facing adapter over the Paxaver school community platform.
Implements the Model Context Protocol (MCP) on Cloudflare Workers with RS256 JWT
validation, capability-first authorization, and Streamable HTTP transport.
The Paxaver MCP server lets AI assistants (ChatGPT, Claude, Perplexity, and any MCP-compatible client) act on behalf of a Paxaver user: check a lunch menu, order lunch, review wallet balance and transaction history, register for fundraising events, enroll students in school programs, volunteer, and — for school administrators — manage restaurants, menu items, events, attendee check-in, volunteer shifts, program waitlists, and daily orders.
It is a thin adapter. It contains no business logic and holds no database, payment, or email credentials. Every action runs against the Paxaver backend API as the authenticated user, and errors are sanitized before they reach the client.
Point an MCP-compatible client at the hosted endpoint and sign in with a Paxaver account when prompted (OAuth 2.1 Authorization Code + PKCE):
https://mcp.paxaver.com/mcp
The server speaks MCP protocol 2025-06-18 over Streamable HTTP (POST /mcp). One endpoint serves all regions; the user's region is resolved from their account at sign-in.
npm install @paxaver/mcp
The package ships the Worker source for self-hosting and development. Most users only need the hosted endpoint above.
pnpm install # Node >= 26.8.2, pnpm >= 10
pnpm dev # Miniflare on http://localhost:8787 — MCP endpoint: POST /mcp
docker build -t paxaver-mcp .
docker run -p 8787:8787 paxaver-mcp
Self-hosted and local instances perform no token-revocation check: a revoked token stays valid until it expires. Tokens are still verified by signature, expiry, and a live user-context load.
See CONTRIBUTING.md for the full development setup.
The server exposes 37 tools grouped into six categories. Visibility in tools/list is filtered by the caller's roles; every call is re-authorized before dispatch, and the backend re-checks data-level access (defense-in-depth).
| Category | Tools |
|---|---|
| User / wallet | get_my_context, sign_out, get_my_wallet_balance, list_my_wallet_transactions |
| Lunch ordering | get_lunch_menu, list_my_lunch_orders, create_lunch_order_draft, update_lunch_order_draft, discard_lunch_order_draft, pay_lunch_order_draft, cancel_my_lunch_order |
| Events & volunteering | list_school_events, get_school_event, register_for_event, list_my_event_registrations, cancel_my_event_registration, list_my_volunteer_signups, sign_up_for_volunteer_shift, cancel_my_volunteer_signup |
| Event administration | create_school_event, update_school_event, cancel_school_event, list_event_attendees, check_in_event_ticket, create_volunteer_shift |
| Programs | list_school_programs, register_for_program, cancel_program_registration, list_program_registrations, admit_program_registration |
| Restaurant / menu admin | list_school_restaurants, create_school_restaurant, list_restaurant_menu_items, create_restaurant_menu_item, update_restaurant_menu_item, archive_restaurant_menu_item, schedule_lunch_menu_item |
The server registers four prompts: daily_lunch_menu, wallet_balance, upcoming_events, and lunch_order_helper (optional student_name argument). Availability and content are returned by prompts/list and prompts/get.
Ordering is draft → review → payment: create_lunch_order_draft, adjust with update_lunch_order_draft, then pay_lunch_order_draft.
sign_out ends the caller's sign-in for this MCP connection: the next request gets the usual sign-in challenge. An app that holds its own Paxaver credentials cannot be signed out this way — the result directs the user to disconnect Paxaver in that app or in their Paxaver account settings instead.
Pre-2.5 tool names still resolve to the canonical tools but are no longer advertised; the retired order_lunch tool is removed. Financial and destructive tools are labeled and require user confirmation.
The only contact information returned through MCP tools is the caller's own sign-in email — get_my_context includes it so a client can answer "which login am I on?", and sign_out names the account it signs out. Phone, address, and other contact fields are never returned. Student data is limited to IDs, names, and school slugs; allergies, notes, birthday, and other PII are not exposed in read responses. The MCP server does not log user data.
| Document | Topic |
|---|---|
| CHANGELOG.md | Release history |
| SECURITY.md | Vulnerability reporting policy |
| CONTRIBUTING.md | Development setup and contribution process |
Internal documentation (architecture, authentication, authorization, full tool reference, deployment, security model, test scenarios) lives in the private Paxaver monorepo under docs/paxaver-mcp/ and is intentionally not published.
2025-06-18, Streamable HTTPApache-2.0. Copyright (c) 2026 Smartoire. See LICENSE.