Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

NEARpedia

REMOTE · NEAR-PEDIA.XYZ

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

Available components

+3 this week 80 Trust /100

Last scanned (13 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Code Search and Documentation

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 88% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 27 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 27 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 16 Nov 26 +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.

  • 14 Nov 26 +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.

  • 12 Nov 26 +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.

  • 10 Nov 26 +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.

  • 9 Nov 26 0
    • Server version: 1.0.0 → 1.0.1 functional
    • “list_videos” reworded the description of “channel” cosmetic
  • 8 Nov 26 +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.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://near-pedia.xyz/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=near-pedia.xyz CN=YE2,O=Let's Encrypt,C=US 2 Nov 2026 31 Jan 2027 ECDSA 256 ECDSA-SHA384 53f67b6ae4007a707d1ca7152b980c51818
SANs: *.near-pedia.xyz, near-pedia.xyz
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of near-pedia.xyz. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
xyz. DS published 3599, 18130 8, 8 Verified
near-pedia.xyz. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://near-pedia.xyz/mcp Verified 200
http (plaintext) http://near-pedia.xyz/mcp HTTPS enforced 308 https://near-pedia.xyz/mcp
MCP tools · 27 exposed · ~4,056 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_code ~202

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.

NameTypeReqDescription
codestringyesThe file contents, up to 100000 characters.
filenamestring–The file name, e.g. "contract.ts", "Cargo.toml", "package.json". Picks the language.
languagestring–Overrides the language detected from the file name or content.

No output schema declared.

No examples provided.

check_deprecation ~185

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.

NameTypeReqDescription
limitinteger–Most entries to return (default 3).
namestringyesPackage, crate, repository (owner/repo or GitHub URL), RPC method, identifier, config key or endpoint host.

No output schema declared.

No examples provided.

explain_error ~110

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.

NameTypeReqDescription
error_textstringyesThe error message or response, as printed.

No output schema declared.

No examples provided.

find_code_examples ~134

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

NameTypeReqDescription
limitinteger–Most examples to return (default 4).
topicstringyesWhat the code should do or use, e.g. "ft_transfer_call", "cross contract call", "near-api-js view function".

No output schema declared.

No examples provided.

find_known_issues ~140

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.

NameTypeReqDescription
descriptionstringyesWhat you're seeing, in short prose. For an error message, explain_error answers with its cause and fix.
limitinteger–Max rows per source (default 5).

No output schema declared.

No examples provided.

find_project ~221

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

NameTypeReqDescription
categorystring–NEAR Catalog category, any case, singular or plural ("wallets", "DeFi", "DEX", "Validator"). An unknown one returns the list of categories.
limitinteger–Most projects to return (default 5; up to 50 for a whole category).
querystringyesProject name or words for what it does ("lending", "intents swap"); empty to list.

No output schema declared.

No examples provided.

get_blog_post ~166

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.

NameTypeReqDescription
charsinteger–Characters of text to return. Default 12000; raise it (max 200000) for the whole post, or set 0 for metadata only.
idstringyesPost id, as list_blog_posts gives it.
offsetinteger–Character position to start reading from, for a long post. The response names the offset that continues the read.

No output schema declared.

No examples provided.

get_breaking_changes ~242

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

NameTypeReqDescription
from_versionstringyesThe version you are on, e.g. "5.1.0".
productstringyesOne 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_versionstringyesThe version you move to, e.g. "7.4.0". A prerelease target includes prereleases.

No output schema declared.

No examples provided.

get_contract_info ~128

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.

NameTypeReqDescription
account_idstringyesThe account, e.g. "intents.near", "token.rhealab.near".
networkstring–Default mainnet.

No output schema declared.

No examples provided.

get_discussion ~134

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.

NameTypeReqDescription
from_postinteger–First post to return, for reading past the first 15. A URL ending in a post number starts there.
topic–yesTopic number (42644) or its gov.near.org URL (https://gov.near.org/t/slug/42644).

No output schema declared.

No examples provided.

get_doc ~96

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.

NameTypeReqDescription
id–yesDoc page ID (from search/semantic_search results)

No output schema declared.

No examples provided.

get_incident ~64

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

NameTypeReqDescription
idstringyesIncident id from list_incidents.

No output schema declared.

No examples provided.

get_network_state ~87

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_partner ~170

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.

NameTypeReqDescription
partnerstringyesPartner id, name, contract account or catalog slug, e.g. "near-intents".

No output schema declared.

No examples provided.

get_proposal ~104

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

NameTypeReqDescription
proposalstringyesOn-chain id ("27", "#27") or HSP number ("HSP-027", "HSP 27").

No output schema declared.

No examples provided.

get_protocol_status ~134

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.

NameTypeReqDescription
networkstring–One network; both when omitted.

No output schema declared.

No examples provided.

get_radar ~264

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

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

No output schema declared.

No examples provided.

get_recent_changes ~107

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.

NameTypeReqDescription
daysinteger––
limitinteger––

No output schema declared.

No examples provided.

get_standard ~119

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.

NameTypeReqDescription
nepstringyesA NEP number ("141", "NEP-141") for its full text, or words to search titles and texts.

No output schema declared.

No examples provided.

get_validators ~138

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.

NameTypeReqDescription
accountstring–One validator pool account, e.g. astro-stakers.poolv1.near. Omit for the list.
limitinteger–How many of the largest to list (default 20).

No output schema declared.

No examples provided.

list_blog_posts ~217

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.

NameTypeReqDescription
limitinteger–How many posts to return. Default 20, max 50.
offsetinteger–Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.
querystring–Words to look for in titles and text. Results come best match first.
sourcestring–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.

No output schema declared.

No examples provided.

list_incidents ~176

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

NameTypeReqDescription
limitinteger–Most incidents to return (default 10).
projectstring–NEAR Catalog slug, e.g. "ref-finance".
querystring–Text in the name, technique or description, e.g. "oracle".
relevancestring–Default "near".

No output schema declared.

No examples provided.

list_proposals ~147

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.

NameTypeReqDescription
limitinteger–Most proposals to return (default 10).
querystring–Text to find in the title or description.
statusstring–Contract status, e.g. "Voting" or "Succeeded".

No output schema declared.

No examples provided.

list_videos ~144

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.

NameTypeReqDescription
channelstring–Channel name filter, one of NEAR Protocol and NEAR DevHub. Case-insensitive substring.
limitinteger––
offsetinteger––
sincestring–Earliest published_at (ISO date, e.g. "2026-01-01"). Default: no lower bound.

No output schema declared.

No examples provided.

resolve_package ~139

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.

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

No output schema declared.

No examples provided.

search ~144

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.

NameTypeReqDescription
limitinteger––
querystringyesSearch query
typestring––

No output schema declared.

No examples provided.

semantic_search ~144

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.

NameTypeReqDescription
limitinteger––
querystringyesFree-form question or phrase.
source_typesarray–Restrict to these source types. Omit for all.

No output schema declared.

No examples provided.

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.

remote · near-pedia.xyz

# add to Claude Code
claude mcp add --transport http unitynodes-near-pedia 'https://near-pedia.xyz/mcp'
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.