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.
This one is in the “Apps that connect to AI” tab, which is ordered without stars, in this order
| 1. In Claude’s connector directory | No | |
|---|---|---|
| 2. Tried by our team | No | |
| 3. Works for Thai users | No | |
| 4. Usage without stars | 20/100 | Popularity 0 · Freshness 12 · Still answering 8 · Likes from users +0 |
| 5. Listed on | 2026-11-16 |
Likes from users: 0 · Adds at most 5 points to the order (1 per person). It cannot be bought.
Quality: Passed 4/4 basic checks (shown, not used for ordering)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install NearVerse. Follow https://mcp.popnx.com/i/space-nearverse-nearverse.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 4/4 checks · What you ask goes through the maker’s server (nearverse.space) · ✓ Commands checked Nov 16, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude · about 5 min
You need a NearVerse key (create it on the maker’s site) · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
CustomizeConnectors
Copy each value into the field with the same name in Claude, then click Continue
NearVersehttps://nearverse.space/mcpUnder Request headers, add this name and value
AuthorizationBearer <paste your key here>Paste the key only into the app’s field, never into a chat or to anyone
Click Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add
+ConnectorsNearVerse
Use NearVerse and tell me what you can do for me, then show me one thing✓ If Claude says it is using NearVerse or shows a NearVerse tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect NearVerse yet
NearVerse needs your own key to connect, but OpenAI’s help page only describes OAuth sign-in; there is no key option we could verify
A · Use an app that can connect NearVerse
B · Others in Games, sports, food & learning that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code · about 5 min
You need a NearVerse key (create it on the maker’s site)
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --transport http --scope user nearverse https://nearverse.space/mcp --header 'Authorization: Bearer your-value'Replace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
You should see NearVerse listed as connected
Use NearVerse and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using NearVerse or shows a NearVerse tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor · about 5 min
You need a NearVerse key (create it on the maker’s site)
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
In the NearVerse settings, Authorization is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use NearVerse and tell me what you can do for me, then show me one thing✓ If Cursor says it is using NearVerse or shows a NearVerse tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code · about 5 min
You need a NearVerse key (create it on the maker’s site)
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
In the NearVerse settings, Authorization is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use NearVerse and tell me what you can do for me, then show me one thing✓ If VS Code says it is using NearVerse or shows a NearVerse tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
https://nearverse.space/mcpJSON settings are under “For developers” below
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"
}
}
}
}Descriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
The server asks you to sign in before it lists its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026
The registry name was verified against the domain nearverse.space (the registry checks domain ownership)
Code last changed yesterday
Not applicable: a cloud server run by the owner of nearverse.space; you don't run code from the repo
Responded in 145 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/space-nearverse-nearverse)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 4 of 4 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: Authorization
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed yesterday, and the latest version (1.0.0) reached the registry 4 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).
In the same category: LearnHouse, Anime Garden, WilmAI, Lumify Sports Intelligence, Savecraft
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
| This one NearVerse | LearnHouse | Anime Garden | WilmAI | Lumify Sports Intelligence | Savecraft | |
|---|---|---|---|---|---|---|
| Runs where | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | Yes | No | No | No | Yes | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 4/4 | 5/5 | 4/4 | 3/3 | 4/4 | 3/4 |
| License | MIT | AGPL-3.0 | AGPL-3.0 | MIT | MIT | Apache-2.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
##