Pscale Biome

Name: Pscale Biome
Author: pscale-commons

by pscale-commonsversion 0.5.0i★ –iRuns in the cloud

Registry nameio.github.pscale-commons/pscale-biome

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://biome-commons-production.up.railway.app/mcp

Run this in your terminal

claude mcp add --transport http pscale-biome https://biome-commons-production.up.railway.app/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "pscale-biome": {
      "url": "https://biome-commons-production.up.railway.app/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "pscale-biome": {
      "type": "http",
      "url": "https://biome-commons-production.up.railway.app/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://biome-commons-production.up.railway.app/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account pscale-commons, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 18334 servers in this category
Published to the registry more recently than 13% of the other 18334 servers in this category
Basic checks equal to or better than 100% of the other 18334 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Pscale Biome safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.5.0) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, ProAgentStore

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

ProAgentStore

by ProAgentStore

MCP-first control plane for ProAgentStore agents and private instances.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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.

Source	What was vendored	Vendored 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.js`	2026-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.tsx`	2026-05-09
`happyseaurchin` (local)	`docs/systemic-kernel.json`	2026-05-09
User draft	`docs/biome-design.md`	2026-05-09
This project	`src/sentinel/biome.json`, README, CLAUDE.md, docs/minimal-package.md	2026-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)

#	Concern	Source code in this tree
1	Storage (beach surface)	`src/beach/handler.js`
2	BSP function	`src/bsp/`
3	MCP transport	not yet vendored — to be authored or ported from bsp-mcp
4	Hermit-crab shell (autonomous LLM mode)	not yet present — mobius pattern, awaiting reference
5	xstream 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.

Pscale Biome

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

ProAgentStore

README from the maker

pscale-biome

What this is

What's NOT this

Layout

Provenance

The five concerns (per biome-design.md)

The open question

License