Hi Welcome Mcp Poc

io.github.AZ-IDDPublished by GitHub account AZ-IDDv0.1.0Updated Oct 24, 2026

POC MCP server. Tool say_hello returns 'Welcome' (agent -> MCP -> API path).

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

A proof-of-concept remote MCP server whose single tool, say_hello, returns "Welcome" to demonstrate an agent-to-MCP-to-API path.

What you can do
  • Call the say_hello tool, which returns the text "Welcome".
  • The call is routed agent to MCP server to an API, serving as a connectivity demonstration.
  • No other tools or capabilities are described.
When to use it
Useful only for testing that an MCP client can connect to a remote OAuth-protected endpoint and complete a tool call end to end. It offers no real data or workflow, so it is not meant for production use.
Requirements
A remote streamable HTTP endpoint; OAuth authentication is required. No environment variables or headers are declared.
Before you install
It is explicitly a proof of concept, so availability and behavior may change without notice. Connecting requires granting OAuth access to a third-party hosted endpoint.

Installation

In SourceWeft

  1. Open Hi Welcome Mcp Poc in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. 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.AZ-IDD%2Fhi-welcome-mcp-poc/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "hi-welcome-poc": {
      "type": "http",
      "url": "https://poc-v2-mcp-server.amr-dbe.workers.dev/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

67% 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
  • Auth declaredRequired10 pts
  • 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.