MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Code & DevOps

io.github.pscale-commons/pscale-biome

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

Checks passed
13 / 22

1 failed · 8 not measured

Median response
140 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
3

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Responded

The server completed its last measured handshake. This is an observation, not a guarantee.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
004
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
310
Publisher identityCan the publisher be traced to its source?
402

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 140 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-11-25, serverInfo.name biome-mcp.

  • Pass
    Lists tools

    tools/list returned 3 tools.

  • Pass
    Current protocol

    Negotiated 2025-11-25. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 140 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 140 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Pass
    Parameters documented

    18 of 18 parameters have a description (100%). The bar is 80%.

  • Fail
    Safety hints

    3 tools set neither readOnlyHint nor destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Not measured
    Website matches publisher

    This namespace is not a reverse domain, so the website comparison does not apply.

  • Pass
    Source repo linked

    A repository URL is on file.

  • Pass
    Repo owner matches

    The GitHub repository owner matches the namespace login.

  • Pass
    Recently updated

    Updated 2026-07-03T22:44:49.183234Z, within 180 days.

  • Not measured
    Open-source licence

    The GitHub licence lookup has not returned an OSI result yet.

Start using io.github.pscale-commons/pscale-biome

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

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

Capabilities

Tools 3

meet

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.

Discovered
play

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.

Discovered
spark

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.

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected140 ms3