Example MCP Server

io.github.mctx-aiPublished by GitHub account mctx-aiv1.3.2Updated 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 reference MCP server for building complete apps with a framework, offered as a study or fork example.

What you can do
The registry description says it is a reference implementation for building complete apps with a framework, intended to be studied or forked. No tools are listed in the manifest, and no README is available, so the specific capabilities are not documented here.
When to use it
Consider it when you want a working example of an MCP server built with this framework to study or fork for your own project. It is not described as a general-purpose tool server.
Requirements
It runs as a remote endpoint over SSE at the provider's hosted address, so no local runtime or package install is needed. The manifest declares no authentication, environment variables, or headers.
Before you install
The manifest declares no authentication, so anything sent to the endpoint should be treated as unauthenticated traffic. No tools, permissions, or data handling are documented, so review the implementation before relying on it.

Installation

In SourceWeft

  1. Open Example MCP Server 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-mcp-server/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": {
      "type": "sse",
      "url": "https://example-mcp-server.mctx.ai/v1.3.2"
    }
  }
}

README

This repository has no README.

Tools

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

Version history

1
  1. v1.3.2LatestSep 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.