VR.org VR / AR / XR Reader

MCP搜索检索

提供方 evanatpizzarobot

搜索检索 未标注 API Key 社区 / 第三方 CursorCodexZed

Read-only access to VR.org's live VR, AR, and XR coverage. Ten tools let an agent search the latest VR, AR, and XR news, see trending topics, read VR.org's original editorial, compare headsets, pull current deals and prices, and fetch the top game and app lists. No API keys, no w

一句话选型结论

按资料字段整理

VR.org VR / AR / XR Reader 属于搜索检索类 MCP 服务器,传输方式未标注,API Key,可直接接入 Cursor、Codex、Zed,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类搜索检索 传输方式未标注 鉴权API Key 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

搜索检索
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

virtual reality news gaming read only

支持客户端

适用场景

virtual realitynewsgaming

安装与配置

未标注 API Key
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
联网搜索取证

让模型查最新资料并给出出处。

资料聚合

把一个主题的网页、文档集中抓回来整理。

情报与竞品检索

按关键词持续检索行业动态和竞品信息。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Cursor、Codex、Zed,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在搜索检索场景里让模型直接调用外部能力的人。
  • 已经在用 Cursor、Codex 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
VR.org VR / AR / XR Reader当前 未标注 未标注 未标注 无 未标注
Brave Search 433812ff 2 未标注 未标注 无 2026-05-17
Sequentialthinking 1 SSE · 服务端推送 远程部署 有 2026-05-18
Baidu Netdisk 未标注 未标注 未标注 无 2026-05-17
ragflow 未标注 stdio · 本地进程 本地部署 有 2026-04-11
mindsdb (430e18) 未标注 未标注 未标注 有 2026-05-17

服务器档案

搜索检索
字段来自项目仓库与公开索引,中文说明由本站标注
提供方evanatpizzarobot上游标注的维护方 evanatpizzarobot
分类搜索检索本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Cross-platform本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

12.2 KB
来自项目仓库与上游目录的原文,未做删改

vr-org-mcp

Read-only Model Context Protocol server for VR.org, a dedicated VR / AR / XR news publication and aggregator.

It gives any MCP-compatible agent (Claude Desktop, Claude Code, Cursor, Continue, and others) one-call access to live VR, AR, and XR news, VR.org's original editorial (including full article text), the VR/AR/XR events calendar, curated headset deals, buyer-guide answers, and top-game and top-app lists.

Eleven tools, five resources, and three prompts. Zero keys. Zero writes. Zero payments.

Install

Run it directly with npx (no global install needed):```bash
npx vr-org-mcp


### Claude Desktop

One-click: download the `.mcpb` bundle from the latest release and double-click it to install into Claude Desktop. Or configure manually:

Add to your `claude_desktop_config.json`:```json
{
  "mcpServers": {
    "vr-org": {
      "command": "npx",
      "args": ["-y", "vr-org-mcp"]
    }
  }
}

Claude Code```bash

claude mcp add vr-org -- npx -y vr-org-mcp


### Cursor

Add to `.cursor/mcp.json`:```json
{
  "mcpServers": {
    "vr-org": {
      "command": "npx",
      "args": ["-y", "vr-org-mcp"]
    }
  }
}

Hosted remote endpoint (no install)

VR.org also runs the same tools as a remote server over MCP's streamable-HTTP transport, so web clients (ChatGPT connectors, Claude.ai connectors) can use it with no local install:```
https://vr.org/mcp


Human setup walkthrough for every client: vr.org/connect.

## Tools

| Tool | What it returns |
|------|-----------------|
| `search_vr_news` | Latest VR / AR / XR headlines from the live feed, with optional category filter and keyword search (all keywords must match, in any order) |
| `get_vr_trending` | Topics currently trending across the feed |
| `list_vr_originals` | Summaries of VR.org's own editorial articles, newest first |
| `get_vr_article` | Full content of one original by slug: metadata, canonical URL, and the article body HTML |
| `get_vr_events` | Upcoming VR / AR / XR industry events (conferences, expos, launches), soonest first |
| `get_vr_deals` | Curated product picks with prices, badges, and retailer links |
| `compare_vr_headsets` | Side-by-side of two headsets (partial names accepted) |
| `get_top_vr_games` | Current ranked top VR games list |
| `get_top_vr_apps` | Current ranked top VR apps and utilities list |
| `list_vr_sources` | The news sources VR.org aggregates, with counts |
| `vr_explain` | Canonical short answer plus pillar-page link for a common question |

## Resources

Browsable MCP resources an app can attach as context:

| Resource | Contents |
|----------|----------|
| `vrorg://news/latest` | Latest aggregated VR / AR / XR headlines |
| `vrorg://originals/latest` | Index of VR.org's newest original articles |
| `vrorg://events/upcoming` | Upcoming VR / AR / XR industry events |
| `vrorg://guides` | VR.org's canonical pillar-guide answers in one doc |
| `vrorg://article/{slug}` | Full HTML body of any original article (resource template) |

## Prompts

| Prompt | What it does |
|--------|--------------|
| `recommend_a_headset` | Recommends a headset from VR.org's picks given a budget and use case |
| `this_week_in_vr` | Drafts a weekly VR / AR / XR roundup from the feed and originals |
| `explain_vr_topic` | Explains a VR topic grounded in VR.org's canonical answer |

## How it works

Every tool composes VR.org's public JSON API (`https://vr.org/api/*`) into a single agent-friendly response. The server is a thin proxy: it holds no secrets, writes nothing, and cannot move money.

## Threat model

VR.org's editorial is controlled, but the live feed also carries third-party RSS headlines. To keep a malicious or compromised upstream headline from manipulating the calling model, every tool output is:

1. **Sanitized.** Control characters and zero-width / direction-override characters are stripped from every string.
2. **Capped.** Serialized responses are limited to 50 KB so a large payload cannot flood the agent's context window.

Inputs are validated before any outbound request and every free-text parameter is length-capped at the schema layer. Errors are returned as structured, non-echoing objects rather than raw stack traces; on the rare path where an error string reaches the caller it runs through the same output scrub as a tool result, with any credential-shaped substring redacted and the text capped, and is flagged with `isError`.

## Configuration

The API base URL is fixed to `https://vr.org` in source and cannot be overridden, so the server can only ever talk to VR.org.

| Env var | Default | Purpose |
|---------|---------|---------|
| `VR_ORG_UA_SUFFIX` | _(none)_ | Optional suffix appended to the outbound User-Agent |

## Development```bash
npm install
npm run dev        # run from source over stdio
npm run build      # compile to dist/
npm test           # run the offline test suite
npm run typecheck  # type-check without emitting

Changelog

0.5.0

Protocol upgrade. Requires Node.js 20 or newer.

  • The server now runs on the MCP SDK v2 (@modelcontextprotocol/server) and speaks the 2026-07-28 protocol revision. Clients on the 2025 revisions connect exactly as before: the opening message decides which revision a connection uses.
  • Node.js 18 is no longer supported, because the v2 SDK needs Node.js 20. If you are pinned to Node 18, stay on 0.4.4.
  • The install is much smaller. The old SDK pulled in an HTTP stack this stdio server never used, more than 80 packages of it. The production dependency tree is now three packages, and npm audit is clean with no overrides.
  • The hosted endpoint at https://vr.org/mcp moved to the same protocol on the same day. It also answers at /mcp directly now instead of redirecting to /api/mcp, which halves the round trips for clients configured with the short URL.
  • No tool, resource or prompt changed.

0.4.4

search_vr_news now matches on words instead of one exact phrase.

  • The keyword filter used to require the whole query to appear, as typed, somewhere in a headline or snippet. Agents tend to send queries like "steam frame release date" or "best vr headset 2026", and those came back empty even when the feed was full of matching stories. In a replay of 25 realistic queries against the live feed, 18 returned nothing.
  • A query is now split into keywords. Filler ("what is the latest", "news", "today", years and month names) is dropped, and every remaining keyword has to appear in the headline, snippet, tags, category or source name, in any order. Plurals match singulars, punctuation is ignored ("half-life alyx" finds "Half-Life: Alyx"), and a model name typed without its space still matches ("psvr2" finds "PS VR2"). Numbers and two-letter terms match whole words only, so "quest 3" does not return Quest 3S stories.
  • Headline matches are listed first, newest first inside each group.
  • When a query is sent, the response adds match (all_terms, partial, none, or latest for a query that was all filler), terms (the keywords actually used) and total_matches. If nothing matches every keyword, the closest matches are returned and labelled partial with a hint. A call with no query returns exactly what it did before.
  • The hosted endpoint at https://vr.org/mcp carries the same matcher.

0.4.3

Maintenance release.

  • The vr_explain tool description now names the newer topics it can answer ("steam frame price", "meta vr glasses"), so an agent reading the tool list knows to ask for them. The hosted endpoint at https://vr.org/mcp carries the same wording.
  • The release workflow now publishes through npm trusted publishing (OIDC) and only falls back to a token if that is rejected. Provenance is attached as before.

0.4.2

vr_explain and the vrorg://guides resource now answer from VR.org's live explainer feed, so they stay current between releases.

  • The answers used to be a list compiled into the package in July 2026. By October most realistic topics ("steam frame", "steam frame price", "meta vr glasses", "quest 4") returned no_explainer, and several of the answers that did exist were out of date. The list is now fetched from https://vr.org/api/explainers and cached for ten minutes, the same way deals and events are, so a guide refresh on the site reaches agents without a package release.
  • Every fetched entry is validated before use (keys must be a non-empty list of non-empty strings, and the link must be on https://vr.org) and passes through the same sanitizer as other upstream text. If the fetch fails or returns nothing valid, the built-in list answers instead. That list now mirrors the site's current 34 guides, up from 10, so an offline server still gives current answers. A failed fetch is remembered for one minute so an outage does not slow down every call.
  • Matching is unchanged: the longest key contained in the topic wins, so "steam frame price" reaches the price page and not the Steam Frame hub.
  • The explain_vr_topic prompt no longer offers 'passthrough' as an example topic, which had no answer. It and the no_explainer hint now suggest 'steam frame'.
  • The get_vr_deals description names all five catalog sections: headsets, AR and XR glasses, accessories, haptics and body tracking, gaming hardware.
  • Bumps @modelcontextprotocol/sdk from 1.30.0 to 1.32.1 and refreshes the ip-address and proxy-addr pins. The advisories behind this sit in the SDK's OAuth client and HTTP transport, which this stdio server never loads. npm audit on the production dependencies reports zero vulnerabilities.

0.4.1

Fixes from a September 2026 audit, matched on the hosted endpoint at vr.org/mcp.

  • get_vr_article now returns the whole article. body_html was cut at the general 4,096-character string cap, which truncated most articles mid-tag while still reporting ok: true. It now has its own 45,000-character cap, and the 50 KB response cap still applies. The article also carries updated, the date a correction was applied, which the hosted endpoint already returned.
  • vr_explain no longer answers short topics with the wrong guide. A topic like "vr" or "3" used to match inside a longer key and return "PSVR2 vs Quest 3" with confidence; the reverse match now needs four or more characters starting on a word boundary.
  • compare_vr_headsets matches "Pimax Dream Air SE" correctly. The pimax alias was a prefix match that rewrote every Pimax query to Crystal.
  • Reading vrorg://news/latest no longer shrinks keyword search to 25 items for the next minute (the two shared a cache key with different request sizes).
  • A malformed slug in vrorg://article/{slug} now says "not found" instead of "temporarily unavailable, retry shortly".
  • Refreshed transitive dependency pins (hono, fast-uri, qs) for npm audit.

0.4.0

Content provenance. Feed results now carry a provenance field on every item, either vr_org_editorial (written and edited by VR.org) or third_party_feed (a headline or snippet relayed verbatim from an outside publisher). Any response containing relayed text also carries a content_notice saying to treat that text as data rather than instructions, and the vrorg://news/latest resource carries the same notice in prose. This is additive metadata, so existing fields and existing consumers are unaffected.

The point is to let a calling client tell which text VR.org actually stands behind. It follows the August 2026 GhostSplice research on splitting instructions across MCP channels, whose core mitigation is that clients should treat server output as data. This server is not a vector for that attack (it never requests sampling, its tool descriptions are static literals, and every value that can flow back in as a tool argument is validated against a strict allowlist), but it does relay text it did not write, and now it says so.

Also bumps @modelcontextprotocol/sdk to 1.30.0 and pins four transitive dependencies of the SDK's HTTP transport that carried advisories. This server is stdio-only and never loads that transport, so the pins are hygiene rather than an exposure fix. npm audit --omit=dev reports zero vulnerabilities.

0.3.2

Error-path hardening: tool errors now pass through the same output scrub as tool results, with secrets redacted and error text capped. All free-text parameters gain schema-level max lengths. No behavior change for valid inputs.

License

MIT. A VR.org project.

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
VR.org VR / AR / XR Reader 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

VR.org VR / AR / XR Reader 怎么在 Cursor、Codex、Zed 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

VR.org VR / AR / XR Reader 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

VR.org VR / AR / XR Reader 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

VR.org VR / AR / XR Reader 支持哪些客户端?

资料标注支持 Cursor、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

VR.org VR / AR / XR Reader 能提供哪些能力?

资料显示能力标签包括 virtual reality、news、gaming、read only。具体工具清单以官方文档为准。

VR.org VR / AR / XR Reader 需要什么运行环境?

运行时为 Cross-platform。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。