[NEARpedia. What NEAR looks like today. A terminal session: an agent adds the NEARpedia MCP server (27 tools), check_code names near-sdk-js, DelegateV2 and keyStores in its file with their replacements, get_validators and get_proposal answer live.]
[Connect an agent]
[Live site near-pedia.xyz]
[Ask a question]
[MCP setup for every client]
[CI]
[License MIT]
[Node 22]
[MCP over Streamable HTTP]
[NEAR mainnet]
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.
[!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
[Four steps. 1, Read: NEAR's own sources, live (docs, GitHub, npm and crates, RPC, House of Stake, the forum, blogs, videos, NEAR Catalog). 2, Index: full-text and meaning search over every source, what NEAR deprecated with the evidence, a radar whose alerts expire. 3, Check: check_code names each line that uses something NEAR removed, with what replaces it. 4, Answer: 27 MCP tools, a REST API, a site and /ask on NEAR AI, each answer with its source and its date.]
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
[For developers: is my NEAR code current? 12 tools: check_code, check_deprecation, resolve_package, get_breaking_changes, explain_error, find_known_issues, find_code_examples, get_standard, get_protocol_status, search, semantic_search, get_doc.]
[For builders: what is moving on NEAR? 10 tools: get_radar, list_proposals, get_proposal, get_discussion, list_incidents, get_incident, find_project, get_partner, get_contract_info, get_recent_changes.]
[For everyone: what is NEAR right now? 5 tools: get_network_state, get_validators, list_blog_posts, get_blog_post, list_videos.]
Connect an agent
Or, in Claude Code, the plugin: the same server plus a skill that checks NEAR code before and after writing it.
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:
Cursor, in ~/.cursor/mcp.json or .cursor/mcp.json:
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:
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:
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:
In another terminal:
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 935 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
What the corpus holds
As filled on 2026-11-02:
Forum posts and GitHub bodies are stripped of their HTML and blog posts of the site's footer; videos are embedded once they have a description, releases only with notes. The first fill reads the posts of the 300 newest threads and 300 video descriptions; the schedule reads the rest (40 threads every 15 minutes, 300 descriptions a day).
Layout
What was built before the hackathon, and what during it
Hackathon rules count work from 19 October 2026; anything earlier is a baseline (the hackathon FAQ's items Q-001, Q-002 and Q-005). We draw the line more strictly, at the template itself.
Baseline, not hackathon work. The engine is a copy of pedia-template, the ecosystem-neutral engine we extracted from our earlier knowledge hubs CCPEDIA (Canton) and Blobpedia (Celestia). It brings the database layer, search and embeddings, the MCP and REST servers, the web UI, the sync runner and the standing checks. The repository's first commit is that copy, tagged pre-hackathon and committed on 1 November 2026. It also carries general engine maintenance made in the template on 20–21 October, nothing NEAR-specific; we count that as baseline too rather than claim it.
Hackathon work. Everything after that tag: the NEAR rebrand, the NEAR sources, the deprecation engine, check_code, the RPC, validator and House of Stake readers, the ecosystem, incident and partner data, the radar, the 27-tool MCP surface, the GitHub Action, the Agent Market migration agent, the site pages, the NEAR AI Cloud integration, the database hash contract and the distribution files. The full difference is one link (FAQ Q-003): pre-hackathon...main.
Code from our other projects. lib/retry.ts and lib/polite-fetch.ts are ported from Monpedia, our Monad knowledge hub (October 2026); the port added conditional requests.
Third-party code. Open-source libraries listed in package.json (Next.js, React, better-sqlite3, sqlite-vec, the MCP SDK, Express, zod, @nearai/inference-sdk, near-api-js and others) and contracts/db-anchor/Cargo.toml (near-sdk), each under its own license. Two Lottie animations are credited in public/animations/CREDITS.txt. The site and the images in assets/ use Space Grotesk and JetBrains Mono, both under the SIL Open Font License 1.1.
AI assistance. The code in this repository, the baseline included, was written with Claude Code.
Our other hackathon project
The team also submits Hungry Minds, an AI pet NFT that pays for its own thoughts from its own balance (tracks nfts and games). The two projects are independent and share no code (Q-015).
Not an official project
NEARpedia is an independent community project. It is not a product of the NEAR Foundation, NEAR AI or House of Stake; it reads their public sources and links back to each.
License
MIT.
Maintained by Unity Nodes.
