Official MCP server for esa.io - a documentation sharing service for teams
Nothing to run from here
NEARpedia is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
27
tools declared
remote
at its publisher
—
calls last 7d
What it does
Live NEAR knowledge for agents: deprecations, breaking changes, protocol and contracts, dated
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http nearpedia-mcp https://near-pedia.xyz/mcp
# 2 — ask your agent for something these tools do
# search, get_discussion, get_doc and 24 more
NEARpedia costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
UNAll 3 servers
UnityNodes3 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http nearpedia-mcp https://near-pedia.xyz/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
27 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search query |
| type | string | no | — |
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | yes | Topic number (42644) or its gov.near.org URL (https://gov.near.org/t/slug/42644). | |
| from_post | integer | no | First post to return, for reading past the first 15. A URL ending in a post number starts there. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | yes | Doc page ID (from search/semantic_search results) |
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, no
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | — |
| limit | integer | no | — |
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 parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account | string | no | One validator pool account, e.g. astro-stakers.poolv1.near. Omit for the list. |
| limit | integer | no | How many of the largest to list (default 20). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| channel | string | no | Channel name filter, one of NEAR Protocol, NEAR DevHub, NEAR AI. Case-insensitive substring. |
| since | string | no | Earliest published_at (ISO date, e.g. "2026-01-01"). Default: no lower bound. |
| limit | integer | no | — |
| offset | integer | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Free-form question or phrase. |
| source_types | array | no | Restrict to these source types. Omit for all. |
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source | string | no | Which tab: blog (Blog), news (News), press-release (Press), partner-news (Partner press), third-party (Third-party). Omit for All, which is first-party writing only. |
| query | string | no | Words to look for in titles and text. Results come best match first. |
| limit | integer | no | How many posts to return. Default 20, max 50. |
| offset | integer | no | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Post id, as list_blog_posts gives it. |
| chars | integer | no | Characters of text to return. Default 12000; raise it (max 200000) for the whole post, or set 0 for metadata only. |
| offset | integer | no | Character position to start reading from, for a long post. The response names the offset that continues the read. |
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".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | What the code should do or use, e.g. "ft_transfer_call", "cross contract call", "near-api-js view function". |
| limit | integer | no | Most examples to return (default 4). |
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 mov
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product | string | yes | One of: nearcore, near-sdk, near-api-js, near-api, near-cli-rs, cargo-near, near-workspaces, near-jsonrpc-client, mpc, near-sdk-js; or its GitHub repo, e.g. "near/near-api-js". |
| from_version | string | yes | The version you are on, e.g. "5.1.0". |
| to_version | string | yes | The version you move to, e.g. "7.4.0". A prerelease target includes prereleases. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| description | string | yes | What you're seeing, in short prose. For an error message, explain_error answers with its cause and fix. |
| limit | integer | no | Max rows per source (default 5). |
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"
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Package, crate, repository (owner/repo or GitHub URL), RPC method, identifier, config key or endpoint host. |
| limit | integer | no | Most entries to return (default 3). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| package | string | yes | Package name, optionally with a version and registry: "near-api-js", "near-sdk@5.1.0", "npm:@near-js/accounts@2.5.1", "crates:near-workspaces". |
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 it
| Parameter | Type | Required | Notes |
|---|---|---|---|
| error_text | string | yes | The error message or response, as printed. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| nep | string | yes | A NEP number ("141", "NEP-141") for its full text, or words to search titles and texts. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account_id | string | yes | The account, e.g. "intents.near", "token.rhealab.near". |
| network | string | no | Default mainnet. |
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/T
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | The file contents, up to 100000 characters. |
| filename | string | no | The file name, e.g. "contract.ts", "Cargo.toml", "package.json". Picks the language. |
| language | string | no | Overrides the language detected from the file name or content. |
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 upg
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | One network; both when omitted. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Contract status, e.g. "Voting" or "Succeeded". |
| query | string | no | Text to find in the title or description. |
| limit | integer | no | Most proposals to return (default 10). |
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").
| Parameter | Type | Required | Notes |
|---|---|---|---|
| proposal | string | yes | On-chain id ("27", "#27") or HSP number ("HSP-027", "HSP 27"). |
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 wal
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Project name or words for what it does ("lending", "intents swap"); empty to list. |
| category | string | no | NEAR Catalog category, any case, singular or plural ("wallets", "DeFi", "DEX", "Validator"). An unknown one returns the list of categories. |
| limit | integer | no | Most projects to return (default 5; up to 50 for a whole category). |
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 ex
| Parameter | Type | Required | Notes |
|---|---|---|---|
| relevance | string | no | Default "near". |
| query | string | no | Text in the name, technique or description, e.g. "oracle". |
| project | string | no | NEAR Catalog slug, e.g. "ref-finance". |
| limit | integer | no | Most incidents to return (default 10). |
One NEAR ecosystem security incident in full, with DefiLlama's description, by the id list_incidents prints (e.g. "llama-1546-2026-04-16").
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Incident id from list_incidents. |
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 Out
| Parameter | Type | Required | Notes |
|---|---|---|---|
| partner | string | yes | Partner id, name, contract account or catalog slug, e.g. "near-intents". |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| level | string | no | Severity floor. "critical" and "important" return only that level; "ecosystem" is the low-severity feed; "all" (default) returns every live alert. |
| limit | integer | no | How many alerts to return, most severe and most recent first. Default 25. |
| offset | integer | no | Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install NEARpedia or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.0 · scanned 6 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest0a03f717e72391219b411cd0cffab5f38d128c1cba173eb80f92f18dc14f307e
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search | no tags | |
| get_discussion | no tags | |
| get_doc | no tags | |
| get_recent_changes | no tags | |
| get_network_state | no tags | |
| get_validators | no tags | |
| list_videos | no tags | |
| semantic_search | no tags | |
| list_blog_posts | no tags | |
| get_blog_post | no tags | |
| find_code_examples | no tags | |
| get_breaking_changes | no tags | |
| find_known_issues | no tags | |
| check_deprecation | no tags | |
| resolve_package | no tags | |
| explain_error | no tags | |
| get_standard | no tags | |
| get_contract_info | no tags | |
| check_code | no tags | |
| get_protocol_status | no tags | |
| list_proposals | no tags | |
| get_proposal | no tags | |
| find_project | no tags | |
| list_incidents | no tags | |
| get_incident | no tags | |
| get_partner | no tags | |
| get_radar | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest0a03f717e7239121
Scanned2026-11-06
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish NEARpedia can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.