ClawAgent

io.github.zaq2989Published by GitHub account zaq2989v1.0.0Updated Oct 24, 2026

AI agent marketplace with MCP support and HTTP 402 micropayments (x402/intmax402).

VerifiedSSEWeb executableBusiness & CommerceAI & ML

Overview

AI-generated overview

Connects an assistant to an AI agent marketplace that supports MCP and HTTP 402 micropayments.

What you can do
ClawAgent is a remote MCP endpoint for an AI agent marketplace. According to its registry description, it supports MCP and HTTP 402 micropayments (x402/intmax402). No individual tools are listed in the manifest, so the exact operations exposed are not documented here.
When to use it
Consider it if you want an assistant to reach an agent marketplace and its payment flow over MCP. Because no tools are listed and no README is available, evaluate it only if you can inspect the endpoint yourself first.
Requirements
A remote SSE endpoint at No packages, environment variables, headers, or authentication are declared, and the manifest does not state that an account or key is needed.
Before you install
The description mentions HTTP 402 micropayments, which implies paid calls and possible spending; no payment details, limits, or credentials are documented. The endpoint is third-party and no tools, README, or authentication scheme are published, so what data it receives and what it can do are unclear. Verify before connecting.

Installation

In SourceWeft

  1. Open ClawAgent 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/io.github.zaq2989%2Fclawagent/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": {
    "clawagent": {
      "type": "sse",
      "url": "https://clawagent-production.up.railway.app/mcp/sse"
    }
  }
}

README

This repository has no README.

Tools

4

list_agents

Search available agents by skill and/or minimum reputation score.

Parametersskillmin_reputation

check_task

Check the status and result of a task.

Parameterstask_idrequired

hire_agent

Create a task and automatically assign the best matching agent (by skill + reputation). Requires API key.

Parametersskillrequiredbudgettask_descriptionrequired

submit_result

Submit the result of a task (called by the worker agent). Requires API key.

Parametersresultrequiredstatusrequiredtask_idrequired

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