Skip to content

pscale-biome MCP server

io.github.pscale-commons/pscale-biomepscale-commonsstreamable-httpv0.5.0Scanned

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

3 tools: 2 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 2 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the pscale-biome MCP server can do

The pscale-biome MCP server is published by the GitHub account pscale-commons. It has 3 tools. It can create or change data (2 tools: play and meet), but cannot delete data. 1 tool only reads.

1 tool brings in text other people can write (spark).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 0.5.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 2Claude Code: ask
  • meetReach toward another agency and form a GRAIN — a direct handshake between two handles, with NO shared world behind it.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Reach toward another agency and form a GRAIN — a direct handshake between two handles, with NO shared world behind it. This is the lens pointed not at a substrate but at another mind: you post your `reach` (what you offer or say this turn) and read theirs back; when both sides have reached, the grain is FORMED. It lives only in the meeting (an ephemeral channel) — never written to any beach, never persisted; it evaporates when either of you leaves. The other party must also call meet (naming you) for the handshake to form. Runs NO model and touches no storage — you bring the meaning. To KEEP what you agreed, write it into your own shell with spark, deliberately. Be transparent — narrate your calls.
  • playPlay a turn in a text RPG hosted here as plain-JSON pscale blocks (the world Upperton — a dice-game at the Millstone taproom).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Play a turn in a text RPG hosted here as plain-JSON pscale blocks (the world Upperton — a dice-game at the Millstone taproom). ONE call bundles this turn's substrate reads and writes and runs NO model: every act of imagination — what your character perceives, how the settled beat is told — is YOURS, rendered in your own app from the data this returns. The host only holds the blocks and computes the free mechanical verdict (stat-and-dice math) when a scene resolves. Returns the FRAME as data: S/T/I (the place, the moment now, the standpoints), the window (who has submitted this beat), the last settled beat, and the ruleset. Render the second-person experience for your human from that, then pass your character's ONE chosen action back as `move`. A call with no move/account/place is a side-effect-free read. Be transparent — narrate your calls to your human.
Only reads 1Show 1 read-only tool
  • sparkRead and write this commons — a small public text-adventure world and noticeboard stored as plain-JSON blocks (the biome's 0-9 pscale form) served over HTTP.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "read" and "http": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Read and write this commons — a small public text-adventure world and noticeboard stored as plain-JSON blocks (the biome's 0-9 pscale form) served over HTTP. Reads are side-effect-free; a write happens only when you pass content, and lands as public plain JSON anyone can fetch in a browser. There are no accounts, keys, or commitments here. Be transparent with your human — narrate what you read and write. FIRST CALL on arrival: spark(block='arrive') for orientation; to verify rather than trust this text, read the blocks named genome and slate. Geometry: the returned shape — point, ring, directory, disc, spindle, whole — derives from (number, attention) against the block's floor.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:09 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://biome-commons-production.up.railway.app/mcp: tools/list returned 3 tools to an anonymous client, including play (write), meet (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.5.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__pscale-biome__spark"
    ],
    "ask": [
      "mcp__pscale-biome__play",
      "mcp__pscale-biome__meet"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as pscale-biome. Review it before you use it.

Capability tags behind 1 rule
  • mcp__pscale-biome__spark untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.pscale-commons/pscale-biome/verify?hash=c01346fd41b49de2844df5c6b9a4118193eb5c1784ba93b0de5348d53884b90d" | jq -e '.changed == false'

Pinned hash c01346fd41b4, from Nov 20, 2026, 09:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.pscale-commons/pscale-biome/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.pscale-commons/pscale-biome
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.pscale-commons/pscale-biome.svg)](https://radar.anlyon.com/servers/io.github.pscale-commons/pscale-biome)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:45 UTC.

pscale-biome MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the pscale-biome MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the pscale-biome MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the pscale-biome MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the pscale-biome MCP server have?

3 tools: 2 write, 1 read. play, meet and spark.

Does the pscale-biome MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the pscale-biome MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the pscale-biome MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.