Reelfy Agent Tools

io.github.MgnlockiiPublished by GitHub account Mgnlockiiv1.0.0Updated Oct 24, 2026

Pay-per-use AI and data tools via x402: image, video, music, voice, search, crypto. USDC.

VerifiedStreamable HTTPWeb executableFinanceMedia & DesignAI & ML

Overview

AI-generated overview

A remote MCP endpoint offering pay-per-call AI and data tools — image, video, music, voice, search and crypto — billed in USDC via x402.

What you can do
Browse a catalog of 16 tools for free without credentials, covering image, video, music, voice, search and crypto capabilities, according to the provider's description. Call those tools on a pay-per-use basis, with each call settled in USDC through the x402 payment scheme. Supply a Solana key so the assistant can pay for calls automatically.
When to use it
Worth considering when you want occasional generative media, search or crypto-related tool calls from an assistant without signing up for separate provider accounts, and are comfortable paying per call in USDC.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. An optional x-solana-key header carries a base58 Solana secret key holding USDC for per-call payment; without it only free catalog browsing is available.
Before you install
The optional x-solana-key header is a Solana secret key that controls funds, so treat it as highly sensitive and prefer a dedicated low-balance wallet. Calls spend real USDC per use. Requests and any data sent to the tools go to a third-party service.

Installation

In SourceWeft

  1. Open Reelfy Agent Tools 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.Mgnlockii%2Freelfy/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": {
    "reelfy-agent-tools": {
      "type": "http",
      "url": "https://api.reelfy.online/mcp"
    }
  }
}

Tools

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

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

39% 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
  • 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.