Roundhouse

io.roundhouseaiPublished by roundhouseai.ioOfficial publisherv0.1.0Updated Oct 24, 2026

Read-only analytics on x402 agent payments and ERC-8004 agent identity, with SQL.

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

Read-only SQL analytics on x402 agent payments and ERC-8004 agent identity, queried through a remote endpoint.

What you can do
Roundhouse exposes read-only analytics over x402 agent payment data and ERC-8004 agent identity records, queried with SQL. It runs as a remote streamable HTTP endpoint rather than a local package. The manifest lists no individual tools, so the exact query interface is not documented here.
When to use it
Useful when an assistant needs to answer questions about agent payment activity or agent identity registrations by running SQL against that data, without setting up a local server.
Requirements
A remote MCP endpoint at api.roundhouseai.io over streamable HTTP. Authentication is required: either an OAuth sign-in or a Roundhouse API key supplied in the x-api-key header. No local runtime, packages or environment variables are declared.
Before you install
The API key is a secret sent in the x-api-key header; keep it out of logs and shared transcripts. Access is described as read-only analytics, but queries still reach a third-party service, so consider what the queried data reveals before sending it.

Installation

In SourceWeft

  1. Open Roundhouse 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/io.roundhouseai%2Froundhouse/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": {
    "roundhouse": {
      "type": "http",
      "url": "https://api.roundhouseai.io/v0/mcp"
    }
  }
}

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. v0.1.0LatestOct 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.