Loops MCP by usefulapi
REMOTE · LOOPS.USEFULAPI.IO
Manage Loops contacts, mailing lists, and transactional/event emails.
Available components
Last scanned (3 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. 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
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 2 Nov 26 −62
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “add_or_update_a_contact” functional
- New prompt “check_lists_or_add_a_contact_property” functional
- New prompt “look_up_a_contact_in_loops” functional
- New prompt “send_a_transactional_email” functional
- New prompt “send_an_event_to_start_automations” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 0
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 0
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.0 → 1.21.3 functional
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.20.0 → 1.21.0 functional
- Server version: 1.19.0 → 1.20.0 functional
- Server version: 1.17.0 → 1.19.0 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 5 Nov 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 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.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. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
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 | Redirected | 302 | https://usefulapi.io/loops/ |
| http (plaintext) | http://loops.usefulapi.io/mcp | Inconclusive | 302 | http://loops.usefulapi.io/mcp |
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.
How do I install the Loops MCP by usefulapi server?
Loops MCP by usefulapi 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'
What is the Loops MCP by usefulapi server?
Loops MCP by usefulapi is 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 Loops MCP by usefulapi server safe to use?
Loops MCP by usefulapi scores 18 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 Loops MCP by usefulapi server expose?
Loops MCP by usefulapi 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 Loops MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Loops MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Loops MCP by usefulapi server still maintained?
Loops MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Loops MCP by usefulapi server?
VerifyMCP ran 4 checks on Loops MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Loops MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.