Skip to content
by Unity Nodes
BUILD · NEARpedia FOR AI AGENTS

MCP Setup

Give your agent what NEAR looks like today: is this API still alive, what replaced it, what changed this week. NEARpedia serves it over MCP and a REST API, with a source and a date on every answer. No authentication required.

27MCP tools
01

MCP Server

ENDPOINThttps://near-pedia.xyz/mcp

Install in your IDE / editor (11)

Claude Desktopjson
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) · %APPDATA%\Claude\claude_desktop_config.json (Windows)
{
  "mcpServers": {
    "nearpedia": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://near-pedia.xyz/mcp"]
    }
  }
}

NOTEClaude Desktop expects stdio, not HTTP. mcp-remote bridges the two. A bare "type": "http" entry can silently drop your whole mcpServers block on startup.

Available tools (27)

For code

12 tools

Is this API, package or version still current, what broke, what an error means, what a standard says.

  • searchKeyword/full-text search over the NEAR knowledge base: docs.near.org and partner docs (NEAR Intents, Trezu), gov.near…
  • get_docRead the FULL text of one indexed NEAR documentation page by id (NEAR node and developer docs plus partner docs) — ex…
  • semantic_searchSemantic (meaning-based) search over the NEAR knowledge base: docs.near.org and partner docs, gov.near.org threads, N…
  • find_code_examplesNEAR code examples on a topic from docs.near.org and gov.near.org, each code block run through check_code first: exam…
  • get_breaking_changesWhat changed between two versions of one NEAR product: every release in between with the removals and deprecations it…
  • find_known_issuesSurface known UNRESOLVED problems matching a free-text description: forum threads with zero replies but high views, p…
  • check_deprecationCheck whether a NEAR package, crate, repository, RPC method, protocol feature, config key or hosted service is deprec…
  • resolve_packageLook up one NEAR npm or crates.io package, optionally at a version: latest and latest stable version, whether that ve…
  • explain_errorPaste a NEAR error (RPC response, transaction failure, contract panic, CLI output) and get its cause and fix: matched…
  • get_standardA NEAR standard (NEP) from github.com/near/NEPs: by number for the full text with status, category, what it requires,…
  • check_codeCheck NEAR code before you ship it: finds the lines that import, depend on, call or configure something removed, depr…
  • get_protocol_statusLive NEAR protocol state of mainnet and testnet: the protocol version each runs and the newest its nodes support, the…

For builders

10 tools

What is changing now, governance votes and the forum debate behind them, incidents, projects, partners and contracts.

  • get_discussionRead a gov.near.org forum thread in full: House of Stake proposals and their debate, validator threads, incident writ…
  • get_recent_changesWhat changed on NEAR in the last N days, newest first: repositories archived or marked deprecated, packages deprecate…
  • get_contract_infoWhat is deployed on a NEAR account, read live from RPC: balance, storage, code hash and size, every method the wasm e…
  • list_proposalsList NEAR House of Stake governance proposals from the vote.dao contract, newest first: id, HSP number, status (with…
  • get_proposalOne NEAR House of Stake proposal in full: status, timeline, the vote with the quorum and approval arithmetic of the v…
  • find_projectFind NEAR ecosystem projects in NEAR Catalog (340) by name, by what they do, or by category: category, phase, website…
  • list_incidentsSecurity incidents in the NEAR ecosystem from DefiLlama's hacks dataset, newest first: date, amount lost and returned…
  • get_incidentOne NEAR ecosystem security incident in full, with DefiLlama's description, by the id list_incidents prints (e.g
  • get_partnerWhat an agent needs to build on a NEAR partner: what it is, its mainnet contract accounts, GitHub, docs and llms.txt,…
  • get_radarGet the NEAR Radar: what is changing on NEAR now and needs action, and nothing that has already resolved

For everyone

5 tools

NEAR right now: price, supply, validators and where to stake, the latest news and videos.

  • get_network_stateNEAR right now, read live: NEAR price, market cap and 24-hour change (CoinGecko), and from mainnet RPC the block heig…
  • get_validatorsNEAR mainnet validators right now, from RPC: the largest by stake with their share, how much of their assigned work t…
  • list_videosThe newest videos of the NEAR Protocol, NEAR DevHub and NEAR AI YouTube channels: talks, interviews, livestreams, wor…
  • list_blog_postsList the blog posts nearpedia holds: articles, news and press releases from NEAR, and in tabs of their own partner pr…
  • get_blog_postGet one blog post by the id list_blog_posts or search gave: title, kind, author, date and the text
02

Troubleshooting

Tools don’t show up after adding the server
Claude Code: run /mcp in a session, or claude mcp list to check connection status. VS Code: run "MCP: List Servers" from the command palette to see logs. Cursor / Claude Desktop / Windsurf / Zed: fully quit and reopen the app. Closing the window is not enough.
Claude Desktop config file looks empty after restart
A bare {"type":"http","url":...} entry can cause Claude Desktop to silently drop the whole mcpServers block. Use the mcp-remote bridge form shown above instead, and keep a backup of claude_desktop_config.json before editing it by hand.
Getting 429 Too Many Requests
Check the RateLimit-* response headers for your remaining quota and the Retry-After header for how long to wait. Limits are per IP (see Rate limits below), not per API key. There is no key to upgrade.
Not sure if it’s a client problem or the server is down
Test the server directly, outside any client: curl -s https://near-pedia.xyz/mcp -H "content-type: application/json" -H "accept: application/json, text/event-stream" -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' | head -c 200. If that returns JSON starting with {"jsonrpc":"2.0", the server is fine and the issue is in your client config.
03

REST API v1

BASE URLhttps://near-pedia.xyz/api/v1

Quick examples

SHELL
curl -X POST https://near-pedia.xyz/api/v1/check-code -H 'Content-Type: application/json' \
  -d '{"filename":"contract.ts","code":"import { near } from \"near-sdk-js\";"}'
curl 'https://near-pedia.xyz/api/v1/deprecations?q=near-lake'
curl 'https://near-pedia.xyz/api/v1/protocol?network=mainnet'
curl 'https://near-pedia.xyz/api/v1/search?q=meta+transactions&limit=5'

Endpoints (46)

  • /api/v1/proposalsHouse of Stake proposals from vote.dao with vote standing and forum threadstatus, q, limit
  • /api/v1/proposals/:refOne House of Stake proposal with its texton-chain id or HSP number, e.g. "27" or "HSP-027"
  • /api/v1/projectsNEAR Catalog projects with TVL on NEAR (DefiLlama) and partner flag; without q, the top projects by TVLq, category, limit
  • /api/v1/projects/:slugOne NEAR Catalog project with tokens, TVL components and security incidentscatalog slug, e.g. "ref-finance"
  • /api/v1/incidentsSecurity incidents in the NEAR ecosystem (DefiLlama hacks), newest firstrelevance (near|related|all), q, project, limit
  • /api/v1/incidents/:idOne security incidentincident id from /api/v1/incidents, e.g. "llama-1546-2026-04-16"
  • /api/v1/partnersNEAR partners (Intents, OutLayer, Trezu, HOT, Rhea): contracts, GitHub, docs feeds
  • /api/v1/partners/:idOne partner with its catalog projects and incidentspartner id, e.g. "near-intents"
  • /api/v1/protocolProtocol version, upgrade vote by stake, epoch progress and upgrade schedule of mainnet and testnetnetwork (mainnet|testnet)
  • /api/v1/packages/:nameOne npm or crates.io package (optionally name@version): latest, yanked or deprecated, the deprecation entryname, e.g. "[email protected]" or "crates:near-sdk"
  • POST /api/v1/explain-errorA NEAR error explained: catalog entry from docs.near.org, deprecations it names, forum threads and GitHub issuesBody: { error_text: string }
  • /api/v1/standardsNEAR standards (NEPs) from github.com/near/NEPsq (words in title or text)
  • /api/v1/standards/:nepOne NEP with its full text and what it requires, replaces or is replaced bynep, e.g. "141"
  • /api/v1/contracts/:accountWhat is deployed on an account, live from RPC: methods, standards, NEP-330 source metadata, token metadataaccount id; network (mainnet|testnet)
  • /api/v1/anchorsDaily database hashes, each with where it is recorded on NEAR (contract, transaction, block)limit
  • /api/v1/anchors/:dateOne day's database hash with its per-table manifestdate, YYYY-MM-DD
  • POST /api/v1/askAnswer a NEAR question (optionally about one pasted file) through NEAR AI Cloud, from this index's sources, with a verified response signature and a link to NEAR AI's Verification CenterBody: { question: string (≤2000 chars), code?: string (≤20000 chars), filename?, history?: [{ question, answer }] (the last 3 turns, so a follow-up can refer to them) }. 30 an hour per address
  • POST /api/v1/check-codeCheck one NEAR source file or manifest for removed, deprecated, changed or superseded APIs and outdated dependenciesBody: { code: string (≤100000 chars), filename?, language? (js|rust|cargo|package-json|json|toml|text) }
  • /api/v1/deprecationsDeprecated, removed and changed NEAR packages, APIs and services, each with evidenceq, kind, status, limit, offset
  • /api/v1/deprecations/:idOne deprecation entry with every piece of evidenceentry id, e.g. "near-sdk-js"
  • /api/v1/searchFull-text search across all contentq, type (all|doc|discussion|blog|youtube|github), limit
  • /api/v1/discussionsList forum topicslimit, offset, category
  • /api/v1/discussions/:idGet topic with poststopic id
  • /api/v1/docsList documentation pagessource, limit, offset
  • /api/v1/docs/:idGet full doc page contentdoc id
  • /api/v1/radarBreaking changes and deadlineslevel (all|critical|important|ecosystem)
  • /api/v1/blogBlog posts: articles, news and press releases, with tabs for partner press, notices and reprintssource, q, limit, offset
  • /api/v1/videosYouTube videoschannel, since, has_transcript, limit, offset
  • /api/v1/statsNetwork stats snapshot + history
  • /api/v1/reposIndexed GitHub repositories
  • /api/v1/codeGitHub issues and PRs browserrepo, state, type, q, limit, offset
  • /api/v1/ecosystemNEAR Catalog project catalogcategory, q, limit, offset
  • /api/v1/blog/:idSingle blog post; reprints and partner press come as an excerptpost id
  • /api/v1/videos/:idSingle YouTube video metadata + transcript, with the time of each linevideo id
  • /api/v1/github-discussionsGitHub Discussions (near/docs and other NEAR repos)repo, category, limit, offset
  • /api/v1/github-discussions/:idSingle discussion with body + commentsdiscussion node id
  • /api/v1/searches/popularTop human search queries on /searchwindow (days, 1-90), limit
  • /api/v1/searches/zeroDistinct search queries that returned 0 results - content-gap signalwindow, limit
  • /api/v1/sourcesDiscovery: one row per content type with current count + last-synced timestamp
  • /api/v1/networkLIVE NEAR on-chain state + NEAR market (Explorer + CoinGecko)
  • /api/v1/changesUnified activity feed: NEAR change events, forum threads, blog posts, releases, radar items - merged descending-by-timedays (1-90), limit (1-500)
  • /api/v1/csp-violationsAggregated CSP violations grouped by directive - for security monitoring dashboardswindow (days, 1-90), limit (top blocked_uris per directive, 1-25)
  • /api/v1/openapi.jsonOpenAPI 3.1 description of every endpoint - feed to Swagger UI / OpenAI function-calling / Postman
  • /api/v1/referenceInteractive API reference (Scalar) rendered from the OpenAPI spec - open in a browser to explore + try endpoints
  • /api/v1API index - lists every v1 endpoint with a one-line description
  • /healthLiveness probe + MCP tool count
04

Reference

Protocol

Version
2024-11-05
Transport
HTTP
Auth
None
CORS
*
Format
JSON / SSE

Content

Deprecations
136
Docs pages
483
Releases
1,328
Packages
90
Open issues and PRs
3,162
Forum threads
2,836
HoS proposals
30
Search chunks
26,453

Rate limits

/mcp
300 tool calls / 15 min per IP
/api/v1/search
20 req / min per IP
/api/v1/*
120 req / 15 min per IP

Limits returned in RateLimit-* headers. On 429, check Retry-After.