LearnHouse
Build, edit and run courses, learning paths and communities in your LearnHouse academy.
Space story game on NEAR: swap via NEAR Intents to open star systems and unlock chapters.
作者提供的原文
此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列
| 1. 在 Claude 连接器目录中 | 否 | |
|---|---|---|
| 2. 团队实测过 | 否 | |
| 3. 适合泰国用户 | 否 | |
| 4. 不计星标的使用量 | 20/100 | 热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0 |
| 5. 登记日期 | 2026-11-16 |
用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。
质量: 基础检查通过 4/4 项(仅展示,不用于排序)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 NearVerse。按照 https://mcp.popnx.com/i/space-nearverse-nearverse.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 4/4 项检查 · 你的提问会经过开发者的服务器(nearverse.space) · ✓ 命令已检查 2026年11月16日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 5 分钟
需要 NearVerse 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
NearVersehttps://nearverse.space/mcp在 Request headers 下添加这个名称和值
AuthorizationBearer <在这里粘贴你的密钥>只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsNearVerse
用 NearVerse 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 NearVerse,或回答中出现 NearVerse 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 NearVerse
NearVerse 连接时需要你自己的密钥,但 OpenAI 帮助页面只说明了 OAuth 登录,没有我们能核实的填密钥方式
A · 使用能连接 NearVerse 的应用
B · 游戏、体育、美食与学习 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code · 约 5 分钟
需要 NearVerse 的密钥(在开发者网站创建)
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user nearverse https://nearverse.space/mcp --header 'Authorization: Bearer your-value'按 Enter 前,把“your-value”改成你的密钥
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
应能看到 NearVerse 在列表中并显示已连接
用 NearVerse 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 NearVerse,或回答中出现 NearVerse 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 5 分钟
需要 NearVerse 的密钥(在开发者网站创建)
在 NearVerse 的设置中,Authorization 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 NearVerse 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 NearVerse,或回答中出现 NearVerse 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 5 分钟
需要 NearVerse 的密钥(在开发者网站创建)
在 NearVerse 的设置中,Authorization 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 NearVerse 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 NearVerse,或回答中出现 NearVerse 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --transport http --scope user nearverse https://nearverse.space/mcp --header 'Authorization: Bearer your-value'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"nearverse": {
"url": "https://nearverse.space/mcp",
"headers": {
"Authorization": "Bearer your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"nearverse": {
"type": "http",
"url": "https://nearverse.space/mcp",
"headers": {
"Authorization": "Bearer your-value"
}
}
}
}说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
注册名称已通过域名 nearverse.space 验证(注册中心会核实域名所有权)
代码最后更新于昨天
不适用:由 nearverse.space 的所有者自己运行的云端服务器,你不会运行仓库里的代码
在 145 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/space-nearverse-nearverse)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 4 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:Authorization
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于昨天,最新版本(1.0.0)于4天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:LearnHouse, Anime Garden, WilmAI, Lumify Sports Intelligence, Savecraft
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Build, edit and run courses, learning paths and communities in your LearnHouse academy.
Finland's Wilma school system for parents and students: schedule, homework, exams and messages.
Schedules, scores, odds, splits & explainable AI bet confidence — 8+ sports, free instant key.
Savecraft serves real save game data and expert game knowledge to AI assistants.
| 本项 NearVerse | LearnHouse | Anime Garden | WilmAI | Lumify Sports Intelligence | Savecraft | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 是 | 否 | 否 | 否 | 是 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 4/4 | 5/5 | 4/4 | 3/3 | 4/4 | 3/4 |
| 许可证 | MIT | AGPL-3.0 | AGPL-3.0 | MIT | MIT | Apache-2.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
NearVerse is an English-language space exploration interface for real swaps through NEAR Intents. Its six asset regions contain ten systems and thirty sequential story chapters. NEAR, USDC, BTC, ETH and SOL are the main regions; USDT remains an alternative. A passage represents a swap, not a separate financial instrument or a promise of profit. After arrival, systems in the same asset region can be explored without additional swaps.
The application uses React, TypeScript and Vite, with a small Node/SQLite history backend. Aurora Intents core is pinned to 7.29.0 and the supported NEAR connector to 0.6.11. The existing standalone package remains locked for reproducibility but is not imported into the runtime. The map has an equivalent keyboard-accessible destination list, system illustrations have text descriptions, and expeditions resume from their saved timestamps.
Live application: nearverse.space.
NearVerse was developed for the November 2026 NEAR HACKATHON. Local development history runs from November 8 to November 16, 2026; the public repository contains a consolidated source snapshot rather than that development history. The application turns real NEAR Intents swaps into passages between fictional asset regions: a system, its description and its story chapters open only after a real swap into its asset that the server verifies. NEAR provides the account identity; NEAR Intents and Aurora's integration provide quotes, asset conversion and settlement. This is an interface built on existing infrastructure, not a new exchange protocol. AI agents can play the same game through a remote MCP server, with owner-set spending limits.
Third-party foundations include React, Vite, Aurora Intents core and the supported NEAR connector; exact dependencies and versions are recorded in package.json and package-lock.json. NearVerse's application code is available under the MIT License; dependencies retain their own licenses.
Use Node 22 and npm 10 on a dedicated development/build machine with sufficient memory. Dependency installation, the complete test suite and production bundling are resource-intensive: do not run them on a shared production host. The build's 4096 MiB JavaScript heap limit does not bound all subprocess memory.
npm ci --no-audit --no-fund
npm run typecheck npm test npm run test:icons npm run build npm run preview
npm run build produces the default minified Vite output in dist/. npm run preview serves that output and the history API on http://127.0.0.1:4319/. This command is a loopback server, not an automatic public deployment. The default database is data/history.sqlite.
For development, run these in separate terminals:
APP_ORIGIN=http://127.0.0.1:5173 PORT=4318 npm run server
npm run dev
Vite serves http://127.0.0.1:5173 and proxies /api to the history backend on port 4318. When changing the frontend origin, set APP_ORIGIN accordingly; do not disable Origin checks. The backend reads APP_ORIGIN, PORT and HISTORY_DB from its process environment.
Set VITE_AURORA_API_KEY in a local .env.local or in the build process environment. It is a public client integration key, embedded by Vite at build time. Never place a seed, private key, password or partner API secret in any VITE_* variable. Missing configuration blocks live quotes/swaps rather than substituting a fixture quote. Do not copy an entire secret environment file to a build server.
The committed .npmrc is required for lockfile-compatible peer resolution. Native SQLite installation may require Python and a C/C++ toolchain. The exact material-icon alias in vite.config.ts avoids importing a large icon barrel while retaining the original per-icon components; test:icons verifies its consumers and development/test/build mappings. Do not edit node_modules to change application behavior.
There is no swap-free mode: every system, its description and its chapters open only after a real swap into the system's asset that the server verifies. Without a wallet, the atlas shows only system names and assets. With a wallet, try editing the ship, swapping a small amount, starting an expedition, reloading and completing it after its timer. Select a destination from the text list and verify that focus moves to its heading. Check keyboard navigation, narrow screens and reduced-motion settings.
Export/import accepts bounded plain JSON for the same mode/account. Live imports change only local ship settings, never verified arrivals. User biographies are rendered as text, not HTML. Built-in ship art is used instead of arbitrary uploads.
Automated tests cover UI behavior, storage isolation, authenticated HTTP history, quote binding, signing guards, recovery and consent revocation. Controlled offline signers, mocked providers and dry quotes are not mainnet swaps. Successful tests or bundling do not constitute independent real-wallet financial acceptance.
availableWallets and connect(id) public APIs. Its built-in pointer-only .connect-item popup is not patched or imported as a universal wallet UI. Native NEAR signing, account lookup and transaction guards remain in the official connector and core SDK.src/assets.ts. BTC/ETH/SOL in the Intents balance are not automatic withdrawals to their native chains. Supported balances do not represent a full portfolio; staked assets and NFTs are outside scope.appFees: []; this does not mean upstream fees are zero. Actual applied fees must be read from the bound quote. No additional integrator fee is configured by this release.Do not perform financial acceptance, connect a personal wallet or change fee settings merely because a build/deployment succeeded. Wallet tests and any spending require their own explicit scope and approval.
History access requires a separate NEP-413 ownership sign-in: connecting an address alone is not authentication. Domain/nonce/expiry/account and the account's access key are checked. Sessions use HttpOnly/SameSite cookies, Secure on HTTPS, expiry/revocation and Origin checks. Account changes invalidate access to another account's history.
SQLite stores validated exploration events and minimal recovery bindings, not a portfolio, seed, private key or signed transaction archive. Expedition times are server-authoritative. IndexedDB is an account/mode-isolated cache and retry queue; unconfirmed writes remain visibly unsynced. Ship names, biographies and built-in appearance stay local. Public stories/art can be downloaded directly. Wallets, RPC providers and Aurora still see the information required for their operations; anonymity is not promised.
Export and deletion concern the user's journal. Local deletion does not delete server history, and server deletion does not undo a blockchain operation. See server/CONTRACT.md for the API contract and DEPENDENCY-SECURITY.md for dependency review. Third-party dependencies and untested wallet paths remain separate security-review concerns.
Use SQLite's online backup API rather than copying only the main file of a running WAL database:
npm run server -- backup data/history-backup.sqlite
npm run server -- restore data/history-backup.sqlite data/history-restored.sqlite
Existing destinations are not overwritten. Restore validates the database and revokes sessions/challenges. Stop the relevant service before switching HISTORY_DB; preserve the original database and its sidecars until rollback is no longer needed. Keep backups outside public web roots with restricted access.
Build and test on an isolated machine, retain source/artifact SHA-256 manifests and complete command logs, and transfer only the verified dist/. Back up the existing public assets before an atomic swap. Preserve the serving backend, its environment/configuration, database (including WAL/SHM), logs, service identity and neighboring sites. Do not deploy the repository's backend over a production backend carrying operational logging changes. An assets-only update should not require restarting that service or changing DNS.
Verify the public HTTPS HTML, language/title, hashed assets and their content hashes, compression, health endpoint, and unchanged backend/service identity. Keep the previous asset directory for rollback. Browser and real-wallet acceptance remain separate from static deployment proof.
##