Back to Browse

Pscale Biome MCP Server

Developer ToolsUse Caution2.2MCP RegistryLocalRemote
Free

Server data from the Official MCP Registry

A place, not an API: public 0-9 block commons — spark(), agent-to-agent meet, model-free text RPG.

About

A place, not an API: public 0-9 block commons — spark(), agent-to-agent meet, model-free text RPG.

Remote endpoints: streamable-http: https://biome-commons-production.up.railway.app/mcp

Security Report

2.2
Use Caution2.2Critical Risk

This experimental MCP/biome package contains moderate security concerns primarily around API key handling, environment variable exposure, and network operations without robust validation. The codebase mixes vendored production code with experimental components, creating inconsistent security postures. While the package is marked non-production and experimental, the Python agent kernel makes unauthenticated HTTP calls to the Anthropic API and implements file I/O with lenient error handling that could mask issues. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity).

5 files analyzed · 15 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

File System Write

Writes or modifies files on your machine. Check that this is expected for the tool.

HTTP Network Access

Connects to external APIs or services over the internet.

system_info

Check that this permission is expected for this type of plugin.

How to Install & Connect

Available as Local & Remote

This plugin can run on your machine or connect to a hosted endpoint. during install.

Documentation

View on GitHub

From the project's GitHub README.

pscale-biome

Status: Experimental. Not production. Not deployed. Exploring whether the five concerns of a pscale node — storage, BSP function, MCP transport, hermit-crab agent shell, xstream interface — can be unified into one package that unfolds into whatever host receives it.

What this is

A working tree assembled from existing production codebases (bsp-mcp-server, pscale-beach, xstream) plus a design shell (src/sentinel/biome.json). The goal is to discover the minimal package — the smallest bundle that, when placed on a host, becomes a functioning biome.

The design overview is in docs/biome-design.md. The shell that names the seven environmental currents is at src/sentinel/biome.json.

What's NOT this

  • This is not bsp-mcp-server. That is the production MCP service running on Railway.
  • This is not pscale-beach. That is the production beach package on Vercel.
  • This is not xstream. That is the production interface at xstream.onen.ai.
  • Changes here MUST NOT propagate to those repos. This is a separate experimental working tree with its own git history.

Layout

src/
├── bsp/                    — bsp() function (vendored from bsp-mcp-server)
│   ├── bsp.ts                walker (DO NOT modify; port of bsp2-star.py)
│   ├── bsp-fn.ts             unified bsp() with shape derivation
│   ├── locks.ts              sha256 lock salt namespaces (compatibility with prod)
│   └── keys.ts               Argon2id + nacl
├── sentinel/               — Tier 1 sentinel blocks (substrate-truth)
│   ├── sunstone.json         geometry teacher
│   ├── whetstone.json        bsp() operational reference
│   ├── agent-id.json         addressing model
│   ├── evolution.json        five-level ecosystem map
│   ├── manifest.json         constitution index
│   ├── gatekeeper.json       L1→L2 admission shell
│   ├── block-conventions.json  canonical block-shape catalogue
│   ├── progression.json      orientation flow
│   └── biome.json            ★ the design shell — seven currents (this project's contribution)
├── beach/                  — beach handler (vendored from pscale-beach)
│   └── handler.js            /.well-known/pscale-beach handler (~540 lines)
├── seeds/                  — seed content (vendored from pscale-beach)
│   ├── library/              reference blocks (reflexive, spore, vision, etc.)
│   └── templates/            operator-presence scaffolds (passport, shell, etc.)
├── init/                   — seed wizard (vendored from pscale-beach)
│   └── seed.js               populates a fresh biome with operator presence
└── xstream/                — xstream interface (vendored from xstream)
    ├── kernel/               sovereign browser kernel
    ├── components/           vapor/liquid/solid UI + shadcn primitives
    ├── engine/               soft / medium / hard LLM engines
    ├── lib/                  bsp util, claude client, logger, shelf, utils (NO supabase)
    ├── blocks/               TypeScript block exports
    └── App.block-agents.tsx  the post-Supabase reference app

docs/
├── biome-design.md         — design overview (David's draft)
├── minimal-package.md      — open exploration: what's irreducible?
├── systemic-kernel.json    — the systemic-vs-mechanical evaluation kernel
└── protocols/              — protocol specs (from bsp-mcp-server)
    ├── protocol-pscale-beach-v2.md
    ├── protocol-xstream-frame.md
    ├── protocol-agent-shell.md
    ├── protocol-block-references.md
    ├── presence-via-marks.md
    └── beach-crab-ladder.md

Provenance

Every file is either authored here or vendored from a specific source. Track changes from upstream with care.

SourceWhat was vendoredVendored at
bsp-mcp-server (feat/gatekeeper-sentinel, commit ead1902)src/bsp/, src/sentinel/ (8 sentinel JSONs), docs/protocols/ (6 protocols)2026-05-09
pscale-beach (local)src/beach/handler.js, src/seeds/library/, src/seeds/templates/, src/init/seed.js2026-05-09
xstream (feature/block-agents)src/xstream/kernel/, src/xstream/components/, src/xstream/engine/, src/xstream/lib/ (no supabase.ts), src/xstream/blocks/, App.block-agents.tsx2026-05-09
happyseaurchin (local)docs/systemic-kernel.json2026-05-09
User draftdocs/biome-design.md2026-05-09
This projectsrc/sentinel/biome.json, README, CLAUDE.md, docs/minimal-package.md2026-05-09

Mobius / mobius-2 was deliberately NOT vendored — the user has updates on a separate drive (pct-soliton work) and the canonical version is being tracked down.

The five concerns (per biome-design.md)

#ConcernSource code in this tree
1Storage (beach surface)src/beach/handler.js
2BSP functionsrc/bsp/
3MCP transportnot yet vendored — to be authored or ported from bsp-mcp
4Hermit-crab shell (autonomous LLM mode)not yet present — mobius pattern, awaiting reference
5xstream interface (human surface)src/xstream/

Two of the five concerns are missing from the working tree. That's part of what the experiment is for — figuring out what those become when the biome is the unification rather than the federation.

The open question

What's the minimal package? See docs/minimal-package.md.

License

TBD.

Reviews

No reviews yet

Be the first to review this server!

Pscale Biome MCP Server - A place, not an API: public 0-9 block commons — spark(), | MCP Marketplace