Example App

io.github.mctx-aiPublished by GitHub account mctx-aiv1.3.4Updated Oct 24, 2026

Build complete Apps with our framework — study or fork this reference implementation. Covers all @mc

VerifiedSSEWeb executableDeveloper Tools

Overview

AI-generated overview

A remote MCP endpoint for a reference app framework, letting an assistant work with the framework's example implementation.

What you can do
The registry describes it as a way to build complete apps with a framework, and to study or fork a reference implementation. No tools are listed in the manifest, so the concrete capabilities an assistant would gain are not documented here. It is offered as a remote endpoint over SSE rather than a local package.
When to use it
Consider it if you want an assistant to explore or work from this framework's reference implementation while building an app. Because no tools or documentation are provided, it is hard to judge its usefulness in advance.
Requirements
A remote MCP endpoint reached over SSE at the provider's host; no packages, environment variables, headers, or authentication are declared. Network access to that endpoint is required.
Before you install
The description is truncated and no README or tool list is available, so what the server actually does with your data cannot be verified. No authentication is declared, so avoid sending sensitive or private information through it.

Installation

In SourceWeft

  1. Open Example App in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.mctx-ai%2Fexample-app/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "example-app": {
      "type": "sse",
      "url": "https://example-app.mctx.ai/v1.3.4"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.3.4LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.