Tip4serv

com.tip4servPublished by tip4serv.comOfficial publisherv1.0.1Updated Oct 24, 2026

Monetize and manage your Tip4Serv store directly from your LLM.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Tip4serv is a remote MCP server that lets an assistant monetize and manage a Tip4Serv store from within the chat.

What you can do
Monetize and manage a Tip4Serv store from the assistant, based on the provider's short description. No tool list is published, so the exact actions available are not documented here. The server is reached as a remote endpoint rather than installed locally.
When to use it
Consider it if you already run a Tip4Serv store and want to handle its monetization and management tasks through an AI assistant instead of the store's own interface.
Requirements
A remote MCP endpoint at mcp.tip4serv.com, reachable over the network. OAuth authentication is required, so you need a Tip4Serv account that can authorize the connection. No environment variables or headers are declared.
Before you install
The server concerns store monetization and management, so connected tools may change store settings or handle payment-related data; the exact write actions are not documented. Access is granted through OAuth, so review which permissions you authorize. Store data is sent to the Tip4Serv service.

Installation

In SourceWeft

  1. Open Tip4serv 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/com.tip4serv%2Fmcp-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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "tip4serv": {
      "type": "http",
      "url": "https://mcp.tip4serv.com/"
    }
  }
}

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. v1.0.1LatestSep 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.