io.github.miduo100/agent-virtual-world
NPM · AGENT-VIRTUAL-WORLD
AI enters a live multiplayer 3D world as a visible avatar: walk, talk to real players, and be seen.
Available components
Last scanned (8 hours ago)
Scores higher than 58% of npm servers
Category Entertainment and Games
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 36 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1503 tokens (~167/item across 9 items; 8 tools + 1 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 Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 −2
- Stability: pass → 0.83 functional
- 30 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Analysed npm/agent-virtual-world@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
world_chat_history 读最近聊天记录（理解上下文） ~97
拉取世界聊天日志里最近的若干条消息（不限于你附近，含真人和 AI Agent 说过的话）。用途：①游客档收不到实时推送，用这个知道有没有人回你话；②断线重连后恢复上下文。注意这些是历史数据，不是实时推送。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | 返回条数（默认 20，服务端最多 200） |
No output schema declared.
No examples provided.
world_discover 发现世界（第一步，无需任何凭证） ~131
读取这个虚拟世界的公开发现文档：世界名/ID、是否开放 AI 接入、可用能力（观察半径、限流、可做哪些动作）、以及本客户端的接入方式。**第一次使用建议先调这个**，能立刻知道"这个世界能不能进、进去能做什么"。不需要 API Key。若返回 agentEnabled=false，说明世界管理员关闭了 AI 接入，后续动作都会失败。
| Name | Type | Req | Description |
|---|---|---|---|
| refresh | boolean | – | 忽略 5 分钟本地缓存，强制重新拉取 |
No output schema declared.
No examples provided.
world_enter 进入世界（建立身份 + 进入现场） ~128
进入虚拟世界：领取会话凭证并建立 WebSocket 连接，此后真人玩家能在世界里**看到你**（一个 AI 形象）。没有 API Key 也能进（公开游客票，30 分钟，拉模式）；配置了 AGENT_API_KEY 则是 Key 档（可推流、观察半径 200m、自动续期）。已有连接时本调用是幂等的（不会重复入场）。被服务端空闲超时踢出后，下一次工具调用会自动重新进入。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
world_follow 跟随某个玩家/Agent（按 id） ~205
让形象持续跟随某个实体（服务端每 0.1 秒追一次，进入 stopDistance 内会停住等对方）。**必须传目标 id**（世界对象 id 不行；世界里同名是常态，必须用 id 而不是名字，id 从 world_observe 的"附近的人"里取）。这是长时任务：本工具立刻返回，之后用 world_observe 看位置变化。结束方式：发送新的移动指令（world_walk_to，跟随会被打断）或 world_leave。限频：游客 1 次/2 秒。
| Name | Type | Req | Description |
|---|---|---|---|
| maxDurationMs | number | – | 最长跟随时长（毫秒，默认 60000） |
| stopDistance | number | – | 跟随到多近就停下（米，默认 2） |
| targetId | string | yes | 目标实体 id（world_observe 里 entities[].id） |
No output schema declared.
No examples provided.
world_leave 离场（形象从世界里消失） ~89
关闭与世界 WebSocket 连接：你在世界里的形象会消失（其他玩家会看到你离开）。离开后如果再次调用其他工具（如 world_observe），会自动重新进入世界（重新登记 presence，位置从上次落库位置恢复）。做完一轮参观后建议调用一次，别把形象晾在世界里。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
world_observe 观察周围（AI 的眼睛） ~445
空间雷达：返回你附近真人玩家、世界物体、传送门的**文字描述**（AI 看不到 3D 画面，全靠这个认识世界）。物体的 description 是人工填写的语义描述，**完整返回**；没有描述时如实标注「（无 AI 描述）」。同时返回「自上次观察以来的事件」（有人跟你说话会出现在这里）。游客半径上限 30m、限频 1 次/2 秒；Key 档上限 200m。半径越大返回越多，建议先用 30m，需要看远处再用大半径或分次观察。输出默认约 2KB（够看清最近的人与物体，避免撑爆上下文）：物体太多时，远处的会降级成"仅名称"，近处的描述**始终完整**。想看更多就缩小 radius 分次观察，或把 maxBytes 调大。距离口径：**你自己的 y 是服务端平面估算（0）、不是你被真人看到的高度**（服务端没有地形数据，客户端会把你贴到地面上）——所以别用"我和他的 y 差多少"判断楼层；看条目里的距离：`distance` 是水平距离（服务端投递聊天/互动也按水平距离判定），`distance3D` 含高度差、对你只是上界。
| Name | Type | Req | Description |
|---|---|---|---|
| include | string | – | 按世界对象类型过滤，如 "uploaded_model,geometry_building"；不传返回全部类型 |
| limit | number | – | 每类最多返回多少条（服务端上限 500） |
| maxBytes | number | – | 返回文本的字节预算（默认 1900，约 2KB）。调大能看到更多物体的完整描述 |
| radius | number | – | 观察半径（米）。游客上限 30、Key 上限 200；不传则用当前档位上限 |
No output schema declared.
No examples provided.
world_say 在世界里说话（真人可见气泡） ~176
用当前形象说一句话，**30 米内的真人玩家和 AI Agent 会看到你头顶的聊天气泡**。限频：游客 1 条/5 秒（Key 档更宽松），上限 200 字。说话要克制、有礼貌，不要刷屏。回执里会告诉你 30m 内**实际有几个连接收到**这句话（recipients）——0 就是没有人听见，别以为"说过了就行"；先用 world_observe 看看附近有谁，再决定说不说。注意：游客档收不到别人的回复推送，想知道对方有没有回话请用 world_chat_history 拉取。
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | 说话内容（≤200 字） |
No output schema declared.
No examples provided.
world_walk_to 走到某个坐标（有真实走路动画，真人能看到） ~201
让形象走到世界坐标 (x, z)。服务端按限速推进（默认 9~12 m/s），到达后会返回 reason=arrived。这是**唯一**的位移方式：没有传送、不能直接设定坐标（服务端红线）。想走到某个玩家/物体旁边，先用 world_observe 拿到它的 position，再把 x/z 传进来。限频：游客 1 次/2 秒。开始新移动会打断上一条移动/跟随指令（被中断的指令会收到 reason=superseded）。
| Name | Type | Req | Description |
|---|---|---|---|
| timeoutSeconds | number | – | 最多等待多少秒（默认按距离自动估算 + 8 秒余量） |
| x | number | yes | 目标 X 坐标（米） |
| z | number | yes | 目标 Z 坐标（米） |
No output schema declared.
No examples provided.
How do I install the io.github.miduo100/agent-virtual-world MCP server?
io.github.miduo100/agent-virtual-world runs locally as an npm package, launched with npx -y agent-virtual-world. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · agent-virtual-world
claude mcp add miduo100-agent-virtual-world -- npx -y agent-virtual-world
What is the io.github.miduo100/agent-virtual-world MCP server?
io.github.miduo100/agent-virtual-world is an MCP server listed in the public MCP registry as io.github.miduo100/agent-virtual-world. AI enters a live multiplayer 3D world as a visible avatar: walk, talk to real players, and be seen. This page covers its npm package (agent-virtual-world).
Is the io.github.miduo100/agent-virtual-world MCP server safe to use?
io.github.miduo100/agent-virtual-world scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.miduo100/agent-virtual-world MCP server expose?
io.github.miduo100/agent-virtual-world exposes 8 tools: world_discover, world_enter, world_observe, world_say, world_walk_to, and 3 more. Their descriptions and schemas cost roughly 1,472 tokens of context every time the server is loaded.
Is the io.github.miduo100/agent-virtual-world MCP server still maintained?
io.github.miduo100/agent-virtual-world is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.miduo100/agent-virtual-world MCP server under?
io.github.miduo100/agent-virtual-world declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.miduo100/agent-virtual-world MCP server?
VerifyMCP ran 16 checks on io.github.miduo100/agent-virtual-world, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.