Prototipo · Versión preliminar: todos los servidores del registro oficial, sincronizados cada 30 minutos. Las reseñas y las cuentas llegarán en una etapa posterior.
PopNx MCPServidores MCP para quienes usan IA · explicados con palabras sencillas

NEARpedia

de UnityNodesversión 1.0.0i★ –iSe ejecuta en la nube
Nombre en el registroio.github.UnityNodes/near-pedia

Instalar

Resumen

Descripción del creador (original en inglés)

Live NEAR knowledge for agents: deprecations, breaking changes, protocol and contracts, dated

Los tres pilares de PopNx MCP

Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

  • Conexión: Se ejecuta en la nube
  • Transporte: Streamable HTTP
  • Categoría: Búsqueda y memoria de IA

Instalación

Elige la app de IA que usas y copia la configuración.

Antes de instalar

Necesitas

¿Qué app usas?

Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.

Funciona en Claude para web, escritorio y móvil:

  1. Abre Settings → Connectors
  2. Presiona Add custom connector
  3. Pega la dirección de abajo y presiona Add
  4. Si te pide iniciar sesión, inicia sesión en el servicio del creador
SettingsConnectors1+ Add2https://…3
https://near-pedia.xyz/mcp

Ejecuta esto en tu terminal

claude mcp add --transport http near-pedia https://near-pedia.xyz/mcp

Abrir en Cursor

O copia la configuración tú

Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json

{
  "mcpServers": {
    "near-pedia": {
      "url": "https://near-pedia.xyz/mcp"
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Abrir en VS Code

O copia la configuración tú

Pégalo en .vscode/mcp.json de tu proyecto

{
  "servers": {
    "near-pedia": {
      "type": "http",
      "url": "https://near-pedia.xyz/mcp"
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

ChatGPT solo se conecta a servidores en internet:

  1. Abre ChatGPT en la web → Settings → Connectors (Apps)
  2. Presiona Create o Add (en algunos planes primero hay que activar Developer mode en Advanced)
  3. Pega la dirección de abajo, ponle un nombre y guarda
  4. Si te pide iniciar sesión, inicia sesión en el servicio del creador
SettingsConnectors1+ Create2https://…3
https://near-pedia.xyz/mcp

Los nombres de los menús pueden variar un poco según el plan y con el tiempo.

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Nombres y descripciones de las herramientas tal como los informó el servidor el 6 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.

  • search

    Keyword/full-text search over the NEAR knowledge base: docs.near.org and partner docs (NEAR Intents, NEAR AI Cloud, NEAR Agent Market, Trezu), gov.near.org governance and developer threads, NEAR release notes, blog and GitHub issues of NEAR repositories. NEAR only: not for other

  • get_discussion

    Read a gov.near.org forum thread in full: House of Stake proposals and their debate, validator threads, incident write-ups, developer standards. Takes the topic number or the gov.near.org URL that search, semantic_search and get_proposal give, and returns the posts in order, 15 a

  • get_doc

    Read the FULL text of one indexed NEAR documentation page by id (NEAR node and developer docs plus partner docs) — exact commands, flags, and whole sections a search snippet truncates. Best for NEAR operational/how-to questions. NEAR docs only, not the docs of other projects or t

  • get_recent_changes

    What changed on NEAR in the last N days, newest first: repositories archived or marked deprecated, packages deprecated, yanked or released, docs pages added, rewritten or removed, protocol upgrades, House of Stake proposals and status changes, security incidents, new NEAR Catalog

  • get_network_state

    NEAR right now, read live: NEAR price, market cap and 24-hour change (CoinGecko), and from mainnet RPC the block height, protocol and node version, total NEAR supply, and how many validators hold how much stake this epoch. For who the validators are, use get_validators; for the p

  • get_validators

    NEAR mainnet validators right now, from RPC: the largest by stake with their share, how much of their assigned work they did this epoch, and which protocol version they announce; who was kicked out of the last epoch and why. Pass a pool (astro-stakers.poolv1.near) for its rank, w

  • list_videos

    The newest videos of the NEAR Protocol, NEAR DevHub and NEAR AI YouTube channels: talks, interviews, livestreams, workshops, each with its date and the start of its description. Filter by channel or date. To find videos on a subject, use search with type youtube, or semantic_sear

  • semantic_search

    Semantic (meaning-based) search over the NEAR knowledge base: docs.near.org and partner docs, gov.near.org threads, NEAR release notes, blog, the ecosystem catalog and GitHub issues of NEAR repositories. NEAR only: not for other blockchains, the general web or local files. Use th

  • list_blog_posts

    List the blog posts nearpedia holds: articles, news and press releases from NEAR, and in tabs of their own partner press and third-party reprints. Omit source for what the Blog page shows under All. Pass query to search titles and text. Returns metadata only (id, title, kind, aut

  • get_blog_post

    Get one blog post by the id list_blog_posts or search gave: title, kind, author, date and the text. Articles, news and press releases from NEAR are returned in full; reprints and partner press are returned as an excerpt with a link to the original, the same as the website. Pass o

  • find_code_examples

    NEAR code examples on a topic from docs.near.org and gov.near.org, each code block run through check_code first: examples on live APIs come first, and a block that uses something removed or deprecated is listed after them with what in it is stale. Use for "show me how to call a c

  • get_breaking_changes

    What changed between two versions of one NEAR product: every release in between with the removals and deprecations its notes announce, lines marked breaking, and nearcore's CODE_COLOR, PROTOCOL_UPGRADE and SECURITY_UPGRADE flags. Products: nearcore, near-sdk, near-api-js, near-ap

  • find_known_issues

    Surface known UNRESOLVED problems matching a free-text description: forum threads with zero replies but high views, plus open GitHub issues. Answers "is anyone else hitting this?". NEAR-specific. Does NOT return fixes, solutions, config, or how-to steps, and returns nothing when

  • check_deprecation

    Check whether a NEAR package, crate, repository, RPC method, protocol feature, config key or hosted service is deprecated, removed or changed, and what to use instead, with the source and date of every claim. Pass the name as code or a config uses it: "near-sdk-js", "@near-wallet

  • resolve_package

    Look up one NEAR npm or crates.io package, optionally at a version: latest and latest stable version, whether that version is yanked or deprecated, how many stable versions are newer, the registry's deprecation message, and the deprecation entry with its replacement when the pack

  • explain_error

    Paste a NEAR error (RPC response, transaction failure, contract panic, CLI output) and get its cause and fix: matched against a catalog of common NEAR errors whose explanations are checked against docs.near.org on every sync, the deprecation entries for any API or package the err

  • get_standard

    A NEAR standard (NEP) from github.com/near/NEPs: by number for the full text with status, category, what it requires, replaces or is superseded by; or by words to find one (e.g. "fungible token", "storage", "meta transactions"). Use when implementing FT, NFT, storage management,

  • get_contract_info

    What is deployed on a NEAR account, read live from RPC: balance, storage, code hash and size, every method the wasm exports, NEP-330 source metadata (version, source repository and commit, build environment), standards declared or inferred from its methods, FT or NFT metadata, an

  • check_code

    Check NEAR code before you ship it: finds the lines that import, depend on, call or configure something removed, deprecated, changed or superseded in NEAR (archived SDKs, removed protocol actions, deprecated RPC methods, retired endpoints), and dependencies that are yanked or who

  • get_protocol_status

    Live NEAR protocol state of mainnet and testnet: the protocol version each runs and the newest its nodes support, the nearcore version, epoch progress, the stake-weighted upgrade vote of the block producers this epoch (with how much of the stake it was read from), the threshold,

  • list_proposals

    List NEAR House of Stake governance proposals from the vote.dao contract, newest first: id, HSP number, status (with lapsed deadlines called out), vote standing against quorum and approval thresholds, and the gov.near.org thread. Filter by status or by text in the title and descr

  • get_proposal

    One NEAR House of Stake proposal in full: status, timeline, the vote with the quorum and approval arithmetic of the vote.dao contract, links on chain and to its gov.near.org thread, and the proposal text. Pass the on-chain id ("27") or the HSP number ("HSP-027").

  • find_project

    Find NEAR ecosystem projects in NEAR Catalog (340) by name, by what they do, or by category: category, phase, website, GitHub, tokens with their NEAR contract, TVL on NEAR from DefiLlama, security incidents, and whether it is a NEAR partner. An empty query lists the projects with

  • list_incidents

    Security incidents in the NEAR ecosystem from DefiLlama's hacks dataset, newest first: date, amount lost and returned, technique, chains and source. "near" are hacks on NEAR or Aurora or of NEAR protocols (NEAR Intents, 2026-10-01, is filed under BSC by DefiLlama and counted here

  • get_incident

    One NEAR ecosystem security incident in full, with DefiLlama's description, by the id list_incidents prints (e.g. "llama-1546-2026-04-16").

  • get_partner

    What an agent needs to build on a NEAR partner: what it is, its mainnet contract accounts, GitHub, docs and llms.txt, how much of its docs search and semantic_search cover, its NEAR Catalog entry with TVL, and its security incidents. Partners: near-intents (NEAR Intents), intents

  • get_radar

    Get the NEAR Radar: what is changing on NEAR now and needs action, and nothing that has already resolved. Protocol upgrades with the validator vote and voting dates (until the network runs the new version), CODE_RED and security nearcore releases, House of Stake votes (until they

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026

  • ✓ Superada

    El creador coincide con el repo

    El nombre en el registro se verificó con la cuenta de GitHub UnityNodes, dueña del repo

  • … Aún sin revisar

    Sigue en mantenimiento

    Todavía no hemos leído este repo en GitHub

  • … Aún sin revisar

    Tiene licencia

    Todavía no hemos leído este repo en GitHub

  • ✓ Superada

    El endpoint responde

    Respondió en 750 ms (HTTP 200)

  • – No aplica

    Inicio de sesión con OAuth

    No hace falta iniciar sesión

  • ✓ Superada

    Sin instrucciones ocultas en las descripciones de herramientas

    Leímos 27 descripciones de herramientas y no encontramos instrucciones ocultas para la IA

Comparado con otros en Búsqueda y memoria de IAi

  • Más estrellas que el 0% de los otros 7254 servidores de esta categoría
  • Publicado en el registro más recientemente que el 96% de los otros 7254 servidores de esta categoría
  • Revisiones básicas iguales o mejores que el 100% de los otros 7254 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Preguntas frecuentes

¿Es seguro NEARpedia?

Superó 3 de 3 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.

¿Qué claves o códigos necesita?

El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.

¿Se ejecuta en mi computadora o en la nube?

Se ejecuta en la nube del creador. Te conectas por internet sin instalar nada, pero lo que envías pasa por los servidores del creador.

¿Sigue en mantenimiento?

El repo de GitHub cambió por última vez –, y la última versión (1.0.0) llegó al registro ayer.

¿Qué apps pueden usarlo?

Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.

¿Qué puedo usar en su lugar?

En la misma categoría: Context7, Codebase Memory, Exa

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

Context7

de upstash

Up-to-date docs for AI agents

Computadora o nube★ 64.224MITActualizado hoy
Instalar

Codebase Memory

de DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Se ejecuta en tu computadora★ 48.148MITActualizado hace 20 días
Instalar

Exa

de exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Se ejecuta en la nube★ 5213MITActualizado el mes pasado
Instalar

README del creador

Abrir el README

Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.

Live NEAR knowledge for AI agents. NEARpedia is an MCP server and REST API that tells a coding agent when the NEAR code it is about to write is already stale, and gives the replacement, with a source and a date on every answer. The same index serves people researching NEAR: a site and an /ask chat about protocol upgrades, House of Stake votes, validators, projects and incidents.

Built for the NEAR Hackathon (1–14 November 2026, tracks open and agents). Live at near-pedia.xyz since 2 November 2026; the MCP endpoint https://near-pedia.xyz/mcp needs no key.

Demo video, 81 seconds: youtu.be/L1mbTEWWraE. Submission post on X, with a 45-second promo: x.com/UnityNodes/status/2118447685397291123.

[!TIP]

Agents write NEAR code from what they remember, and NEAR keeps moving. A few changes from the last year, the first two in the weeks before this hackathon, that a model trained earlier cannot know about:

- near-sdk-js is archived and its README says "DO NOT USE".

- nearcore 2.14.0 removes DelegateV2.

- NEAR Lake is shut down and its tutorials are gone from docs.near.org.

- @near-js/* packages stopped at 2.5.1; the maintained package is near-api-js 7.x, which ships no keyStores.

Package registries rarely flag any of this, so the agent finds out when the build or the transaction fails. The official near/agent-skills are static instructions, and nearai/near-mcp performs chain actions rather than answering what is current.

How it works

The deprecation engine is fed by six signals: archived repositories, "deprecated / do not use" in a README, npm and crates.io deprecation or yank flags, removals in release notes, the docs' own deprecation markers and deleted pages, and long-dormant packages with a live successor. Weak signals are reported as "possibly deprecated". The radar keeps only what is true now: every alert ends when its subject resolves.

Three ways in

You want toGo to
Give your coding agent the toolsConnect an agent, or /for-ai for Claude.ai and ChatGPT (a custom connector, no install), Claude Desktop, Cursor, VS Code, Windsurf, Cline, Continue, Zed and JetBrains
See what NEAR deprecated, with the evidence/deprecations
Follow the protocol upgrade and the validator vote/protocol, /radar
Read House of Stake proposals and how the vote stands/governance
Ask in plain words/ask, answered by a model in a TEE on NEAR AI Cloud

Connect an agent

claude mcp add --transport http nearpedia https://near-pedia.xyz/mcp

Or, in Claude Code, the plugin: the same server plus a skill that checks NEAR code before and after writing it.

/plugin install nearpedia --marketplace UnityNodes/near-pedia

Then ask Claude Code to write a NEAR contract in JavaScript with meta-transactions and to check it with the nearpedia tools: check_code names near-sdk-js and DelegateV2 with their replacements.

Codex, Cursor and other clients

Codex, in ~/.codex/config.toml:

[mcp_servers.nearpedia]

url = "https://near-pedia.xyz/mcp"

Cursor, in ~/.cursor/mcp.json or .cursor/mcp.json:

{

"mcpServers": { "nearpedia": { "url": "https://near-pedia.xyz/mcp" } } }

Claude.ai and ChatGPT take the URL as a custom connector, with no install. Claude Desktop, Cursor, VS Code, Windsurf, Cline, Continue, Zed and JetBrains each name the fields differently; near-pedia.xyz/for-ai has the exact block for each. The public endpoint allows 300 tool calls per 15 minutes per client.

Check every pull request

A GitHub Action runs check_code on the files a pull request changes and leaves one comment: each line that uses something NEAR deprecated, removed or changed, what replaces it, and the source. Add .github/workflows/nearpedia.yml:

name: NEARpedia

on: pull_request permissions: contents: read pull-requests: write jobs: check: runs-on: ubuntu-latest steps:

  • uses: UnityNodes/near-pedia/github-action@main

No key is needed. Checked on 3 November 2026, near-examples/coin-flip-examples#37 adds 7 such lines: the @near-js/* packages that near-api-js 7 replaced, and dependencies a major version or more behind. To see the comment the action writes, open UnityNodes/near-pedia#5, a demo pull request that adds stale NEAR code to this repository: 12 findings in one comment and annotations on the changed lines. Inputs, outputs and a way to run it against any public pull request without installing anything are in github-action/README.md.

How common this is: on 3 November 2026, 19 of the 67 NEAR Hackathon projects with a public repository used something NEAR deprecated, removed or changed, most often keyStores and the @near-js/* packages. The method, and a script that runs the same check on any set of clones without naming anyone, are in docs/demo/hackathon-stale-count.md. The 67 repositories are not listed, so as not to single out other teams; the figure can be rerun on any set, not rechecked on the same one.

Try it against the live API

No install, no key:

# a file written from memory: three findings, each with its replacement and sources

curl -s -X POST https://near-pedia.xyz/api/v1/check-code -H 'Content-Type: application/json' \ -d '{"filename":"contract.ts","code":"import { NearBindgen } from \"near-sdk-js\";\nconst d = { DelegateV2: signed };\nconst ks = new keyStores.InMemoryKeyStore();"}'

the mainnet protocol version, the upgrade vote by stake and the voting schedule

curl -s 'https://near-pedia.xyz/api/v1/protocol?network=mainnet' | head -c 600

what is changing now, each alert with what ends it

curl -s https://near-pedia.xyz/api/v1/radar | head -c 600

check_code answers: line 1 imports near-sdk-js, archived, use near-sdk in Rust; line 2 builds a DelegateV2 action, removed in nearcore 2.14.0, use Delegate signed with a regular access key; line 3 uses keyStores, which near-api-js 7 does not ship, use a KeyPairSigner.

Run it yourself

The judge path, from a clean clone:

git clone https://github.com/UnityNodes/near-pedia

cd near-pedia npm ci npm run db:init npm run sync:near # every source is read live, about 25 minutes npx tsx mcp-server.ts # MCP and REST on :3131, leave it running

In another terminal:

curl -s -X POST http://127.0.0.1:3131/api/v1/check-code -H 'Content-Type: application/json' \

-d '{"filename":"contract.ts","code":"import { near } from \"near-sdk-js\";\nconst a = { DelegateV2: signed };"}' curl -s 'http://127.0.0.1:3131/api/v1/protocol?network=mainnet' | head -c 600 curl -s -X POST http://127.0.0.1:3131/api/v1/explain-error -H 'Content-Type: application/json' \ -d '{"error_text":"wasm execution failed with error: MethodResolveError(MethodNotFound)"}' curl -s http://127.0.0.1:3131/api/v1/contracts/intents.near | head -c 600 claude mcp add --transport http nearpedia http://127.0.0.1:3131/mcp

No time for the 25-minute sync? The same curls against https://near-pedia.xyz instead of http://127.0.0.1:3131 answer from the live index, and npm test needs neither. Without the sync, a local server answers explain-error and contracts (curated data and live RPC) but has an empty deprecation index and no protocol snapshot yet.

You see two check_code findings (near-sdk-js on line 1, DelegateV2 on line 2, each with its sources, dated where the source has a date), the mainnet upgrade with its voting dates and the share of stake that has voted, what the MethodNotFound error means and how to fix it, and the methods deployed on intents.near read live from RPC. npm run build && npm run start serves the site on :3130 from the same database. npm test runs 938 tests without network or keys; docs/TESTING.md says what each part checks.

You need

  • Node 22 (better-sqlite3 is built against its ABI, see .nvmrc)
  • No key for the steps above. NEARAI_API_KEY embeds the corpus for semantic_search (otherwise it matches words; embedding adds about 50 minutes) and turns on /ask; GITHUB_TOKEN adds the open issues and discussions of the NEAR repositories

What is done

PartState

| Engine: SQLite with F

Solo se muestra el principio; lee el resto en el repo

Pregunta a PopNx