Skip to content
anlyon.devby Anlyon

NEARpedia MCP server

io.github.UnityNodes/near-pediaUnityNodesstreamable-httpv1.0.0Scanned

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

27 tools: 2 change things and 25 only read.

Tools: 0 delete, 0 irreversible, 2 write, 25 read.
  • Reads private data · 14
  • Reads text others write · 11
  • Can send data out · 0
  • No findings

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. anlyon.dev only lists and labels, and these labels are the same either way.

Compare with similar serversMarkdownJSONReport this listing

What the NEARpedia MCP server can do

The NEARpedia MCP server is published by the GitHub account UnityNodes. It has 27 tools. It can create or change data (2 tools: check_deprecation and check_code), but cannot delete data. 25 tools only read.

14 tools read private data (search, get_discussion, get_doc and 11 more); 11 tools bring in text other people can write (search, get_discussion, get_recent_changes and 8 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Nov 5, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

27 tools

Changes things 2Claude Code: ask
  • check_codeCheck 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 p…No findings

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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_deprecationCheck 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 sou…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 25Show 25 read-only tools
  • explain_errorPaste 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…No findings

    Why it is in this group

    • The name "explain_error" says "explain": a word for reading.
    Description, as the server wrote it
    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.
  • find_code_examplesNEAR 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 r…Reads private dataNo findings

    Why it is in this group

    • The name "find_code_examples" says "find": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "doc": it reads documents.
    Description, as the server wrote it
    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".
  • find_known_issuesSurface known UNRESOLVED problems matching a free-text description: forum threads with zero replies but high views, plus open GitHub issues.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "find_known_issues" says "find": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "thread": it reads messages.
    • untrusted-inputThe name "find_known_issues" says "find" and "issue": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "thread": it reads messages, which other people can write.
    Description, as the server wrote it
    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.
  • find_projectFind 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 Def…Reads text others writeNo findings

    Why it is in this group

    • The name "find_project" says "find": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "find" and "website": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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".
  • get_blog_postGet one blog post by the id list_blog_posts or search gave: title, kind, author, date and the text.Reads text others writeNo findings

    Why it is in this group

    • The name "get_blog_post" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe name "get_blog_post" says "get" and "post": it reads posts, which other people can write.
    • untrusted-inputThe description's first sentence says "get" and "post": it reads posts, which other people can write.
    Description, as the server wrote it
    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_breaking_changesWhat 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_CO…Reads private dataNo findings

    Why it is in this group

    • The name "get_breaking_changes" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "note": it reads notes.
    Description, as the server wrote it
    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?".
  • get_contract_infoWhat 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…Reads private dataNo findings

    Why it is in this group

    • The name "get_contract_info" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "repository": it reads repositories.
    Description, as the server wrote it
    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.
  • get_discussionRead a gov.near.org forum thread in full: House of Stake proposals and their debate, validator threads, incident write-ups, developer standards.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_discussion" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "thread": it reads messages.
    • untrusted-inputThe name "get_discussion" says "get" and "discussion": it reads comments, which other people can write.
    • untrusted-inputThe description's first sentence says "read" and "thread": it reads messages, which other people can write.
    Description, as the server wrote it
    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.
  • get_docRead 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 trunca…Reads private dataNo findings

    Why it is in this group

    • The name "get_doc" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_doc" says "get" and "doc": it reads documents.
    • private-dataThe description's first sentence says "read" and "doc": it reads documents.
    Description, as the server wrote it
    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.
  • get_incidentOne NEAR ecosystem security incident in full, with DefiLlama's description, by the id list_incidents prints (e.g.No findings

    Why it is in this group

    • The name "get_incident" says "get": a word for reading.
    Description, as the server wrote it
    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_network_stateNEAR 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 …No findings

    Why it is in this group

    • The name "get_network_state" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_partnerWhat 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 NEA…Reads private dataNo findings

    Why it is in this group

    • The name "get_partner" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "doc": it reads documents.
    Description, as the server wrote it
    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.
  • get_proposalOne 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…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_proposal" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "thread": it reads messages.
    • untrusted-inputThe description's first sentence says "thread": it reads messages, which other people can write.
    Description, as the server wrote it
    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").
  • get_protocol_statusLive 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 v…Reads private dataNo findings

    Why it is in this group

    • The name "get_protocol_status" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "note": it reads notes.
    Description, as the server wrote it
    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.
  • get_radarGet the NEAR Radar: what is changing on NEAR now and needs action, and nothing that has already resolved.No findings

    Why it is in this group

    • The name "get_radar" says "get": a word for reading.
    Description, as the server wrote it
    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_recent_changesWhat 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, …Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_recent_changes" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "repository": it reads repositories.
    • untrusted-inputThe description's first sentence says "thread": it reads messages, which other people can write.
    Description, as the server wrote it
    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.
  • get_standardA 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.No findings

    Why it is in this group

    • The name "get_standard" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_validatorsNEAR 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; w…No findings

    Why it is in this group

    • The name "get_validators" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • list_blog_postsList the blog posts nearpedia holds: articles, news and press releases from NEAR, and in tabs of their own partner press and third-party reprints.Reads text others writeNo findings

    Why it is in this group

    • The name "list_blog_posts" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe name "list_blog_posts" says "list" and "post": it reads posts, which other people can write.
    • untrusted-inputThe description's first sentence says "list" and "post": it reads posts, which other people can write.
    Description, as the server wrote it
    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_incidentsSecurity incidents in the NEAR ecosystem from DefiLlama's hacks dataset, newest first: date, amount lost and returned, technique, chains and source.No findings

    Why it is in this group

    • The name "list_incidents" says "list": a word for reading.
    Description, as the server wrote it
    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".
  • list_proposalsList 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 …Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "list_proposals" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "thread": it reads messages.
    • untrusted-inputThe description's first sentence says "list" and "thread": it reads messages, which other people can write.
    Description, as the server wrote it
    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_videosThe 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.No findings

    Why it is in this group

    • The name "list_videos" says "list": a word for reading.
    Description, as the server wrote it
    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.
  • resolve_packageLook 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 new…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "resolve_package" says "resolve": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "message": it reads messages.
    • untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data14
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write11
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

All changes to this server

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__near-pedia__search",
      "mcp__near-pedia__get_discussion",
      "mcp__near-pedia__get_doc",
      "mcp__near-pedia__get_recent_changes",
      "mcp__near-pedia__get_network_state",
      "mcp__near-pedia__get_validators",
      "mcp__near-pedia__list_videos",
      "mcp__near-pedia__semantic_search",
      "mcp__near-pedia__list_blog_posts",
      "mcp__near-pedia__get_blog_post",
      "mcp__near-pedia__find_code_examples",
      "mcp__near-pedia__get_breaking_changes",
      "mcp__near-pedia__find_known_issues",
      "mcp__near-pedia__resolve_package",
      "mcp__near-pedia__explain_error",
      "mcp__near-pedia__get_standard",
      "mcp__near-pedia__get_contract_info",
      "mcp__near-pedia__get_protocol_status",
      "mcp__near-pedia__list_proposals",
      "mcp__near-pedia__get_proposal",
      "mcp__near-pedia__find_project",
      "mcp__near-pedia__list_incidents",
      "mcp__near-pedia__get_incident",
      "mcp__near-pedia__get_partner",
      "mcp__near-pedia__get_radar"
    ],
    "ask": [
      "mcp__near-pedia__check_deprecation",
      "mcp__near-pedia__check_code"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as near-pedia. Review it before you use it.

Capability tags behind 17 rules
  • mcp__near-pedia__search private-data, untrusted-input
  • mcp__near-pedia__get_discussion private-data, untrusted-input
  • mcp__near-pedia__get_doc private-data
  • mcp__near-pedia__get_recent_changes private-data, untrusted-input
  • mcp__near-pedia__semantic_search private-data, untrusted-input
  • mcp__near-pedia__list_blog_posts untrusted-input
  • mcp__near-pedia__get_blog_post untrusted-input
  • mcp__near-pedia__find_code_examples private-data
  • mcp__near-pedia__get_breaking_changes private-data
  • mcp__near-pedia__find_known_issues private-data, untrusted-input
  • mcp__near-pedia__resolve_package private-data, untrusted-input
  • mcp__near-pedia__get_contract_info private-data
  • mcp__near-pedia__get_protocol_status private-data
  • mcp__near-pedia__list_proposals private-data, untrusted-input
  • mcp__near-pedia__get_proposal private-data, untrusted-input
  • mcp__near-pedia__find_project untrusted-input
  • mcp__near-pedia__get_partner private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/io.github.UnityNodes/near-pedia/verify?hash=5bf72d39f6457a8363ef8d331ec9d7e892c15aa3d456681954e5046b32732275" | jq -e '.changed == false'

Pinned hash 5bf72d39f645, from Nov 5, 2026, 16:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.github.UnityNodes/near-pedia/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

anlyon.dev badge for io.github.UnityNodes/near-pedia
[![anlyon.dev](https://anlyon.dev/badge/io.github.UnityNodes/near-pedia.svg)](https://anlyon.dev/servers/io.github.UnityNodes/near-pedia)

Source: MCP Registry · repository. Synced Nov 5, 2026, 16:17 UTC.

NEARpedia MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the NEARpedia MCP server safe?

No scan can promise that. What its definitions show: 27 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the NEARpedia MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the NEARpedia MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the NEARpedia MCP server have?

27 tools: 2 write, 25 read. check_deprecation, check_code, search, get_discussion, get_doc, get_recent_changes, get_network_state, get_validators and 19 more.

Does the NEARpedia MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the NEARpedia MCP server changed its tools?

Not since anlyon.dev started tracking it. Last scanned Nov 5, 2026.