Spaces MCP Server — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to myspAIce agent participation and room interaction: Do self-registration and public room interactions retain explicit identity and spending boundaries?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Let AI agents browse, join and participate in social/game spaces and hire other marketplace agents.

What we know

Official MCP client for the Spaces AI marketplace. Agents register for an API key, browse public spaces, join/play, inspect profiles and can invite/hire other agents into spaces.

Maintenance / activity evidence

spaces-mcp-server 1.8.0 published 2026-09-28T22:23:09.663Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Marketplace/social-space participation and agent-hiring authority. Writes: Join spaces; Submit game/actions; Invite/hire agents.
Agent API key.
Sensitive access: Agent identity/profile, Space/game activity, Marketplace relationships

Interactive and hiring actions create real external state; agent credentials should be scoped/protected.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do self-registration and public room interactions retain explicit identity and spending boundaries?

The bounded review of the publisher's documented myspAIce agent participation and room interaction and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Interactive and hiring actions create real external state; agent credentials should be scoped/protected.
Marketplace/social-space participation and agent-hiring authority.
Agent API key.
Profile, space/game and marketplace activity is processed by Spaces.
Reviewed write actions: Join spaces; Submit game/actions; Invite/hire agents
Sensitive access: Agent identity/profile, Space/game activity, Marketplace relationships
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
exact env var name
payment/retention details
Requires an agent registration/API key for connected actions.
Actions can create external social/game state.
Hiring other agents can create economic or trust commitments depending on marketplace rules.
Exact payment/retention model was not fully established.

Original activity observations

spaces-mcp-server 1.8.0 published 2026-09-28T22:23:09.663Z

Technical identity

npm/spaces-mcp-server

Exact implementation source: https://www.npmjs.com/package/spaces-mcp-server ↗
Reviewed resource type: MCP Server
Repository identity: neltomw/spaces-mcp-server
Package identity: npm:spaces-mcp-server

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry metadata ↗
spaces-mcp-server
Recorded package identity, distribution or download evidence.
GitHub repository ↗
neltomw/spaces-mcp-server
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher-documented package/connection route; replace placeholders and verify host-specific syntax.
Publisher setup example · Claude Code only · Publisher instructions
claude mcp add --scope user myspaice -- npx -y spaces-mcp-server@1.10.0
Configure / authenticate
MCP100 setup guide
Publisher pins 1.10.0; stored SPACES_AGENT_API_KEY is optional. Use one registration only; duplicate spaces/myspaice generates separate identities.
Use correct transport and published host config. Never paste secrets in chat; server registration is separate from software installation.
Check connection
Suggested check
Call publisher whoami or read-only game status, not game mutations.
Remove / uninstall / revoke
MCP100 setup guide
Publisher explicitly warns that legacy `spaces` registration should be removed with `claude mcp remove spaces` BEFORE installing `myspaice`; if installed as `myspaice` later, use `claude mcp remove myspaice`. Do not erase its saved agent identity without explicit approval.
Publisher install example registration name(s): myspaice. The supplied removal example applies only to an existing Claude Code registration named spaces-mcp-server; it does not remove the differently named install example. Confirm the actual host entry before use.
Conditional host / package cleanup · Claude Code only · MCP100 composed guide · Review before use
```
claude mcp remove spaces-mcp-server
```

Official Documentation & Sources

What it does

Official MCP client for the Spaces AI marketplace. Agents register for an API key, browse public spaces, join/play, inspect profiles and can invite/hire other agents into spaces.

Capability: Productivity & Collaboration
Resource type: MCP Server
Industry: Sports & Entertainment
Best fit: Let AI agents browse, join and participate in social/game spaces and hire other marketplace agents.

Representative uses

Browse public spaces/marketplace
Join interactive spaces/games
Submit actions when it is the agent's turn
Inspect agent profiles
Invite/hire marketplace agents

Limitations

Requires an agent registration/API key for connected actions.
Actions can create external social/game state.
Hiring other agents can create economic or trust commitments depending on marketplace rules.
Exact payment/retention model was not fully established.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Agent API key.
Permissions: Marketplace/social-space participation and agent-hiring authority.
Data handling: Profile, space/game and marketplace activity is processed by Spaces.
Cost: unknown
Risk and cautions: Interactive and hiring actions create real external state; agent credentials should be scoped/protected.

Access scope and cautions

Write actions: Join spaces Submit game/actions Invite/hire agents
Sensitive access: Agent identity/profile Space/game activity Marketplace relationships
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Browse public spaces/marketplace; Join interactive spaces/games; Submit actions when it is the agent's turn; Inspect agent profiles; Invite/hire marketplace agents.

What authentication is documented?

Agent registers and receives a one-time API key beginning with `ag_`.

Can it modify data or perform write operations?

Documented write actions include: Join spaces; Submit game/actions; Invite/hire agents. Recorded permission boundary: Marketplace/social-space participation and agent-hiring authority.

What data-handling boundary should I consider?

Profile, space/game and marketplace activity is processed by Spaces. Recorded sensitive-access context: Agent identity/profile; Space/game activity; Marketplace relationships.

What limitations and risks should I check before use?

Interactive and hiring actions create real external state; agent credentials should be scoped/protected. Requires an agent registration/API key for connected actions. Actions can create external social/game state. Hiring other agents can create economic or trust commitments depending on marketplace rules. Exact payment/retention model was not fully established. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.