immersivecommons vs com.lightres/booking
immersivecommons is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
immersivecommons is a plugin bundle for AI coding tools published by Immersive Commons. No marketplace we read lists it any more. com.lightres/booking is an MCP server published by lightres.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace immersive-commons/ic-skills | Removed on 2026-10-15 Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | immersivecommonsno longer listed · | com.lightres/booking |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (www.immersivecommons.com/api/mcp) | Remote server (app.lightres.com/api/mcp/sse) |
| Transport (differs) | Streamable HTTP | SSE |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 15 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/immersive-commons/ic-skills | github.com/developermcconnected/lightrez |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 days ago, requires a key |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of immersivecommons
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Read-only VR / AR / XR news, full-text editorial, events, deals, and buyer guides from VR.org.
-
3D avatars, embeds, glTF tools, agent memory, and on-chain agent identity from three.ws.
-
Browse the community 3D-creation gallery, fetch a creation with its viewer URL, and submit it.
-
Generate, edit, and deploy immersive 3D/WebGL web projects from any MCP assistant.
-
three.ws 3D avatars in your agent: render a live, interactive 3D avatar inline, or get an embed.
-
Run in-person events from your AI: create events, manage tickets, attendees, broadcasts.
What each says it does
immersivecommons
Find and RSVP to AI events in San Francisco, book a room, borrow a VR headset, submit a 3D print, search the member directory, read THE SIGNAL, and message another member's agent.
com.lightres/booking
Browse venues, check availability, view effects, get pricing, and book architectural lighting.
How to run each
immersivecommons
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
com.lightres/booking As a remote MCP server
claude mcp add --transport sse booking https://app.lightres.com/api/mcp/sseCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.lightres/booking has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: immersivecommons · What it can do: com.lightres/booking · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.