Crystal

io.github.EraHQPublished by GitHub account EraHQv1.0.0Updated Oct 24, 2026

Self-curating memory your AI tools share: provenance, verified citations, and trust tiers.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Crystal is a remote, OAuth-protected memory service that gives AI tools a shared, self-curating memory with provenance, verified citations and trust tiers.

What you can do
  • Store and curate memory entries that persist across AI tools.
  • Attach provenance and verified citations to remembered information.
  • Apply trust tiers to distinguish more and less reliable memories.
  • Share one memory layer across multiple AI tools rather than per-assistant context.
  • No tool list is published, so exact operations are not documented.
When to use it
Useful when you want several AI assistants or tools to draw on the same long-lived memory and need to know where each remembered fact came from and how much to trust it.
Requirements
A remote MCP endpoint reached over streamable HTTP; OAuth authentication is required. No environment variables, headers or packages are declared.
Before you install
The service holds memory content and provenance data on a third-party hosted endpoint, so anything stored is sent outside your machine. OAuth grants access to your account there. Review what gets written before relying on it, since no tool list or README documents the write behavior.

Installation

In SourceWeft

  1. Open Crystal in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.EraHQ%2Fcrystal/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "crystal": {
      "type": "http",
      "url": "https://crystal-api-118881845105.us-east5.run.app/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 29, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.