MCP servers › io.github.UnityNodes › near-pedia

MCP server · registry snapshot 2026-11-06 · last tested 2026-11-06

near-pedia MCP server

Registry name io.github.UnityNodes/near-pedia

by UnityNodes · GitHub account (the registry's namespace rule)repository: same ownerSource ↗Website ↗

Live NEAR knowledge for agents: deprecations, breaking changes, protocol and contracts, dated — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-11-06version 1.0.0TypeScriptstreamable HTTP27 tools

Summary

io.github.UnityNodes/near-pedia is a remote MCP server listed in the official MCP registry at version 1.0.0, under the namespace of the GitHub account UnityNodes. Its linked repository, github.com/UnityNodes/near-pedia, belongs to the same GitHub account. On 2026-11-06 ProtocolProbe connected to it in read-only mode and read its inventory: 27 tools, 0 resources and 0 prompts.

Record checks

4 of 5 record checks met · 4 do not apply

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
not met: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Your own values: none declared (not a guarantee)
Sign-in: none needed to open a session
Repository: public
Tools: 27
Last tested: 2026-11-06

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-06 (near-pedia.xyz), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.0).

Add to your client

How fresh this is

Live-tested: yes, a real session (not a text-only review)
Last tested: 2026-11-06
Mode: read-only (no tool calls)
Latest version: 1.0.0, published 2026-11-05 (registry, as of the 2026-11-06 snapshot)
First listed version: 2026-11-05 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-11-06
Package and repository: checked 2026-11-06
Engine: mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-05, listed on 2026-11-06 with version 1.0.0 (published 2026-11-05).

Source: the official MCP Registry list on 2026-11-05 and on 2026-11-06.

What it is

What does this server offer?

Observed inventory

27tools

0resources

0prompts

None of its 27 tools are described as changing anything. For 27 the reading was uncertain, so no mark is shown.

searchon 948 other servers
“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 rele…”
Publisher declares: read-only yes · destructive no · idempotent yes
3 inputs, 1 required
- querystringrequired“Search query”
- typestring
- limitinteger
get_discussionon 9 other servers
“Read a gov.near.org forum thread in full: House of Stake proposals and their debate, validator threads, incident write-ups, developer standards.”
Publisher declares: read-only yes · destructive no · idempotent yes
2 inputs, 1 required
- topicinteger or stringrequired“Topic number (42644) or its gov.near.org URL (https://gov.near.org/t/slug/42644).”
- from_postinteger“First post to return, for reading past the first 15.”
get_docon 46 other servers
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes
1 input, 1 required
- idinteger or stringrequired“Doc page ID (from search/semantic_search results)”
get_recent_changeson 20 other servers
“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, …”
Publisher declares: read-only yes · destructive no · idempotent yes
2 inputs
- daysinteger
- limitinteger
get_network_stateon 3 other servers
“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…”
Publisher declares: read-only yes · destructive no · idempotent yes
Takes no inputs.
get_validators
“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 o…”
Publisher declares: read-only yes · destructive no · idempotent yes
2 inputs
- accountstring“One validator pool account, e.g.”
- limitinteger“How many of the largest to list (default 20).”
list_videoson 19 other servers
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes
4 inputs
- channelstring“Channel name filter, one of NEAR Protocol, NEAR DevHub, NEAR AI.”
- sincestring“Earliest published_at (ISO date, e.g.”
- limitinteger
- offsetinteger
semantic_searchon 31 other servers
“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 repositor…”
Publisher declares: read-only yes · destructive no · idempotent yes
3 inputs, 1 required
- querystringrequired“Free-form question or phrase.”
- source_typesarray“Restrict to these source types.”
- limitinteger
list_blog_postson 43 other servers
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes
4 inputs
- sourcestring“Which tab: blog (Blog), news (News), press-release (Press), partner-news (Partner press), third-party (Third-party).”
- querystring“Words to look for in titles and text.”
- limitinteger“How many posts to return.”
- offsetinteger“Skip this many before returning, for paging past the limit.”
get_blog_poston 22 other servers
“Get one blog post by the id list_blog_posts or search gave: title, kind, author, date and the text.”
Publisher declares: read-only yes · destructive no · idempotent yes
3 inputs, 1 required
- idstringrequired“Post id, as list_blog_posts gives it.”
- charsinteger“Characters of text to return.”
- offsetinteger“Character position to start reading from, for a long post.”
find_code_exampleson 2 other servers
“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 deprecate…”
Publisher declares: read-only yes · destructive no · idempotent yes
2 inputs, 1 required
- topicstringrequired“What the code should do or use, e.g.”
- limitinteger“Most examples to return (default 4).”
get_breaking_changeson 7 other servers
“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_UPGRA…”
Publisher declares: read-only yes · destructive no · idempotent yes
3 inputs, 3 required
- productstringrequired“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.”
- from_versionstringrequired“The version you are on, e.g.”
- to_versionstringrequired“The version you move to, e.g.”

Show 15 more tools

find_known_issueson 2 other servers
“Surface known UNRESOLVED problems matching a free-text description: forum threads with zero replies but high views, plus open GitHub issues.”
Publisher declares: read-only yes · destructive no · idempotent yes
2 inputs, 1 required
- descriptionstringrequired“What you're seeing, in short prose.”
- limitinteger“Max rows per source (default 5).”
check_deprecationon 3 other servers
“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 eve…”
Publisher declares: read-only yes · destructive no · idempotent yes
2 inputs, 1 required
- namestringrequired“Package, crate, repository (owner/repo or GitHub URL), RPC method, identifier, config key or endpoint host.”
- limitinteger“Most entries to return (default 3).”
resolve_packageon 2 other servers
“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 …”
Publisher declares: read-only yes · destructive no · idempotent yes
1 input, 1 required
- packagestringrequired“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_erroron 10 other servers
“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 do…”
Publisher declares: read-only yes · destructive no · idempotent yes
1 input, 1 required
- error_textstringrequired“The error message or response, as printed.”
get_standardon 11 other servers
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes
1 input, 1 required
- nepstringrequired“A NEP number ("141", "NEP-141") for its full text, or words to search titles and texts.”
get_contract_infoon 5 other servers
“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 envi…”
Publisher declares: read-only yes · destructive no · idempotent yes
2 inputs, 1 required
- account_idstringrequired“The account, e.g.”
- networkstring“Default mainnet.”
check_codeon 7 other servers
“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, de…”
Publisher declares: read-only yes · destructive no · idempotent yes
3 inputs, 1 required
- codestringrequired“The file contents, up to 100000 characters.”
- filenamestring“The file name, e.g.”
- languagestring“Overrides the language detected from the file name or content.”
get_protocol_status
“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 pr…”
Publisher declares: read-only yes · destructive no · idempotent yes
1 input
- networkstring“One network; both when omitted.”
list_proposalson 17 other servers
“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…”
Publisher declares: read-only yes · destructive no · idempotent yes
3 inputs
- statusstring“Contract status, e.g.”
- querystring“Text to find in the title or description.”
- limitinteger“Most proposals to return (default 10).”
get_proposalon 8 other servers
“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 …”
Publisher declares: read-only yes · destructive no · idempotent yes
1 input, 1 required
- proposalstringrequired“On-chain id ("27", "#27") or HSP number ("HSP-027", "HSP 27").”
find_project
“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 in…”
Publisher declares: read-only yes · destructive no · idempotent yes
3 inputs, 1 required
- querystringrequired“Project name or words for what it does ("lending", "intents swap"); empty to list.”
- categorystring“NEAR Catalog category, any case, singular or plural ("wallets", "DeFi", "DEX", "Validator").”
- limitinteger“Most projects to return (default 5; up to 50 for a whole category).”
list_incidentson 14 other servers
“Security incidents in the NEAR ecosystem from DefiLlama's hacks dataset, newest first: date, amount lost and returned, technique, chains and source.”
Publisher declares: read-only yes · destructive no · idempotent yes
4 inputs
- relevancestring“Default "near".”
- querystring“Text in the name, technique or description, e.g.”
- projectstring“NEAR Catalog slug, e.g.”
- limitinteger“Most incidents to return (default 10).”
get_incidenton 13 other servers
“One NEAR ecosystem security incident in full, with DefiLlama's description, by the id list_incidents prints (e.g.”
Publisher declares: read-only yes · destructive no · idempotent yes
1 input, 1 required
- idstringrequired“Incident id from list_incidents.”
get_partneron 2 other servers
“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 wit…”
Publisher declares: read-only yes · destructive no · idempotent yes
1 input, 1 required
- partnerstringrequired“Partner id, name, contract account or catalog slug, e.g.”
get_radaron 7 other servers
“Get the NEAR Radar: what is changing on NEAR now and needs action, and nothing that has already resolved.”
Publisher declares: read-only yes · destructive no · idempotent yes
3 inputs
- levelstring“Severity floor.”
- limitinteger“How many alerts to return, most severe and most recent first.”
- offsetinteger“Skip this many before returning, for paging past the limit.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-06.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description: 88% of 58
Tools with a description: 100% of 27
Typical description length: 403 characters

The tool set

Counted from the listing

Tools: 27
Size of the list: about 6,499 tokens for an agent to load (characters ÷ 4)
Naming: 26 of 27 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 27 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-06 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://near-pedia.xyz/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

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

VS Code · .vscode/mcp.json

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

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"near-pedia","type":"http","url":"https://near-pedia.xyz/mcp"}'

Claude Code

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

Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)

{
  "mcpServers": {
    "near-pedia": {
      "type": "streamableHttp",
      "url": "https://near-pedia.xyz/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}

Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project

{
  "mcpServers": {
    "near-pedia": {
      "httpUrl": "https://near-pedia.xyz/mcp"
    }
  }
}

OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project

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

Zed · Zed settings file (command: zed: open settings file)

{
  "context_servers": {
    "near-pedia": {
      "url": "https://near-pedia.xyz/mcp"
    }
  }
}

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://near-pedia.xyz/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint near-pedia.xyz/mcp	Session opened	matches	our test · 2026-11-06
No credential declared as required	Opened a session without any credential	matches	our test · 2026-11-06
Repository github.com/UnityNodes/near-pedia	Opens publicly	matches	api.github.com · 2026-11-06

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.UnityNodes · 3 servers
GitHub owner: an organization (UnityNodes)

Repository: github.com/UnityNodes/near-pedia
Stars: 0
Repository age: 0–30 days
Last push: 0–30 days ago
Archived: no
Security policy: none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-11-06; security policy read from GitHub · 2026-11-06.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 0 stars (ranked from 10)

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-06 (security policy 2026-11-06). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.github.UnityNodes/near-pedia

Answered from the data above

Who publishes io.github.UnityNodes/near-pedia?

The registry ties the namespace io.github.UnityNodes to the GitHub account UnityNodes; only its owner can publish under it. Its linked repository, github.com/UnityNodes/near-pedia, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.UnityNodes/near-pedia safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.github.UnityNodes/near-pedia need an API key or sign-in?

It opened a session without any credential on 2026-11-06. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.github.UnityNodes/near-pedia been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.

Does io.github.UnityNodes/near-pedia publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of io.github.UnityNodes/near-pedia?

In github.com/UnityNodes/near-pedia, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-06

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 2

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised

Not run, with the reason · 12

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 4

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-11-06, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
1,745 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 27 tools, 0 resources, 0 prompts.
5,613 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

pending: added in a later update

listed 2026-11-06; not classified yet

Pricing modelAI-classified

pending: added in a later update

the website is not read yet

Programming language

TypeScript

api.github.com · 2026-11-06

Hosting type

remote (hosted by the publisher)

registry · 2026-11-06

MCP capability

tools

our test · 2026-11-06

Transport

streamable HTTP

registry · 2026-11-06

Required credentials

none declared

registry · 2026-11-06 · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-11-06

Lifecycle status

active

registry · 2026-11-06

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

owner: an organization · repository age: 0–30 days · stars: 0–9

api.github.com · 2026-11-06

Maintenance

active

api.github.com · 2026-11-06

Environment

the publisher's infrastructure

where it runs, from the hosting type · 2026-11-06

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.UnityNodes/near-pedia: MCP server record.” Data checked 2026-11-06. https://protocolprobe.com/mcp/servers/io.github.UnityNodes/near-pedia

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.UnityNodes/near-pedia)](https://protocolprobe.com/mcp/servers/io.github.UnityNodes/near-pedia)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology