# NEARpedia (remote · near-pedia.xyz)

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

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `near-pedia.xyz`: 80/100 (this document), [markdown](https://verifymcp.io/servers/unitynodes-near-pedia/near-pedia.md), [page](https://verifymcp.io/servers/unitynodes-near-pedia/near-pedia)

## Channel facts

- Endpoint: `https://near-pedia.xyz/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4056 tokens (~150/item across 27 items; 27 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 88% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 27 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 27 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the NEARpedia MCP server?

NEARpedia is a hosted endpoint at https://near-pedia.xyz/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http unitynodes-near-pedia 'https://near-pedia.xyz/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "unitynodes-near-pedia": {
      "url": "https://near-pedia.xyz/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "unitynodes-near-pedia": {
      "type": "http",
      "url": "https://near-pedia.xyz/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.unitynodes-near-pedia]
url = "https://near-pedia.xyz/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "unitynodes-near-pedia": {
      "type": "remote",
      "url": "https://near-pedia.xyz/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add unitynodes-near-pedia --url 'https://near-pedia.xyz/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  unitynodes-near-pedia:
    url: "https://near-pedia.xyz/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "unitynodes-near-pedia": {
      "Transport": "http",
      "Url": "https://near-pedia.xyz/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add unitynodes-near-pedia -t streamable-http -u 'https://near-pedia.xyz/mcp'
```

### Other

```json
{
  "mcpServers": {
    "unitynodes-near-pedia": {
      "type": "http",
      "url": "https://near-pedia.xyz/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-09 (score 74, 0)

- [functional] Server version: 1.0.0 → 1.0.1
- [cosmetic] “list_videos” reworded the description of “channel”

### 2026-11-08 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (27)

### `search` (~144 tokens)

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.

Input parameters:

- `limit` (integer)
- `query` (string, required): Search query
- `type` (string)

### `get_discussion` (~134 tokens)

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.

Input parameters:

- `from_post` (integer): First post to return, for reading past the first 15. A URL ending in a post number starts there.
- `topic` (required): Topic number (42644) or its gov.near.org URL (https://gov.near.org/t/slug/42644).

### `get_doc` (~96 tokens)

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.

Input parameters:

- `id` (required): Doc page ID (from search/semantic_search results)

### `get_recent_changes` (~107 tokens)

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.

Input parameters:

- `days` (integer)
- `limit` (integer)

### `get_network_state` (~87 tokens)

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_validators` (~138 tokens)

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.

Input parameters:

- `account` (string): One validator pool account, e.g. astro-stakers.poolv1.near. Omit for the list.
- `limit` (integer): How many of the largest to list (default 20).

### `list_videos` (~144 tokens)

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.

Input parameters:

- `channel` (string): Channel name filter, one of NEAR Protocol and NEAR DevHub. Case-insensitive substring.
- `limit` (integer)
- `offset` (integer)
- `since` (string): Earliest published_at (ISO date, e.g. "2026-01-01"). Default: no lower bound.

### `semantic_search` (~144 tokens)

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.

Input parameters:

- `limit` (integer)
- `query` (string, required): Free-form question or phrase.
- `source_types` (array): Restrict to these source types. Omit for all.

### `list_blog_posts` (~217 tokens)

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.

Input parameters:

- `limit` (integer): How many posts to return. Default 20, max 50.
- `offset` (integer): Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.
- `query` (string): Words to look for in titles and text. Results come best match first.
- `source` (string): 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.

### `get_blog_post` (~166 tokens)

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.

Input parameters:

- `chars` (integer): Characters of text to return. Default 12000; raise it (max 200000) for the whole post, or set 0 for metadata only.
- `id` (string, required): Post id, as list_blog_posts gives it.
- `offset` (integer): Character position to start reading from, for a long post. The response names the offset that continues the read.

### `find_code_examples` (~134 tokens)

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".

Input parameters:

- `limit` (integer): Most examples to return (default 4).
- `topic` (string, required): What the code should do or use, e.g. "ft_transfer_call", "cross contract call", "near-api-js view function".

### `get_breaking_changes` (~242 tokens)

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?".

Input parameters:

- `from_version` (string, required): The version you are on, e.g. "5.1.0".
- `product` (string, required): 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".
- `to_version` (string, required): The version you move to, e.g. "7.4.0". A prerelease target includes prereleases.

### `find_known_issues` (~140 tokens)

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.

Input parameters:

- `description` (string, required): What you're seeing, in short prose. For an error message, explain_error answers with its cause and fix.
- `limit` (integer): Max rows per source (default 5).

### `check_deprecation` (~185 tokens)

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.

Input parameters:

- `limit` (integer): Most entries to return (default 3).
- `name` (string, required): Package, crate, repository (owner/repo or GitHub URL), RPC method, identifier, config key or endpoint host.

### `resolve_package` (~139 tokens)

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.

Input parameters:

- `package` (string, required): 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".

### `explain_error` (~110 tokens)

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.

Input parameters:

- `error_text` (string, required): The error message or response, as printed.

### `get_standard` (~119 tokens)

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.

Input parameters:

- `nep` (string, required): A NEP number ("141", "NEP-141") for its full text, or words to search titles and texts.

### `get_contract_info` (~128 tokens)

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.

Input parameters:

- `account_id` (string, required): The account, e.g. "intents.near", "token.rhealab.near".
- `network` (string): Default mainnet.

### `check_code` (~202 tokens)

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.

Input parameters:

- `code` (string, required): The file contents, up to 100000 characters.
- `filename` (string): The file name, e.g. "contract.ts", "Cargo.toml", "package.json". Picks the language.
- `language` (string): Overrides the language detected from the file name or content.

### `get_protocol_status` (~134 tokens)

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.

Input parameters:

- `network` (string): One network; both when omitted.

### `list_proposals` (~147 tokens)

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.

Input parameters:

- `limit` (integer): Most proposals to return (default 10).
- `query` (string): Text to find in the title or description.
- `status` (string): Contract status, e.g. "Voting" or "Succeeded".

### `get_proposal` (~104 tokens)

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").

Input parameters:

- `proposal` (string, required): On-chain id ("27", "#27") or HSP number ("HSP-027", "HSP 27").

### `find_project` (~221 tokens)

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".

Input parameters:

- `category` (string): NEAR Catalog category, any case, singular or plural ("wallets", "DeFi", "DEX", "Validator"). An unknown one returns the list of categories.
- `limit` (integer): Most projects to return (default 5; up to 50 for a whole category).
- `query` (string, required): Project name or words for what it does ("lending", "intents swap"); empty to list.

### `list_incidents` (~176 tokens)

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".

Input parameters:

- `limit` (integer): Most incidents to return (default 10).
- `project` (string): NEAR Catalog slug, e.g. "ref-finance".
- `query` (string): Text in the name, technique or description, e.g. "oracle".
- `relevance` (string): Default "near".

### `get_incident` (~64 tokens)

One NEAR ecosystem security incident in full, with DefiLlama's description, by the id list_incidents prints (e.g. "llama-1546-2026-04-16").

Input parameters:

- `id` (string, required): Incident id from list_incidents.

### `get_partner` (~170 tokens)

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.

Input parameters:

- `partner` (string, required): Partner id, name, contract account or catalog slug, e.g. "near-intents".

### `get_radar` (~264 tokens)

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".

Input parameters:

- `level` (string): Severity floor. "critical" and "important" return only that level; "ecosystem" is the low-severity feed; "all" (default) returns every live alert.
- `limit` (integer): How many alerts to return, most severe and most recent first. Default 25.
- `offset` (integer): Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/unitynodes-near-pedia/near-pedia#diagnostics

## Score history

- 2026-11-21: 80
- 2026-11-20: 79
- 2026-11-19: 79
- 2026-11-18: 78
- 2026-11-17: 78
- 2026-11-16: 78
- 2026-11-15: 77
- 2026-11-14: 77
- 2026-11-13: 76
- 2026-11-12: 76
- 2026-11-11: 75
- 2026-11-10: 75
- 2026-11-09: 74
- 2026-11-08: 74
- 2026-11-07: 73
- 2026-11-06: 73
- 2026-11-05: 66

## Common questions

### What is the NEARpedia MCP server?

NEARpedia is an MCP server listed in the public MCP registry as io.github.UnityNodes/near-pedia. Live NEAR knowledge for agents: deprecations, breaking changes, protocol and contracts, dated. This page covers its hosted endpoint (https://near-pedia.xyz/mcp).

### Is the NEARpedia MCP server safe to use?

NEARpedia scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the NEARpedia MCP server expose?

NEARpedia exposes 27 tools: search, get_discussion, get_doc, get_recent_changes, get_network_state, and 22 more. Their descriptions and schemas cost roughly 4,056 tokens of context every time the server is loaded.

### Does the NEARpedia MCP server require authentication?

No. We connected to NEARpedia without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the NEARpedia MCP server still maintained?

NEARpedia is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the NEARpedia MCP server?

VerifyMCP ran 13 checks on NEARpedia, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://near-pedia.xyz/mcp
- Repository: https://github.com/UnityNodes/near-pedia
- Website: https://near-pedia.xyz/for-ai
- Changelog RSS feed: https://verifymcp.io/servers/unitynodes-near-pedia/near-pedia.xml
- Changelog JSON feed: https://verifymcp.io/servers/unitynodes-near-pedia/near-pedia/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/unitynodes-near-pedia/near-pedia.json
- HTML version of this page: https://verifymcp.io/servers/unitynodes-near-pedia/near-pedia
