What NEAR looks like today, for AI agents: deprecations, protocol upgrades and g
What NEAR looks like today, for AI agents: deprecations, protocol upgrades and governance with a source and a date. MCP server (27 tools) + REST API, free, no key. Built at NEAR Hackathon 2026.
active Production-safe Score 93/100 http no auth
At a glance
| Endpoint | https://near-pedia.xyz/mcp |
|---|---|
| Source | https://github.com/UnityNodes/near-pedia |
| Transport | http |
| Tools | 27 |
| Auth | none |
| First seen | 2026-11-07 01:18:17 |
| Last checked | 2026-11-17 22:04:06 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 456 / 697 ms |
| Last successful check | 2026-11-17 22:04:06 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (27)
search— Keyword/full-text search over the NEAR knowledge base: docs.near.org and partner docs (NEAR Intents, NEAR AI Cloud, NEAR Agent Market, Trezuget_discussion— Read a gov.near.org forum thread in full: House of Stake proposals and their debate, validator threads, incident write-ups, developer standaget_doc— Read the FULL text of one indexed NEAR documentation page by id (NEAR node and developer docs plus partner docs) — exact commands, flags, anget_recent_changes— What changed on NEAR in the last N days, newest first: repositories archived or marked deprecated, packages deprecated, yanked or released,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 vget_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, andlist_videos— The newest videos of the NEAR Protocol, NEAR DevHub and NEAR AI YouTube channels: talks, interviews, livestreams, workshops, each with its dsemantic_search— Semantic (meaning-based) search over the NEAR knowledge base: docs.near.org and partner docs, gov.near.org threads, NEAR release notes, bloglist_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 repget_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 Nfind_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 comeget_breaking_changes— What changed between two versions of one NEAR product: every release in between with the removals and deprecations its notes announce, linesfind_known_issues— Surface known UNRESOLVED problems matching a free-text description: forum threads with zero replies but high views, plus open GitHub issues.check_deprecation— Check whether a NEAR package, crate, repository, RPC method, protocol feature, config key or hosted service is deprecated, removed or changeresolve_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 deprexplain_error— Paste a NEAR error (RPC response, transaction failure, contract panic, CLI output) and get its cause and fix: matched against a catalog of cget_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 superseget_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 sourcecheck_code— Check NEAR code before you ship it: finds the lines that import, depend on, call or configure something removed, deprecated, changed or supeget_protocol_status— Live NEAR protocol state of mainnet and testnet: the protocol version each runs and the newest its nodes support, the nearcore version, epoclist_proposals— List NEAR House of Stake governance proposals from the vote.dao contract, newest first: id, HSP number, status (with lapsed deadlines calledget_proposal— One NEAR House of Stake proposal in full: status, timeline, the vote with the quorum and approval arithmetic of the vote.dao contract, linksfind_project— Find NEAR ecosystem projects in NEAR Catalog (340) by name, by what they do, or by category: category, phase, website, GitHub, tokens with tlist_incidents— Security incidents in the NEAR ecosystem from DefiLlama's hacks dataset, newest first: date, amount lost and returned, technique, chains andget_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 sget_radar— Get the NEAR Radar: what is changing on NEAR now and needs action, and nothing that has already resolved. Protocol upgrades with the validat
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 22:04:06 | ✓ | ✓ | 697 ms | 90 | active |
| 2026-11-17 21:49:00 | ✓ | ✓ | 464 ms | 90 | active |
| 2026-11-17 21:33:52 | ✓ | ✓ | 548 ms | 90 | active |
| 2026-11-17 21:18:41 | ✓ | ✓ | 519 ms | 90 | active |
| 2026-11-17 21:03:36 | ✓ | ✓ | 480 ms | 90 | active |
| 2026-11-17 20:48:15 | ✓ | ✓ | 398 ms | 90 | active |
| 2026-11-17 20:33:10 | ✓ | ✓ | 402 ms | 90 | active |
| 2026-11-17 20:18:07 | ✓ | ✓ | 350 ms | 90 | active |
| 2026-11-17 20:02:34 | ✓ | ✓ | 1889 ms | 87 | active |
| 2026-11-17 19:47:09 | ✓ | ✓ | 501 ms | 90 | active |
| 2026-11-17 19:32:05 | ✓ | ✓ | 480 ms | 90 | active |
| 2026-11-17 19:16:58 | ✓ | ✓ | 482 ms | 90 | active |
| 2026-11-17 19:01:20 | ✓ | ✓ | 602 ms | 90 | active |
| 2026-11-17 18:46:16 | ✓ | ✓ | 498 ms | 90 | active |
| 2026-11-17 18:31:13 | ✓ | ✓ | 507 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://near-pedia.xyz/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/near-pedia-xyz-mcp # JSON