AgentDrop

fyi.agentdropPublished by agentdrop.fyiOfficial publisherv0.3.0Updated Nov 1, 2026

Paid tools for AI agents over x402: frontier-model chat per call, plus drops and hand-off channels.

VerifiedStreamable HTTPWeb executableBusiness & CommerceAI & ML

Overview

AI-generated overview

A free directory server that lists and describes paid x402 services for AI agents, such as per-call frontier-model chat and temporary key-value drops.

What you can do
  • List the available paid services with their MCP endpoints, HTTP routes, prices and limits
  • Describe a single service in full, including its MCP URL, config snippet, routes, prices, limits and security model
  • Point the assistant to the separate MCP server for each service so it can connect to the one it needs
When to use it
Use it when you want an assistant to discover which paid agent services exist and what they cost before connecting to one, for example per-call model chat or short-lived key-value hand-off channels.
Requirements
Remote streamable HTTP endpoint at agentdrop.fyi; no account, API key or environment variables are declared. The described services themselves are paid over x402 with USDC on Base, so a funded paying wallet is needed to actually use them.
Before you install
This server only describes services; the listed services charge money per call in USDC on Base, with the paying wallet acting as the identity and no account or key to revoke. Review each service's stated price and security model before connecting an assistant that can spend.

Installation

In SourceWeft

  1. Open AgentDrop 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/fyi.agentdrop%2Fagentdrop/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": {
    "agentdrop": {
      "type": "http",
      "url": "https://agentdrop.fyi/mcp"
    }
  }
}

README

This repository has no README.

Tools

2

list_services

List services

The Payperwork services with their MCP endpoints, HTTP routes, prices and limits. Free.

Takes no parameters.

describe_service

Describe a service

One service in full: its MCP URL and config snippet, HTTP routes, prices, limits and security model. Free.

Parametersservicerequired

Version history

1
  1. v0.3.0LatestNov 1, 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
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Agentdrop integrations