io.usefulapi/loops

REMOTE · LOOPS.USEFULAPI.IO · SCANNED AUG 3

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

Available components

+4 this week 74 74 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security78

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability77

AI-judged instruction clarity (excellent).Pass
Tool/resource definitions use about 926 tokens (~92/item across 10 items; 10 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities60

Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · loops.usefulapi.io

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.toml

[mcp_servers.io-usefulapi-loops]
url = "https://loops.usefulapi.io/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-loops": {
      "type": "remote",
      "url": "https://loops.usefulapi.io/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add io-usefulapi-loops --url https://loops.usefulapi.io/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  io-usefulapi-loops:
    url: "https://loops.usefulapi.io/mcp"

// mcp.json

{
  "mcpServers": {
    "io-usefulapi-loops": {
      "type": "http",
      "url": "https://loops.usefulapi.io/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

3 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
2 Aug 26 +13
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.20 → unverified ▼ security
- Authorization: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- First check of Schema quality: unverified functional
1 Aug 26 −12
- Authorization: pass → unverified ▼ security
31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
28 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
27 Jul 26 +9
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 61

First indexed and scored.

Show 5 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://loops.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=usefulapi.io	CN=WE1,O=Google Trust Services,C=US	16 Jul 2026	14 Oct 2026	ECDSA 256	ECDSA-SHA256	9f50bb485254c8d1138eb110b8f2167d
SANs: usefulapi.io, loops.usefulapi.io, *.loops.usefulapi.io
CN=WE1,O=Google Trust Services,C=US (CA)	CN=GTS Root R4,O=Google Trust Services LLC,C=US	13 Dec 2023	20 Feb 2029	ECDSA 256	ECDSA-SHA384	7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA)	CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE	15 Nov 2023	28 Jan 2028	ECDSA 384	SHA256-RSA	7fe530bf331343bedd821610493d8a1b

DNSSEC insecure

Validation of loops.usefulapi.io. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
io.	present	57355	8	Verified
usefulapi.io.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result	Enforced and verified
Enforced	On tool calls
HTTP status	200

WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://loops.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"

Bearer realm="OAuth", resource_metadata="https://loops.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"

Protected resource metadata

Document	https://loops.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved	Yes
Resource	https://loops.usefulapi.io/mcp
Authorisation server	https://loops.usefulapi.io

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://loops.usefulapi.io/mcp	Verified	200
http (plaintext)	http://loops.usefulapi.io/mcp	Inconclusive	401

MCP tools — 10 exposed · ~926 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

loops_create_contact Create a contact ~160

Creates a contact in Loops (additive). Loops API: POST /v1/contacts/create.

Input Output Examples

Name	Type	Req	Description
email	string	yes	Contact email address (required).
firstName	string	—	First name.
lastName	string	—	Last name.
mailingLists	object	—	Map of mailing-list id -> subscribed boolean.
properties	object	—	Arbitrary custom contact properties (string/number/boolean); merged into the request body.
source	string	—	Source label for where the contact came from.
subscribed	boolean	—	Whether the contact is subscribed to email.
userGroup	string	—	User group segment name.
userId	string	—	Your app's user id for this contact.

No output schema declared.

No examples provided.

loops_create_contact_property Create a contact property ~66

Creates a custom contact property/field (additive schema change). Loops API: POST /v1/contacts/properties.

Input Output Examples

Name	Type	Req	Description
name	string	yes	Name of the custom property to create (required).
type	string	yes	Data type of the property (required).

No output schema declared.

No examples provided.

loops_delete_contact Delete a contact ~65

Deletes a contact from Loops. Destructive. Supply email OR userId. Loops API: POST /v1/contacts/delete.

Input Output Examples

Name	Type	Req	Description
email	string	—	Email of the contact to delete.
userId	string	—	userId of the contact to delete.

No output schema declared.

No examples provided.

loops_find_contact Find a contact ~69

Find a contact by email or userId (supply at least one). Loops API: GET /v1/contacts/find.

Input Output Examples

Name	Type	Req	Description
email	string	—	Contact email address to look up.
userId	string	—	Contact userId to look up (your app's user id).

No output schema declared.

No examples provided.

loops_list_contact_properties List contact properties ~53

List contact fields / custom properties defined in Loops. Loops API: GET /v1/contacts/properties.

Input Output Examples

Name	Type	Req	Description
list	string	—	Which properties to return: all (default) or custom only.

No output schema declared.

No examples provided.

loops_list_mailing_lists List mailing lists ~36

List all mailing lists in the Loops account (id + name). Loops API: GET /v1/lists.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

loops_send_event Send an event ~137

Sends an event to Loops for a contact — TRIGGERS any automations/loops subscribed to this event. Loops API: POST /v1/events/send.

Input Output Examples

Name	Type	Req	Description
contactProperties	object	—	Contact properties to update alongside the event.
email	string	—	Contact email (supply email or userId).
eventName	string	yes	The event name to send (required).
eventProperties	object	—	Properties attached to this event.
mailingLists	object	—	Map of mailing-list id -> subscribed boolean.
userId	string	—	Contact userId (supply email or userId).

No output schema declared.

No examples provided.

loops_send_transactional Send a transactional email ~131

SENDS a real transactional email via a Loops template. This dispatches an actual email to the recipient. Loops API: POST /v1/transactional.

Input Output Examples

Name	Type	Req	Description
addToAudience	boolean	—	Whether to add the recipient to your audience.
attachments	array	—	Optional attachments: array of { filename, contentType, data } objects.
dataVariables	object	—	Template data variables (string/number) to interpolate into the template.
email	string	yes	Recipient email address (required).
transactionalId	string	yes	The Loops transactional template id (required).

No output schema declared.

No examples provided.

loops_test_api_key Test API key ~39

Verify the configured Loops API key and return the team name — a good first call. Loops API: GET /v1/api-key.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

loops_update_contact Update a contact ~170

Updates (or creates) a contact by email/userId. Upserts — creates the contact if not found. Loops API: PUT /v1/contacts/update.

Input Output Examples

Name	Type	Req	Description
email	string	yes	Contact email address (required; identifies the contact).
firstName	string	—	First name.
lastName	string	—	Last name.
mailingLists	object	—	Map of mailing-list id -> subscribed boolean.
properties	object	—	Arbitrary custom contact properties (string/number/boolean); merged into the request body.
source	string	—	Source label.
subscribed	boolean	—	Whether the contact is subscribed to email.
userGroup	string	—	User group segment name.
userId	string	—	Your app's user id (alternative identifier).

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	61
27 Jul	70
28 Jul	71
29 Jul	71
30 Jul	69
31 Jul	72
1 Aug	60
2 Aug	73
3 Aug	74