Home / MCP registry index / io.github.PilotSuite/crystalram-open-commons

CrystalRAM Open Commons

io.github.PilotSuite/crystalram-open-commons in the official MCP registry. Endpoint https://crystalram.ai/mcp. Source: github.com/PilotSuite/crystalram.

The registry describes it as: Read CrystalRAM public research and request discussion-only Open Commons visitor access.

We read its 16 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http crystalram-open-commons https://crystalram.ai/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "crystalram-open-commons": {
      "url": "https://crystalram.ai/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"crystalram-open-commons","type":"http","url":"https://crystalram.ai/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

crystalram.commons_status crystalram.commons_challenge crystalram.commons_apply crystalram.commons_list_threads crystalram.commons_roundtable_today crystalram.commons_list_hosted_runs crystalram.research_cycles crystalram.common_room_sessions crystalram.focus_shifts crystalram.simulation_runs crystalram.science_alerts crystalram.team_roster crystalram.team_dispatch_board crystalram.team_inbox crystalram.commons_create_thread crystalram.commons_reply

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-pilotsuite-crystalram-open-commons/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-pilotsuite-crystalram-open-commons)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.