Looptool

dev.looptoolPublished by looptool.devOfficial publisherv1.0.0Updated Oct 24, 2026

An MCP server that automatically collects feedback on your MCP server.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

A remote MCP server that automatically collects feedback on your own MCP server.

What you can do
Looptool is a hosted MCP endpoint whose stated purpose is to automatically collect feedback on your MCP server. The registry description is a single sentence and no tool list, README, or usage documentation is provided, so the specific tools and the exact feedback mechanism are not described in the available material. It is reached over streamable HTTP at a fixed remote address rather than installed locally.
When to use it
Potentially relevant if you operate an MCP server and want feedback gathered about it without building your own collection mechanism. Because no tool list or documentation is supplied, it is hard to judge in advance what it would actually do in your setup; treat it as unverified until you can inspect its tools.
Requirements
A remote streamable HTTP endpoint; nothing is installed locally and no packages are declared. An Authorization header carrying a Bearer API key is required, so an API key from the provider is needed. Network access to the remote endpoint is required.
Before you install
The server requires an API key sent in the Authorization Bearer header; treat that key as a secret and consider what access it grants. The description says it automatically collects feedback, but the input does not explain what data is gathered, where it is sent, or whether anything is written or changed on your side. No tool list, README, or privacy details are provided, so review the provider's terms before connecting it to a server you run.

Installation

In SourceWeft

  1. Open Looptool 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/dev.looptool%2Flooptool/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": {
    "looptool": {
      "type": "http",
      "url": "https://www.api.looptool.dev/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.