Context7
Up-to-date docs for AI agents
제작자가 쓴 설명(영어 원문)
Live NEAR knowledge for agents: deprecations, breaking changes, protocol and contracts, dated
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
웹, 데스크톱, 모바일의 Claude에서 쓸 수 있어요:
https://near-pedia.xyz/mcp터미널에서 이 명령어를 실행하세요
claude mcp add --transport http near-pedia https://near-pedia.xyz/mcp프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"near-pedia": {
"url": "https://near-pedia.xyz/mcp"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"near-pedia": {
"type": "http",
"url": "https://near-pedia.xyz/mcp"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요:
https://near-pedia.xyz/mcp메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
도구 이름과 설명은 서버가 2026년 11월 6일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.
searchKeyword/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_discussionRead 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_docRead 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_changesWhat 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_stateNEAR 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_validatorsNEAR 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_videosThe 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_searchSemantic (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_postsList 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_postGet 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_examplesNEAR 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_changesWhat 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_issuesSurface 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_deprecationCheck 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_packageLook 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_errorPaste 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_standardA 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_infoWhat 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_codeCheck 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_statusLive 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_proposalsList 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_proposalOne 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_projectFind 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_incidentsSecurity 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_incidentOne NEAR ecosystem security incident in full, with DefiLlama's description, by the id list_incidents prints (e.g. "llama-1546-2026-04-16").
get_partnerWhat 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_radarGet 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
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검
레지스트리 이름이 GitHub 계정 UnityNodes 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
750ms 만에 응답(HTTP 200)
로그인 필요 없음
도구 설명 27개를 읽었고, AI에게 보내는 숨겨진 지시는 없었어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 3개 중 3개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(1.0.0)은 어제 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.
같은 카테고리에는: Context7, Codebase Memory, Exa
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
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-jsis 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 isnear-api-js7.x, which ships nokeyStores.
Package registries rarely flag any of this, so the agent finds out when the build or the transaction fails. The official
near/agent-skillsare static instructions, andnearai/near-mcpperforms chain actions rather than answering what is current.
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.
| You want to | Go to |
|---|---|
| Give your coding agent the tools | Connect 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 |
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.
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:
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.
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();"}'
curl -s 'https://near-pedia.xyz/api/v1/protocol?network=mainnet' | head -c 600
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.
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
better-sqlite3 is built against its ABI, see .nvmrc)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| Part | State |
|---|
| Engine: SQLite with F
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요