Skip to content

Loops MCP by usefulapi

io.usefulapi/loopsusefulapi.iostreamable-httpv1.40.4Scanned

Manage Loops contacts, mailing lists, and transactional/event emails.

10 tools: 6 can delete or cancel things, 1 change things and 3 only read.

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

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

7 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Loops MCP by usefulapi can do

The Loops MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 10 tools. It can delete or cancel things (6 tools: loops_create_contact, loops_update_contact, loops_delete_contact, loops_create_contact_property and 2 more) and create or change data (1 tool: loops_test_api_key). 3 tools only read.

2 tools read private data (loops_find_contact and loops_list_contact_properties); 1 tool brings in text other people can write (loops_find_contact); 2 tools can send data out of your system (loops_send_event and loops_send_transactional). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

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

Last scanned Oct 25, 2026, version 1.40.4.

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.

10 tools

Deletes or cancels 6Claude Code: deny
  • loops_create_contactCreates a contact in Loops (additive).No findings

    Why it is in this group

    • The name "loops_create_contact" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Creates a contact in Loops (additive). Loops API: POST /v1/contacts/create.

    Annotations the server declares

    • title: Create a contact
    • destructiveHint: true
  • loops_create_contact_propertyCreates a custom contact property/field (additive schema change).No findings

    Why it is in this group

    • The name "loops_create_contact_property" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Creates a custom contact property/field (additive schema change). Loops API: POST /v1/contacts/properties.

    Annotations the server declares

    • title: Create a contact property
    • destructiveHint: true
  • loops_delete_contactDeletes a contact from Loops.No findings

    Why it is in this group

    • The name "loops_delete_contact" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Deletes a contact from Loops. Destructive. Supply email OR userId. Loops API: POST /v1/contacts/delete.

    Annotations the server declares

    • title: Delete a contact
    • destructiveHint: true
  • loops_send_eventSends an event to Loops for a contact — TRIGGERS any automations/loops subscribed to this event.Can send data outNo findings

    Why it is in this group

    • The name "loops_send_event" says "send": a word for sending, and what is sent cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • outboundThe name "loops_send_event" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Sends an event to Loops for a contact — TRIGGERS any automations/loops subscribed to this event. Loops API: POST /v1/events/send.

    Annotations the server declares

    • title: Send an event
    • destructiveHint: true
  • loops_send_transactionalSENDS a real transactional email via a Loops template.Can send data outNo findings

    Why it is in this group

    • The name "loops_send_transactional" says "send": a word for sending, and what is sent cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • outboundThe name "loops_send_transactional" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    SENDS a real transactional email via a Loops template. This dispatches an actual email to the recipient. Loops API: POST /v1/transactional.

    Annotations the server declares

    • title: Send a transactional email
    • destructiveHint: true
  • loops_update_contactUpdates (or creates) a contact by email/userId.No findings

    Why it is in this group

    • The name "loops_update_contact" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Updates (or creates) a contact by email/userId. Upserts — creates the contact if not found. Loops API: PUT /v1/contacts/update.

    Annotations the server declares

    • title: Update a contact
    • destructiveHint: true
Changes things 1Claude Code: ask
  • loops_test_api_keyVerify the configured Loops API key and return the team name — a good first call.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Verify the configured Loops API key and return the team name — a good first call. Loops API: GET /v1/api-key.

    Annotations the server declares

    • title: Test API key
    • readOnlyHint: true
Only reads 3Show 3 read-only tools
  • loops_find_contactFind a contact by email or userId (supply at least one).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "loops_find_contact" says "find": a word for reading.

    What it can reach

    • private-dataThe name "loops_find_contact" says "find" and "contact": it reads contacts.
    • private-dataThe description's first sentence says "find" and "contact": it reads contacts.
    • untrusted-inputThe description's first sentence says "find" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Find a contact by email or userId (supply at least one). Loops API: GET /v1/contacts/find.

    Annotations the server declares

    • title: Find a contact
    • readOnlyHint: true
  • loops_list_contact_propertiesList contact fields / custom properties defined in Loops.Reads private dataNo findings

    Why it is in this group

    • The name "loops_list_contact_properties" says "list": a word for reading.

    What it can reach

    • private-dataThe name "loops_list_contact_properties" says "list" and "contact": it reads contacts.
    • private-dataThe description's first sentence says "list" and "contact": it reads contacts.
    Description, as the server wrote it
    List contact fields / custom properties defined in Loops. Loops API: GET /v1/contacts/properties.

    Annotations the server declares

    • title: List contact properties
    • readOnlyHint: true
  • loops_list_mailing_listsList all mailing lists in the Loops account (id + name).No findings

    Why it is in this group

    • The name "loops_list_mailing_lists" says "list": a word for reading.
    Description, as the server wrote it
    List all mailing lists in the Loops account (id + name). Loops API: GET /v1/lists.

    Annotations the server declares

    • title: List mailing lists
    • readOnlyHint: true

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.

4 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 untrusted-input tool breaks every one.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__loops__loops_find_contact"
    ]
  }
}

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.

The remote endpoint did not answer the last look

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

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
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

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 7 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://loops.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://loops.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

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. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 7 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://loops.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://loops.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

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

claude mcp add --transport http loops https://loops.usefulapi.io/mcp
claude mcp add --transport http loops https://loops.usefulapi.io/mcp

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__loops__loops_find_contact",
      "mcp__loops__loops_list_contact_properties",
      "mcp__loops__loops_list_mailing_lists"
    ],
    "ask": [
      "mcp__loops__loops_test_api_key"
    ],
    "deny": [
      "mcp__loops__loops_create_contact",
      "mcp__loops__loops_update_contact",
      "mcp__loops__loops_delete_contact",
      "mcp__loops__loops_create_contact_property",
      "mcp__loops__loops_send_event",
      "mcp__loops__loops_send_transactional"
    ]
  }
}

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 loops. Review it before you use it.

Capability tags behind 4 rules
  • mcp__loops__loops_find_contact private-data, untrusted-input
  • mcp__loops__loops_list_contact_properties private-data
  • mcp__loops__loops_send_event outbound
  • mcp__loops__loops_send_transactional outbound

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/io.usefulapi/loops/verify?hash=754b771647b27d857baf1ac2d46665fe93ba0b11908a66470b001367a7d35e1b" | jq -e '.changed == false'

Pinned hash 754b771647b2, from Oct 25, 2026, 23:19 UTC.

Watch

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

https://radar.anlyon.com/servers/io.usefulapi/loops/changes.xml

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

Badge

Anlyon Radar badge for io.usefulapi/loops
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/loops.svg)](https://radar.anlyon.com/servers/io.usefulapi/loops)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

Loops MCP by usefulapi: questions and answers

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

Is the Loops MCP by usefulapi safe?

No scan can promise that. What its definitions show: 10 tools, 7 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 Loops MCP by usefulapi delete data?

Yes. 6 tools can delete, cancel or revoke something: loops_create_contact, loops_update_contact, loops_delete_contact, loops_create_contact_property, loops_send_event and loops_send_transactional.

Can the Loops MCP by usefulapi 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 Loops MCP by usefulapi have?

10 tools: 6 destructive, 1 write, 3 read. loops_create_contact, loops_update_contact, loops_delete_contact, loops_create_contact_property, loops_send_event, loops_send_transactional, loops_test_api_key, loops_find_contact and 2 more.

Does the Loops MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Loops MCP by usefulapi send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): loops_send_event and loops_send_transactional.

Has the Loops MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.