Robly MCP by usefulapi
REMOTE · ROBLY.USEFULAPI.IO
Find Robly contacts and lists; subscribe, update and move contacts between lists.
Available components
Last scanned (14 minutes ago)
Scores higher than 47% of remote servers
Reachable. Last reached 25 Oct 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 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 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
- 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 & 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 Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1926 tokens (~148/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 14 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
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.
- 25 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.2.0 → 1.2.3 functional
- 24 Oct 26 62
First indexed and scored.
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 25 Oct 2026 · Probed https://robly.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 robly.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 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 | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://robly.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://robly.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://robly.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://robly.usefulapi.io/mcp |
| Authorisation server | https://robly.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://robly.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/robly/ |
| http (plaintext) | http://robly.usefulapi.io/mcp | Inconclusive | 302 | http://robly.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 →
robly_add_contact_to_list Add contact to list ~131
WRITE: put an existing contact on a list. With include_autoresponder Robly triggers autoresponders matching the newly listed contact, which EMAIL the contact. POST /api/v1/contacts/add_sub_list.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | The contact's email address. Give this OR member_id. | |
| include_autoresponder | boolean | – | Trigger matching autoresponders (they email the contact). |
| member_id | integer | – | Robly contact (member) id. Give this OR email. |
| sub_list_id | integer | yes | Sub list id from robly_list_sub_lists. |
No output schema declared.
No examples provided.
robly_check_list_membership Check list membership ~96
Whether one contact (by email or member id) is on one list. GET /api/v1/contacts/exists_in_sub_list.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | The contact's email address. Give this OR member_id. | |
| member_id | integer | – | Robly contact (member) id. Give this OR email. |
| sub_list_id | integer | yes | Sub list id from robly_list_sub_lists. |
No output schema declared.
No examples provided.
robly_create_sub_list Create sub list ~68
WRITE: create a new, empty sub list. Robly does not say whether a list with the same name already exists, so check robly_list_sub_lists first. POST /api/v1/sub_lists/add_sub_list.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name of the new list. |
No output schema declared.
No examples provided.
robly_find_contact Find contact ~129
Look up one contact by email address or member id: status, subscription date, sign-up source and, on request, the lists and data fields. Returns found: false when Robly has no such contact. GET /api/v1/contacts/search.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | The contact's email address. Give this OR member_id. | |
| include_fields | boolean | – | Include the contact's data fields. |
| include_sub_lists | boolean | – | Include the lists the contact is on. |
| member_id | integer | – | Robly contact (member) id. Give this OR email. |
No output schema declared.
No examples provided.
robly_get_signup_form Get sign-up form ~61
The data fields and sub lists a new subscriber can be given through the sign-up API (public ones unless include_all is true). GET /api/v1/sign_up/show.
| Name | Type | Req | Description |
|---|---|---|---|
| include_all | boolean | – | Also include non-public fields and lists. |
No output schema declared.
No examples provided.
robly_list_contacts List contacts ~253
List contacts (members) of the Robly account, newest first as Robly orders them: id, email, subscribed/deleted flags, subscription date, sign-up source, timestamps. Filter by status, by list, or by last-updated time; optionally include each contact's lists and data fields. Pages with limit (max 100) and offset: pass next_offset from the previous reply. Robly does not return a total. GET /api/v1/contacts/show.
| Name | Type | Req | Description |
|---|---|---|---|
| include_fields | boolean | – | Include each contact's data fields (name, custom fields). |
| include_sub_lists | boolean | – | Include the lists each contact is on. |
| limit | integer | – | Contacts per page, 1-100 (default 25). |
| list_id | integer | – | Only contacts on this list (sub list id from robly_list_sub_lists). |
| offset | integer | – | Contacts to skip (default 0). |
| status | string | – | Only contacts with this status (default all). |
| updated_since | string | – | Only contacts changed since this ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z. |
No output schema declared.
No examples provided.
robly_list_fields List data fields ~80
List the contact data fields (First Name, Last Name, custom fields): id, label, type, required flag and the user_tag that robly_subscribe_contact and robly_update_contact use as the field key. GET /api/v1/fields/show.
| Name | Type | Req | Description |
|---|---|---|---|
| include_all | boolean | – | Also include fields hidden from public sign-up forms. |
No output schema declared.
No examples provided.
robly_list_sub_lists List sub lists ~74
List the account's sub lists (the lists contacts belong to): id, name, position, timestamps. Public lists only unless include_all is true. Use the ids for list filters and for adding contacts. GET /api/v1/sub_lists/show.
| Name | Type | Req | Description |
|---|---|---|---|
| include_all | boolean | – | Also include non-public lists. |
No output schema declared.
No examples provided.
robly_remove_contact_from_list Remove contact from list ~94
WRITE: take a contact off one list (the contact itself is kept). POST /api/v1/contacts/remove_sub_list.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | The contact's email address. Give this OR member_id. | |
| member_id | integer | – | Robly contact (member) id. Give this OR email. |
| sub_list_id | integer | yes | Sub list id from robly_list_sub_lists. |
No output schema declared.
No examples provided.
robly_rename_sub_list Rename sub list ~59
WRITE: rename a sub list. POST /api/v1/sub_lists/rename_sub_list.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The new name. |
| sub_list_id | integer | yes | Sub list id from robly_list_sub_lists. |
No output schema declared.
No examples provided.
robly_subscribe_contact Subscribe contact ~262
WRITE: add a new subscribed contact (or re-submit an existing one through the sign-up form). With double_opt_in Robly EMAILS the contact a confirmation link first; with welcome_email it EMAILS the welcome message right away; with include_autoresponder it triggers matching autoresponders, which email the contact. Only subscribe people who agreed to receive email. Field values go in `fields`, keyed by the user_tag from robly_list_fields (for example fname, lname). POST /api/v1/sign_up/generate.
| Name | Type | Req | Description |
|---|---|---|---|
| double_opt_in | boolean | – | Send a confirmation email; the contact is subscribed only after clicking it, then gets the welcome email. |
| string | yes | The new contact's email address. | |
| fields | object | – | Data field values keyed by user_tag, e.g. {"fname": "Ada", "lname": "Lovelace"}. |
| include_autoresponder | boolean | – | Trigger matching autoresponders (they email the contact). |
| return_contact | boolean | – | Return the created contact. |
| sub_list_ids | array | – | Lists to put the contact on (ids from robly_list_sub_lists). |
| welcome_email | boolean | – | Skip confirmation and send the welcome email now. |
No output schema declared.
No examples provided.
robly_unsubscribe_contact Unsubscribe contact ~103
WRITE: unsubscribe a contact so Robly stops emailing it. Robly's API cannot undo this: an unsubscribed contact can only come back through a sign-up form. Use it for a contact that asked to stop. POST /api/v1/contacts/unsubscribe.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | The contact's email address. Give this OR member_id. | |
| member_id | integer | – | Robly contact (member) id. Give this OR email. |
No output schema declared.
No examples provided.
robly_update_contact Update contact ~250
WRITE: change an existing contact's data fields and/or list memberships in one call. Name the contact by member_id (look it up with robly_find_contact). `fields` are keyed by user_tag (robly_list_fields); the email address cannot be changed here. add_to_list_ids puts the contact on those lists, remove_from_list_ids takes it off them. remove_from_all_other_lists also removes the contact from every list NOT named in add_to_list_ids (requires add_to_list_ids). include_autoresponder triggers autoresponders that EMAIL the contact. POST /api/v1/contacts/update_full_contact.
| Name | Type | Req | Description |
|---|---|---|---|
| add_to_list_ids | array | – | Lists to put the contact on. |
| fields | object | – | Data field values keyed by user_tag, e.g. {"fname": "Ada"}. |
| include_autoresponder | boolean | – | Trigger matching autoresponders (they email the contact). |
| member_id | integer | yes | Robly contact (member) id. |
| remove_from_all_other_lists | boolean | – | Also remove the contact from every list not in add_to_list_ids. |
| remove_from_list_ids | array | – | Lists to take the contact off. |
No output schema declared.
No examples provided.
How do I install the Robly MCP by usefulapi server?
Robly MCP by usefulapi is a hosted endpoint at https://robly.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 · robly.usefulapi.io
claude mcp add --transport http io-usefulapi-robly 'https://robly.usefulapi.io/mcp'
What is the Robly MCP by usefulapi server?
Robly MCP by usefulapi is listed in the public MCP registry as io.usefulapi/robly. Find Robly contacts and lists; subscribe, update and move contacts between lists. This page covers its hosted endpoint (https://robly.usefulapi.io/mcp).
Is the Robly MCP by usefulapi server safe to use?
Robly MCP by usefulapi scores 63 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 Robly MCP by usefulapi server expose?
Robly MCP by usefulapi exposes 13 tools: robly_list_contacts, robly_find_contact, robly_check_list_membership, robly_list_sub_lists, robly_list_fields, and 8 more. Their descriptions and schemas cost roughly 1,660 tokens of context every time the server is loaded.
Does the Robly MCP by usefulapi server require authentication?
Yes. Robly MCP by usefulapi 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 Robly MCP by usefulapi server still maintained?
Robly MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.