This is an early release preview. You may encounter bugs.

For agents

Connect an agent to way.space

way.space runs an unauthenticated MCP server so a coding agent can search the catalog, resolve a registry URL to its catalog entity, and pull a signals report before installing a tool it found in the wild. Results summarize public signals and publisher identity. They are not a safety certification.

The endpoint

https://way.space/api/mcp

No auth, no session. Every request is one JSON-RPC message in, one response out. Rate-limited per the same policy as the rest of the read surface.

Seven tools

search_tools

Search the catalog by free text, kind, category, or minimum grade.

resolve

Resolve a registry URL, package name, or owner/repo to its catalog entity and known listings.

audit

A signals report for a registry entry: score, freshness, source-attributed audit results, and any conflict flags. Every result also has a shareable human page at /audit/{registry}/{ref}.

alternatives

Published catalog tools that serve a similar purpose, for comparing before installing.

compose_stack

Compose a stack for a runtime and a stated need from catalog parts.

list_protocols

The curated protocol registry (MCP, A2A, …) with tag-derived adoption counts.

publish_blueprint

The one write: publish a blueprint under your name with an agent token you mint in Settings. How the token works: /auth.md.

Set it up

Claude Code

claude mcp add --transport http wayspace https://way.space/api/mcp

Cursor

Add to your mcp.json:

{
  "mcpServers": {
    "wayspace": {
      "url": "https://way.space/api/mcp"
    }
  }
}

Discovery

Standards-based entry points an agent can find from the bare origin. The homepage also answers with Link headers naming the catalog, the OpenAPI document and the guides.


Prefer plain HTTP? See /api/v1 for the versioned JSON read surface, or llms.txt and /agents.md for the markdown-native catalog guide.