Swipa

ru.swipaPublished by swipa.ruOfficial publisherv0.1.1Updated Oct 24, 2026

SWIPA bot API — send/receive messages on swipa.ru via per-connection Bearer auth.

VerifiedSSEWeb executableCommunication & Collaboration

Overview

AI-generated overview

Remote MCP endpoint for the SWIPA bot API on swipa.ru, letting an assistant send and receive messages through a per-connection bot token.

What you can do
  • Send and receive messages on swipa.ru through the SWIPA bot API.
  • Authenticate each connection with a Bearer bot token.
  • No individual tools are documented, so the exact message operations are not listed.
When to use it
Use it when you want an assistant to exchange messages on swipa.ru as a bot, for example to relay or respond to conversations on that platform.
Requirements
A remote SSE endpoint at swipa.ru; no local package or runtime. An Authorization header with a Bearer bot token in the format irc_bot_ . , obtained from the provider's site.
Before you install
The connection requires a bot token sent in the Authorization header; treat it as a secret and keep it out of logs and shared configs. The server can send messages on your behalf, so review what the assistant posts. No tool list is published, so the exact scope of access is unclear.

Installation

In SourceWeft

  1. Open Swipa 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/ru.swipa%2Fmcp/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": {
    "swipa": {
      "type": "sse",
      "url": "https://swipa.ru/mcp/sse"
    }
  }
}

Tools

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

Version history

1
  1. v0.1.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 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

    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.