Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words Sign in

NearVerse

✓ service owner · nearverse.space

by web3blindversion 1.0.0i★ 0iRuns in the cloudOfficial site ↗
Registry namespace.nearverse/nearverse

How to install

What it does

Space story game on NEAR: swap via NEAR Intents to open star systems and unlock chapters.

  • Connects Runs in the cloud
  • Account or key Needs Authorization
  • Category Games, sports, food & learning

Why it ranks here

This one is in the “Apps that connect to AI” tab, which is ordered without stars, in this order

1. In Claude’s connector directoryNo
2. Tried by our teamNo
3. Works for Thai usersNo
4. Usage without stars20/100Popularity 0 · Freshness 12 · Still answering 8 · Likes from users +0
5. Listed on2026-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)

Install

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

  1. Sign up and create a NearVerse key

    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.

    Open the NearVerse site ↗

  2. Open Claude’s Connectors page

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  3. Click “Add” → “Custom” → “Web” and fill in these 2 fields

    Copy each value into the field with the same name in Claude, then click Continue

    Name · NameNearVerse
    Remote MCP server URL · Addresshttps://nearverse.space/mcp

    Under Request headers, add this name and value

    Header nameAuthorization
    ValueBearer <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

  4. Turn it on in a chat

    +ConnectorsNearVerse

  5. Try it

    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

What you can do instead

A · Use an app that can connect NearVerse

  • 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
  • You need a NearVerse key (create it on the maker’s site)
  • You need a NearVerse key (create it on the maker’s site)
  • You need a NearVerse key (create it on the maker’s site)

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)

  1. Sign up and create a NearVerse key

    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.

    Open the NearVerse site ↗

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

    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

  4. Type /mcp in Claude Code

    You should see NearVerse listed as connected

  5. Try it

    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)

  1. Sign up and create a NearVerse key

    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.

    Open the NearVerse site ↗

  2. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  3. Fill in your key

    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

  4. Open the AI chat in Cursor in Agent mode

  5. Try it

    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)

  1. Sign up and create a NearVerse key

    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.

    Open the NearVerse site ↗

  2. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  3. Fill in your key

    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

  4. Open the AI chat in VS Code in Agent mode

  5. Try it

    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.

See every app that uses MCP →

Address for apps that connect over the web

Addresshttps://nearverse.space/mcp

JSON settings are under “For developers” below

Stuck? Ask people who use NearVerse💬 Discussion →
For developers: Terminal commands and JSON settings

Over the web

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"
      }
    }
  }
}

Values you fill in

  • Authorization secret required HTTP header
    Bearer agent token from https://nearverse.space/mcp/ (owner signs a text message and sets USD limits)

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.

At a glance

Downloads per weeki
Not on npm/PyPI
Verified domain
✓ nearverse.space
Connection
Runs in the cloud
Transport
streamable-http
Latest versioni
1.0.0
Published to registryi
Nov 16, 2026
Code last changedi
Nov 19, 2026
Last checked
Nov 16, 2026
Maker
web3blind
Registry status
Active

Which apps can use it

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

All apps, with pros and cons →

Related guides

What it can do

The server asks you to sign in before it lists its tools.

Basic checksi

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

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain nearverse.space (the registry checks domain ownership)

  • ✓ Pass

    Still maintained

    Code last changed yesterday

  • – Not applicable

    Has a licence

    Not applicable: a cloud server run by the owner of nearverse.space; you don't run code from the repo

  • ✓ Pass

    Endpoint responds

    Responded in 145 ms (HTTP 401)

  • ✓ Pass

    Sign-in with OAuth

    Declares OAuth sign-in, so your AI app can take you to log in

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

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

Discussion

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.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Games, sports, food & learningi

  • More stars than 0% of the other 1631 servers in this category
  • Published to the registry more recently than 88% of the other 1631 servers in this category
  • Basic checks equal to or better than 99% of the other 1631 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is NearVerse safe?

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.

What keys or codes does it need?

You need to fill in: Authorization

Does it run on my computer or in the cloud?

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.

Is it still maintained?

The GitHub repo last changed yesterday, and the latest version (1.0.0) reached the registry 4 days ago.

Which apps can use it?

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).

What can I use instead?

In the same category: LearnHouse, Anime Garden, WilmAI, Lumify Sports Intelligence, Savecraft

Similar alternatives

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

LearnHouse

Build, edit and run courses, learning paths and communities in your LearnHouse academy.

by learnhouseWidely used★ 2.5KUpdated yesterday

Runs in the cloud✓ service owner · learnhouse.app

WilmAI

Finland's Wilma school system for parents and students: schedule, homework, exams and messages.

by aikarjalGrowing↓ 1.4K/wk★ 89 Stars for the whole repoUpdated 11 days ago

Runs on your computer✓ service owner · wilm.ai

Savecraft

Savecraft serves real save game data and expert game knowledge to AI assistants.

by joshsymondsEarly★ 13Updated 7 months ago

Runs in the cloudRepo archived✓ service owner · savecraft.gg
Compared with similar ones
This one
NearVerse
LearnHouseAnime GardenWilmAILumify Sports IntelligenceSavecraft
Runs whereRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyYesNoNoNoYesNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks4/45/54/43/34/43/4
LicenseMITAGPL-3.0AGPL-3.0MITMITApache-2.0
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

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

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.

NEAR HACKATHON: Build Beyond Boundaries

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.

A short path for judges
  1. Open the live application. Without a wallet, the atlas shows only system names and assets; there is no swap-free mode.
  2. Connect a NEAR wallet and sign in (a text message, not a transaction). Select a closed system from the keyboard-accessible destination list.
  3. In the Converter, swap a small amount (any amount is accepted) along that system's route, for example NEAR → USDT for Harbor. One swap opens one system. Chapter 2 is a two-hour expedition, chapter 3 needs a return swap along the same route, and new seasonal chapters arrive weekly. The ship panel shows an explorer level that grows with chapters read, not with money. Read the financial safety section first: a quote or a signed deposit is not proof of settlement, and real swaps use your own funds.
  4. After the server verifies the arrival, the system's description and first chapter unlock. Start an expedition, reload, and complete it after its timer to read the chapter.
  5. For agents: open nearverse.space/mcp/, set limits, sign, and give the token to an MCP client. See "AI agents (MCP)" below and llms.txt.

Setup

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.

Preview and accessibility checks

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.

Financial safety

  • The first screen has an active Connect NEAR wallet button. One click loads the financial module and opens the NEAR selector backed by the official connector; it does not request a swap signature. The game shell and cached-account return visits do not load the SDK until requested. A pending or unreadable recovery record is visibly fenced before activation.
  • Connection uses the genuine NEAR connector wallet through the public core provider contract, not the universal multichain wallet wrapper. Wallet accounts remain NEAR; BTC, ETH, SOL, USDC, USDT and wNEAR Intents destinations remain available. The activated provider/store stays mounted across destination and preview changes. The selector uses native dialog/button semantics and the official connector's 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.
  • Token identity is matched by exact asset ID and custody, not symbol alone. See 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.
  • Amounts use smallest-unit strings and BigInt. Signing requires a fresh bound quote, the correct account/assets/amounts/deadline, displayed fees and explicit consent. A supported asset does not guarantee a liquid route.
  • Revoking consent, changing conditions, switching to preview or unmounting blocks a stale attempt before its next wallet call. Re-checking consent does not revive an old attempt. This cannot cancel a wallet call or transaction already sent.
  • Recovery metadata is saved before signing. Unknown or pending outcomes block another transfer; reload restores status rather than resubmitting. Do not erase recovery or budget records to bypass this protection. Refunded/failed operations require explicit acknowledgement of a matching final upstream result.
  • A transaction signature or deposit submission is not arrival. The backend independently verifies final success and operation binding before recording a live arrival.
  • Any connected NEAR account can swap any amount it explicitly approves; the site sets no account allowlist or amount cap. Spending limits belong to the user or to an agent operating the site. Account/storage/gas reserves are checked before wallet calls, and a per-account operation ledger rejects resubmitting an already accounted signature.
  • NearVerse passes 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, privacy and operations

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.

Backup and restore

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.

Frontend-only deployment

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.

##

Only the beginning is shown; read the rest in the repo