Skip to content

Loop Desk MCP server

com.bot2botlabs/loop-deskbot2botlabs.comstreamable-httpv1.0.0Scanned

Agent-payable open-loop tracker for refunds, returns, and asks with TRACE receipts.

3 tools: 1 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 1 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Loop Desk MCP server can do

The Loop Desk MCP server is published by bot2botlabs.com, a domain the MCP Registry verified. It has 3 tools. It can create or change data (1 tool: register_loop), but cannot delete data. 2 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 10, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 1Claude Code: ask
  • register_loopRegister an open loop (refund, return, price_adjustment, delivery, unanswered, other).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Register an open loop (refund, return, price_adjustment, delivery, unanswered, other). Returns TRACE receipt. Needs an API key: keyless calls are read-only (get_loop, list_due).
Only reads 2Show 2 read-only tools
  • get_loopFetch one loop by id for the calling API key.No findings

    Why it is in this group

    • The name "get_loop" says "get": a word for reading.
    Description, as the server wrote it
    Fetch one loop by id for the calling API key.
  • list_dueList open loops due on or before `before` (ISO datetime).No findings

    Why it is in this group

    • The name "list_due" says "list": a word for reading.
    Description, as the server wrote it
    List open loops due on or before `before` (ISO datetime).

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:23 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2024-11-05
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://loop.bot2botlabs.com/mcp: tools/list returned 3 tools to an anonymous client, including register_loop (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http loop-desk https://loop.bot2botlabs.com/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http loop-desk https://loop.bot2botlabs.com/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__loop-desk__get_loop",
      "mcp__loop-desk__list_due"
    ],
    "ask": [
      "mcp__loop-desk__register_loop"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as loop-desk. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.bot2botlabs/loop-desk/verify?hash=56526e467df6ed06fdb592df42696a040ca1a911e553fd42d847710e8a4c952b" | jq -e '.changed == false'

Pinned hash 56526e467df6, from Nov 10, 2026, 09:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.bot2botlabs/loop-desk/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.bot2botlabs/loop-desk
[![Anlyon Radar](https://radar.anlyon.com/badge/com.bot2botlabs/loop-desk.svg)](https://radar.anlyon.com/servers/com.bot2botlabs/loop-desk)

Source: MCP Registry. Synced Oct 29, 2026, 01:17 UTC.

Loop Desk MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Loop Desk MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Loop Desk MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Loop Desk MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Loop Desk MCP server have?

3 tools: 1 write, 2 read. register_loop, get_loop and list_due.

Does the Loop Desk MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Loop Desk MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Loop Desk MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.