NEARpedia

io.github.UnityNodes/near-pediaVersion 1.0.1

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

Status

Responds339 msNov 14, 2026, 14:43 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 14:43 UTC
Latency: 339 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 21:12 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://near-pedia.xyz/mcpResponds339 msNov 14, 2026, 14:43 UTC

No sign-in

Claude Code

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

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: near-pedia
Remote MCP server URL: https://near-pedia.xyz/mcp

Cursor

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

VS Code

code --add-mcp '{"name":"near-pedia","type":"http","url":"https://near-pedia.xyz/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

27 tools

Tools of NEARpedia
	Description		Read-only	Idempotent	Open world
`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 whole breaking lines behind, each with the replacement and the source and date of the claim. Accepts one file: JavaScript/TypeScript, Rust, Cargo.toml, package.json or a JSON config. Use it on code written from memory, or when reviewing NEAR code. NEAR only. For one name rather than a file use check_deprecation.	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 whole breaking lines behind, each with the replacement and the source and date of the claim. Accepts one file: JavaScript/TypeScript, Rust, Cargo.toml, package.json or a JSON config. Use it on code written from memory, or when reviewing NEAR code. NEAR only. For one name rather than a file use check_deprecation.	No	Yes	Yes	Not declared
`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-selector/core", "near-lake-framework", "DelegateV2", "EXPERIMENTAL_tx_status", "near/near-cli", "rpc.testnet.pagoda.co". Use before writing or reviewing NEAR code that names a package or API from memory. NEAR only: for packages of other chains use their own tools.	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-selector/core", "near-lake-framework", "DelegateV2", "EXPERIMENTAL_tx_status", "near/near-cli", "rpc.testnet.pagoda.co". Use before writing or reviewing NEAR code that names a package or API from memory. NEAR only: for packages of other chains use their own tools.	No	Yes	Yes	Not declared
`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 error names (e.g. a removed action), and forum threads and GitHub issues that quote the same error. Needs the error text itself.	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 error names (e.g. a removed action), and forum threads and GitHub issues that quote the same error. Needs the error text itself.	No	Yes	Yes	Not declared
`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 contract from near-api-js", "cross-contract call in Rust".	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 contract from near-api-js", "cross-contract call in Rust".	No	Yes	Yes	Not declared
`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 no open issue matches; for "how do I fix / configure / why does X happen" use semantic_search (then get_doc) instead.	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 no open issue matches; for "how do I fix / configure / why does X happen" use semantic_search (then get_doc) instead.	No	Yes	Yes	Not declared
`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 the most TVL, or every project of a category ("Wallet", "DEX", "Validator"). Use for "what is Rhea Finance", "which wallets can I use on NEAR", "who does intents swaps", "has Meta Pool been hacked".	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 the most TVL, or every project of a category ("Wallet", "DEX", "Validator"). Use for "what is Rhea Finance", "which wallets can I use on NEAR", "who does intents swaps", "has Meta Pool been hacked".	No	Yes	Yes	Not declared
`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 offset to keep reading a long post past the first part.	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 offset to keep reading a long post past the first part.	No	Yes	Yes	Not declared
`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-api, near-cli-rs, cargo-near, near-workspaces, near-jsonrpc-client, mpc, near-sdk-js. Use when upgrading: "what breaks moving near-api-js from 5.1.0 to 7.4.0?".	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-api, near-cli-rs, cargo-near, near-workspaces, near-jsonrpc-client, mpc, near-sdk-js. Use when upgrading: "what breaks moving near-api-js from 5.1.0 to 7.4.0?".	No	Yes	Yes	Not declared
`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, and whether it is a known partner contract, a NEAR Catalog token or the subject of a deprecation entry.	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, and whether it is a known partner contract, a NEAR Catalog token or the subject of a deprecation entry.	No	Yes	Yes	Not declared
`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 at a time.	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 at a time.	No	Yes	Yes	Not declared
`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 the web. Get the id from search or semantic_search first.	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 the web. Get the id from search or semantic_search first.	No	Yes	Yes	Not declared
`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").	One NEAR ecosystem security incident in full, with DefiLlama's description, by the id list_incidents prints (e.g. "llama-1546-2026-04-16").	No	Yes	Yes	Not declared
`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 protocol upgrade vote, get_protocol_status. No arguments.	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 protocol upgrade vote, get_protocol_status. No arguments.	No	Yes	Yes	Not declared
`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-agent-api (NEAR Intents Agent API), near-ai-cloud (NEAR AI Cloud), agent-market (NEAR Agent Market), outlayer (NEAR OutLayer), trezu (Trezu), hot (HOT Labs), rhea (Rhea Finance). Also takes a contract account ("intents.near") or a catalog slug.	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-agent-api (NEAR Intents Agent API), near-ai-cloud (NEAR AI Cloud), agent-market (NEAR Agent Market), outlayer (NEAR OutLayer), trezu (Trezu), hot (HOT Labs), rhea (Rhea Finance). Also takes a contract account ("intents.near") or a catalog slug.	No	Yes	Yes	Not declared
`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").	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").	No	Yes	Yes	Not declared
`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, when voting for the next version starts according to the nearcore release notes, and which deprecations wait on that upgrade. Use when asked whether a protocol change (DelegateV2 removal, the gas rebate) is live yet, or when the next upgrade lands.	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, when voting for the next version starts according to the nearcore release notes, and which deprecations wait on that upgrade. Use when asked whether a protocol change (DelegateV2 removal, the gas rebate) is live yet, or when the next upgrade lands.	No	Yes	Yes	Not declared
`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 close) and timelocks, HSP drafts on gov.near.org not yet on chain, NEAR security incidents (30 days), and dated events such as the hackathon deadline. Each alert has a deadline where one exists, the date it expires, who it affects and a source link. Filter by level (critical/important/ecosystem/all). Use for "what is about to change or break on NEAR", "is there a protocol upgrade", "what is House of Stake voting on".	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 close) and timelocks, HSP drafts on gov.near.org not yet on chain, NEAR security incidents (30 days), and dated events such as the hackathon deadline. Each alert has a deadline where one exists, the date it expires, who it affects and a source link. Filter by level (critical/important/ecosystem/all). Use for "what is about to change or break on NEAR", "is there a protocol upgrade", "what is House of Stake voting on".	No	Yes	Yes	Not declared
`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 projects, plus new forum threads, releases and radar alerts. Each item with its date and source. NEAR activity only, not general crypto news.	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 projects, plus new forum threads, releases and radar alerts. Each item with its date and source. NEAR activity only, not general crypto news.	No	Yes	Yes	Not declared
`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, events, source metadata or wallet standards.	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, events, source metadata or wallet standards.	No	Yes	Yes	Not declared
`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, work done, fee and vote: what someone choosing where to stake wants to know.	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, work done, fee and vote: what someone choosing where to stake wants to know.	No	Yes	Yes	Not declared
`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, author, date); call get_blog_post with an id to read one. Release notes are not blog posts: they are under /releases.	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, author, date); call get_blog_post with an id to read one. Release notes are not blog posts: they are under /releases.	No	Yes	Yes	Not declared
`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); "related" are NEAR Catalog projects hacked on another chain. Use before integrating a protocol, or for "has X been exploited".	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); "related" are NEAR Catalog projects hacked on another chain. Use before integrating a protocol, or for "has X been exploited".	No	Yes	Yes	Not declared
`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 description. Use for "what is NEAR governance voting on", "did HSP-027 pass". For one proposal in full use get_proposal.	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 description. Use for "what is NEAR governance voting on", "did HSP-027 pass". For one proposal in full use get_proposal.	No	Yes	Yes	Not declared
`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_search.	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_search.	No	Yes	Yes	Not declared
`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 package is stale (e.g. near-sdk-js, @near-js/*). Use before adding or upgrading a dependency.	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 package is stale (e.g. near-sdk-js, @near-js/*). Use before adding or upgrading a dependency.	No	Yes	Yes	Not declared
`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 blockchains, the general web or local files. Use this for exact-term or name lookups; use semantic_search for conceptual how-does-X-work questions, and get_doc to read a full page once you have its id.	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 blockchains, the general web or local files. Use this for exact-term or name lookups; use semantic_search for conceptual how-does-X-work questions, and get_doc to read a full page once you have its id.	No	Yes	Yes	Not declared
`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 this for conceptual how-does-X-work questions; use search for exact-term or name lookups, and get_doc to read a full page once you have its id.	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 this for conceptual how-does-X-work questions; use search for exact-term or name lookups, and get_doc to read a full page once you have its id.	No	Yes	Yes	Not declared

Details

Registry status: Active
Published: Nov 10, 2026
Updated: Nov 10, 2026
Website: https://near-pedia.xyz/for-ai⁠ (opens in a new tab)
Repository: https://github.com/UnityNodes/near-pedia⁠ (opens in a new tab)
Categories (suggested): Project managementSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing