MCP servers observed by Lowdown
org.r3js/r3 MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-10 to 2026-11-19) (Lowdown checks this server every 3 days); 80 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-16 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:org.r3js/r3
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:org.r3js/r3?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-19: the server answered initialize and tools/list.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 2 of 3 compared days.
- 2026-11-19: server version changed
- 2026-11-16: input or output schemas changed, descriptions changed, server version changed
- 2026-11-13: input or output schemas changed, descriptions changed, server version changed
What tools does it list?
80 tools on 2026-11-19:
r3_asset_deleter3_asset_sharer3_assets_unusedr3_audio_listr3_blender_copiesr3_blender_downloadr3_blender_draft_pushr3_blender_importr3_blender_listr3_blender_updater3_blender_uploadr3_bug_reportr3_bug_reports_miner3_code_readr3_code_writer3_component_addr3_component_boundsr3_component_readr3_component_renamer3_component_setr3_docs_listr3_docs_readr3_editor_add_componentr3_editor_capturer3_editor_coder3_editor_creater3_editor_deleter3_editor_inspectr3_editor_openr3_editor_runr3_editor_setr3_editor_set_preview_imager3_editor_stopr3_editor_undor3_entity_assignr3_entity_importr3_entity_listr3_entity_readr3_entity_save_templater3_entity_updater3_factory_listr3_factory_runr3_help_writer3_image_creater3_image_listr3_module_listr3_module_pinr3_module_readr3_module_usager3_module_writer3_preview_creater3_preview_remover3_project_changesr3_project_creater3_project_deleter3_project_listr3_project_loadr3_project_remixr3_project_renamer3_publish_liver3_publish_settings_readr3_publish_settings_setr3_release_listr3_release_restorer3_release_rollbackr3_roadmap_listr3_roadmap_suggestr3_roadmap_upvoter3_song_readr3_song_updater3_sound_creater3_sound_readr3_sound_updater3_terrain_heightr3_texture_applyr3_texture_creater3_texture_readr3_texture_updater3_unpublish_liver3_whoami
MCP Registry declaration
- Registry name:
org.r3js/r3 - Declared version: 3.209.0
- Status: active
- Declared hosts:
mcp.r3js.org
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:org.r3js/r3", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:org.r3js/r3?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).