Discover the MCP servers on the official MCP registry with OCI and Wasm artifact types

[Mossaka]

https://github.com/modelcontextprotocol/registry

[Mossaka]

/scout

Agentic Scout triggered by this comment

[github-actions]

🔍 Scout Research Agent - Ready for Assignment

Triggered by @Mossaka on issue #352

Status: Awaiting Research Topic

Hello! I'm the Scout research agent, ready to conduct deep research for you. However, I need more specific direction about what you'd like me to investigate.

How to Use Scout

To get the most value from my research capabilities, please provide a specific research topic or question. For example:

Good Research Requests:

• Technology Investigation: "Research best practices for WebAssembly component security sandboxing"
• Competitive Analysis: "Investigate how other MCP servers handle dynamic component loading"
• Problem Solving: "Research solutions for WASI filesystem permission management in multi-tenant environments"
• Feature Research: "Investigate OCI registry authentication mechanisms for pulling private components"
• Ecosystem Survey: "Research the current state of WebAssembly component registries and tooling"

How to Trigger Research:

You can trigger me in two ways:

1. In issue/PR comments: /scout <your research topic>

   • Example: /scout research WebAssembly component caching strategies

2. Manual workflow dispatch: Provide the research topic in the workflow input field

Available Research Tools

I have access to several powerful research capabilities:

• 🌐 Web Search (Tavily): Deep web search for technical documentation, best practices, and recent developments
• 📚 Microsoft Docs: Official Microsoft documentation and technical guides
• 🔍 GitHub Search: Repository documentation and discussions

What I Can Help With

As a research agent for the Wassette project (a security-oriented WebAssembly MCP runtime), I'm particularly well-suited to research:

• WebAssembly and WASI ecosystem developments
• Model Context Protocol (MCP) implementations and patterns
• Component model specifications and tooling
• Security sandboxing and permission systems
• OCI registry integration patterns
• Rust systems programming best practices
• Cross-language WebAssembly toolchains

---

Ready to start researching! Just reply with /scout <your research topic> and I'll conduct a comprehensive investigation.

AI generated by Scout

[Mossaka]

/scout this issue

Agentic Scout triggered by this comment

[github-actions]

🔍 Scout Research Report

Triggered by @Mossaka on issue #352

Executive Summary

The MCP official registry supports multiple package types including OCI (container images) with robust validation infrastructure. However, there is currently no native support for Wasm artifact types in the registry. OCI packages use Docker/GHCR registries with container images, not WebAssembly components.

Click to expand detailed findings

Research Findings

Registry Package Types

The MCP registry defines these supported package types in pkg/model/constants.go:

• npm - Node.js packages from NPM registry
• pypi - Python packages from PyPI
• oci - Container images (Docker/GHCR)
• nuget - .NET packages from NuGet
• mcpb - MCP Binary format (direct file downloads with SHA-256 verification)

OCI Package Support

Current Implementation:

• OCI packages reference container images (Docker format) stored in Docker Hub or GitHub Container Registry
• Registry validates OCI images by checking for the required annotation: io.modelcontextprotocol.server.name
• The validation code in internal/validators/registries/oci.go performs these checks:
  1. Fetches image manifest from Docker Hub or GHCR
  2. Extracts config digest from manifest
  3. Validates the io.modelcontextprotocol.server.name label matches the server name

Example from seed data:

{
  "registryType": "oci",
  "identifier": "domdomegg/airtable-mcp-server",
  "version": "1.7.2",
  "runtimeHint": "docker",
  "transport": {
    "type": "stdio"
  }
}

WebAssembly/Wasm Artifact Status

Key Finding: There is no mention of WebAssembly or Wasm in the registry codebase.

• Search for "wasm" and "WebAssembly" returned zero results
• No dedicated registry type for Wasm components
• No validators for Wasm artifacts
• OCI packages are strictly Docker container images, not Wasm OCI artifacts

Why This Matters for Wassette

Wassette is a WebAssembly-based MCP runtime that executes MCP servers as Wasm components. The gap between OCI container support and Wasm component support means:

1. No native discovery of Wasm-based MCP servers in the registry
2. Cannot leverage existing OCI infrastructure for Wasm components
3. Need custom tooling to identify Wasm-capable servers

Recommendations

Short-term Solutions

1. Use MCPB format - Package Wasm components as MCPB (direct download) with SHA-256 verification

   • Already supported by registry
   • Straightforward distribution via GitHub Releases
   • Example: https://github.com/user/server/releases/download/v1.0.0/server.mcpb

2. Custom metadata filtering - Query registry API and filter by custom metadata fields

   • Add custom _meta fields to identify Wasm-compatible servers
   • Build discovery tooling that filters based on these markers

Long-term Proposals

1. Add wasm registry type to the official registry

   • New constant: RegistryTypeWasm = "wasm"
   • Support OCI registries with Wasm artifact type
   • Implement Wasm-specific validation (check for component model, exported interfaces)

2. Extend OCI support to handle Wasm artifacts

   • OCI registries already support Wasm artifacts (different artifact type)
   • Add artifact type detection to existing OCI validator
   • Validate Wasm component manifests and exports

3. Create Wasm component metadata standard

   • Define annotations for Wasm components (similar to OCI label requirements)
   • Specify required WIT interfaces for MCP servers
   • Document Wasm component capabilities and constraints

Key Sources

• MCP Registry Repository
• Registry API Documentation
• Package Types Constants
• OCI Validator Implementation
• Seed Data Examples

Suggested Next Steps

1. Open discussion with MCP registry maintainers about Wasm support
2. Document Wasm requirements - Create specification for Wasm-based MCP servers
3. Prototype MCPB distribution - Package a Wasm component as MCPB and test with Wassette
4. Build discovery tooling - Create utility to query registry and identify Wasm-compatible servers
5. Consider registry PR - Contribute Wasm registry type support to upstream project

Research conducted using GitHub API, repository code analysis, and official MCP registry documentation. No WebAssembly or Wasm artifact support was found in the current registry implementation.

AI generated by Scout