Support Service Management Mcp

io.github.varvararattaPublished by GitHub account varvararattav1.0.0Updated Oct 27, 2026

MCP server for Support & Service Management

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint for support and service management, hosted on MCPize with free discovery tools and paid tools via x402.

What you can do
  • Connect to a hosted support and service management service over streamable HTTP.
  • Run a health check and discovery tools without payment.
  • Use paid tools through an x402-capable client, settled in USDC on Base.
  • No tool list is published, so the exact support and service operations are not documented.
When to use it
Consider it if you want an assistant to reach a hosted support and service management service without running anything locally, and your client can handle x402 payments for the paid tools.
Requirements
A remote endpoint at the provider's mcpize.run host, reachable over the network. No authentication, environment variables or headers are declared. Paid tools require an x402-capable MCP client with USDC on Base; health check and discovery tools are free.
Before you install
Paid tools involve cryptocurrency payment in USDC on Base through x402, so using them can spend funds. The tool list is not published, so what the paid tools do to support or service data cannot be verified in advance. The README describes a shared farm of hosted servers rather than this server specifically.

Installation

In SourceWeft

  1. Open Support Service Management Mcp in the dashboard and add it to a workspace.
  2. 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.varvararatta%2Fsupport_service_management_mcp/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": {
    "support-service-management": {
      "type": "http",
      "url": "https://support-service-management-mcp.mcpize.run/mcp"
    }
  }
}

README

BotFactory MCP Farm

Hosted MCP servers on MCPize — zero-auth public APIs, freemium x402 (USDC on Base).

Catalog

See CATALOG.md for the full list with gateway URLs.

Connect

https://<slug>.mcpize.run/mcp

Requires an x402-capable MCP client for paid tools. health_check and discovery tools are free.

Awesome list entries

See AWESOME_ENTRIES.md.

Source: README.md at commit 14e36b4

Tools

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

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% 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 listedRequired15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.