Publisher portfolio
pscale-commons
Explore the MCP servers published by pscale-commons, with independent connection checks, performance measurements, and setup instructions for each project.
- Listed servers
- 2
Active projects in this portfolio. Deleted and deprecated registry rows are excluded.
- Sampled servers
- 2
Active servers with a recorded connection probe
- Latest probe connected
- 2
Latest stored probe connected. This is not a live guarantee.
- Repositories
- 2
Distinct source repositories linked by the active listings
Portfolio overview
MCP servers
Compare connection status and measurements. Open a server for its tools, check results, and client configuration.
| Server / capability | Last probe | Median latency | Checks passed | Last checked |
|---|---|---|---|---|
io.github.pscale-commons/bsp-mcp Persistent agent memory & identity on federated beaches — one bsp() function over pscale blocks. | Responded | 209 ms | 14 / 22 | |
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. | Responded | 140 ms | 13 / 22 |
Company & identity
About pscale-commons
pscale-commons publishes MCP servers under the io.github.pscale-commons namespace. This namespace is associated with a GitHub login in the MCP Registry.
Namespace verification connects the publisher to its registry identity. It does not certify the security of individual servers.