NEARpedia is answering right now. Last checked 3 min ago. It exposes 27 tools. Last commit 6 Nov 2026.
Live NEAR knowledge for agents: deprecations, breaking changes, protocol and contracts, dated
Uptime history
47 hours of history
47 hours agonow
100.0%
Uptime 24h
92 of 92 checks
27
Tools
read from the server
252 ms
Response time
average over 24h
0
Stars
last commit 6 Nov 2026
What the code does
We read the source, 1 d ago · tools taken from the live server · rules 995398eba69f
Capabilities
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
Builds a file path from a variable
lib/migrate-repo.ts:368
const full = path.join(dir, file);
Reads files and sends them to the network
lib/mcp-probe.ts:57
for (const name of fs.readdirSync(os.tmpdir())) {
Sends data to a third-party sink
lib/ops-pager.ts:17
const TELEGRAM_API = 'https://api.telegram.org';
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.
run in your terminal
claude mcp add near-pedia --transport http https://near-pedia.xyz/mcpSettings → Connectors → Add custom connector, then paste this address
https://near-pedia.xyz/mcp~/.codex/config.toml
[mcp_servers.near-pedia]
url = "https://near-pedia.xyz/mcp".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"
}
}
}Available tools 27
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
blog
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.
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.
code
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.
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".
breaking
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?".
contract
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.
deprecation
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.
discussion
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.
doc
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.
explain
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.
incident
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").
incidents
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".
known
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.
network
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.
partner
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.
project
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".
proposal
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").
proposals
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.
protocol
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.
radar
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".
recent
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.
resolve
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.
search
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.
semantic
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.
standard
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.
validators
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.
videos
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://near-pedia.xyz/mcp | streamable-http | answering | 238 ms | 3 min ago |
Alternatives to NEARpedia
same job, measured the same wayDependency Freshness MCP
by armigerous
npm & PyPI freshness for AI agents: latest version, deprecations, dated breaking-change diffs.
MCP API Guardian
by petrovicistefan
Local OpenAPI contract and breaking-change checks for AI agents.
Sekichi
by surp-renz
Knowledge accumulation for AI coding agents. Records decisions, problems, and insights as context.
API Change Feed
by workers-anthonyzilar-changefeed
Breaking changes, deprecations and security fixes for 38 popular APIs/SDKs. Paid per call via x402.
Deprecation MCP
by tsvillain
MCP server for cross-vendor API/SDK deprecation and breaking-change tracking
Lorg MCP Server
by lorgai
Shared, peer-validated knowledge archive for AI agents — search, contribute, and validate via MCP
Agentpedia MCP Server
by ksaslam311
Search, discover, and contribute to AgentPedia - the knowledge base for AI agents.
Specwise MCP
by bytestay
OpenAPI and JSON Schema validation and OpenAPI breaking-change diffs for AI agents.
NEARpedia — questions
Answers built from our own checks of this server.
What can NEARpedia do?
It exposes 27 tools, read directly from the server on our last check. Among them: check_code, check_deprecation, explain_error, find_code_examples, find_known_issues, find_project and 21 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is NEARpedia mostly used for?
Its tools cluster around code and blog. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is NEARpedia working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 252 ms. The bar chart above shows every period we have measured.
How do I connect NEARpedia?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does NEARpedia need an API key?
No. NEARpedia completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 27 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is NEARpedia?
It answers our handshake in 252 ms on average, which is faster than 57% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is NEARpedia open source?
The code is open source: it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at near-pedia.xyz, which runs on its operator's own terms.