io.usefulapi/loops
REMOTE · LOOPS.USEFULAPI.IO · SCANNED SEP 20
Manage Loops contacts, mailing lists, and transactional/event emails.
Available components
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 → Why this is hard to 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 enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. 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 Usability80
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/loops MCP server?
io.usefulapi/loops is a hosted endpoint at https://loops.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · loops.usefulapi.io
claude mcp add --transport http io-usefulapi-loops 'https://loops.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-loops": {
"url": "https://loops.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-loops": {
"type": "http",
"url": "https://loops.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-loops] url = "https://loops.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-loops": {
"type": "remote",
"url": "https://loops.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-loops --url 'https://loops.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-loops:
url: "https://loops.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-loops": {
"Transport": "http",
"Url": "https://loops.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-loops -t streamable-http -u 'https://loops.usefulapi.io/mcp'
{
"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.
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.
- 11 Sept 26 +3
- Authorization: fail → pass ▲ security
- 10 Sept 26 −3
- Authorization: pass → fail ▼ security
- 7 Sept 26 +58
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Schema quality: unverified → fail ▼ functional
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Schema quality: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 6 Sept 26 −3
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
- 5 Sept 26 −55
- Authorization: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: pass → fail ▼ security
- Schema quality: excellent → unverified ▼ functional
- Schema quality: fail → unverified ▼ functional
- Schema quality: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 2 Sept 26 +14
- Authorization: unverified → pass ▲ security
- Stability: fail → pass ▲ security
- 1 Sept 26 +41
- Injection markers: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: this server exposes a tool marked destructive (loops_create_contact) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated. security
- Schema quality: unverified → fail ▼ functional
- Schema quality: unverified → excellent ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → pass ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 31 Aug 26 −55
- Authorization: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: pass → fail ▼ security
- Schema quality: excellent → unverified ▼ functional
- Schema quality: fail → unverified ▼ functional
- Schema quality: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
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 20 Sept 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 | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | df5460e316c0b7630e22dad35a7f84c8 |
| 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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 |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
loops_create_contact Create a contact ~160
Creates a contact in Loops (additive). Loops API: POST /v1/contacts/create.
| Name | Type | Req | Description |
|---|---|---|---|
| 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.
| 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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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.
| 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 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.
| Name | Type | Req | Description |
|---|---|---|---|
| contactProperties | object | – | Contact properties to update alongside the event. |
| 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.
| 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. |
| 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 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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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.
What is the io.usefulapi/loops MCP server?
io.usefulapi/loops is an MCP server listed in the public MCP registry as io.usefulapi/loops. Manage Loops contacts, mailing lists, and transactional/event emails. This page covers its hosted endpoint (https://loops.usefulapi.io/mcp).
Is the io.usefulapi/loops MCP server safe to use?
io.usefulapi/loops scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.usefulapi/loops MCP server expose?
io.usefulapi/loops exposes 10 tools: loops_test_api_key, loops_find_contact, loops_list_contact_properties, loops_list_mailing_lists, loops_create_contact, and 5 more. Their descriptions and schemas cost roughly 926 tokens of context every time the server is loaded.
Does the io.usefulapi/loops MCP server require authentication?
Yes. io.usefulapi/loops asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/loops MCP server still maintained?
io.usefulapi/loops is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.