io.usefulapi/olark
REMOTE · OLARK.USEFULAPI.IO · SCANNED SEP 20
Manage Olark live-chat operators and groups (teams): list, create, update, and assign to teams.
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 429, 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
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 429. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.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.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.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.
How do I install the io.usefulapi/olark MCP server?
io.usefulapi/olark is a hosted endpoint at https://olark.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 · olark.usefulapi.io
claude mcp add --transport http io-usefulapi-olark 'https://olark.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-olark": {
"url": "https://olark.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-olark": {
"type": "http",
"url": "https://olark.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-olark] url = "https://olark.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-olark": {
"type": "remote",
"url": "https://olark.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-olark --url 'https://olark.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-olark:
url: "https://olark.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-olark": {
"Transport": "http",
"Url": "https://olark.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-olark -t streamable-http -u 'https://olark.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-olark": {
"type": "http",
"url": "https://olark.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.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 3 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.20 → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 2 Aug 26 0
- Authorization: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.20 ▲ functional
- 1 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.13 → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Jul 26 0
- 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 0
- 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 0
- Stability: unverified → 0.03 ▲ 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://olark.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 | 15 Sept 2026 | 14 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 9b5baa66142677ff0e44fb11cfa87bf4 |
| SANs: usefulapi.io, olark.usefulapi.io, *.olark.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 olark.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 No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 429 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://olark.usefulapi.io/mcp | HTTP error | 429 | |
| http (plaintext) | http://olark.usefulapi.io/mcp | Inconclusive | 429 |
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 →
add_operator_to_group Add operator to group ~106
MUTATES Olark data: adds an operator to a group (team). Olark API: POST /groups/{group_id}/operators (JSON body { operator_id }). Reversible via remove_operator_from_group. Adding to a nonexistent group returns 404.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | The group (team) id to add the operator to (path only; required). |
| operator_id | string | yes | The operator id to add (sent in the JSON body; required). |
No output schema declared.
No examples provided.
create_operator Create an operator ~137
MUTATES Olark data: creates a new operator (chat agent). Olark API: POST /operators (JSON). Required: email and password; nickname (display name) optional. NOTE: creating an operator CONSUMES A PAID SEAT (billing side effect). Returns the created operator.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The operator's login email (required). | |
| fields | object | – | Additional documented Olark fields to send in the JSON write body — merged OVER the typed fields above. |
| nickname | string | – | The operator's display name shown in chat. |
| password | string | yes | The operator's initial password (required). |
No output schema declared.
No examples provided.
get_operator Get an operator ~48
Fetch a single operator (chat agent) by id. Olark API: GET /operators/{id}. Returns id, email, nickname, available.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The operator id. |
No output schema declared.
No examples provided.
list_groups List groups ~92
List all groups (teams) on the Olark account. Olark API: GET /groups. Returns groups (each with id, name, and operator_ids — the members).
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Olark pagination page number, 1-based (offset-based paging; ~100 records/page). |
| params | object | – | Additional documented query-string filters to send verbatim (merged with the typed params above). |
No output schema declared.
No examples provided.
list_operators List operators ~106
List all operators (chat agents) on the Olark account. Olark API: GET /operators. Returns operators (each with id, email, nickname, available). Only operators under the authenticated account are returned (sub-accounts are not).
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Olark pagination page number, 1-based (offset-based paging; ~100 records/page). |
| params | object | – | Additional documented query-string filters to send verbatim (merged with the typed params above). |
No output schema declared.
No examples provided.
olark_request Raw read request ~98
Power-user escape hatch: GET any Olark API path not wrapped by a dedicated tool. READ-ONLY — only GET is allowed. Pass the FULL API path after the base, starting with a slash, INCLUDING any query string, e.g. "/operators?page=2" or "/groups". Returns the parsed JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Full API path after the base, starting with "/", e.g. "/operators?page=2". |
No output schema declared.
No examples provided.
remove_operator_from_group Remove operator from group ~98
MUTATES Olark data: removes an operator from a group (team). Olark API: DELETE /groups/{group_id}/operators/{operator_id}. Reversible via add_operator_to_group. Does NOT delete the operator, only their group membership.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | The group (team) id (path; required). |
| operator_id | string | yes | The operator id to remove from the group (path; required). |
No output schema declared.
No examples provided.
update_operator Update an operator ~159
MUTATES Olark data: updates an existing operator. Olark API: PUT /operators/{id} (JSON). Set nickname (display name) and/or available (online/offline status); use the `fields` passthrough for any other documented field. NOTE: Olark uses full PUT semantics — omitting a field may reset it to its default. The path id is never sent in the body.
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | New online/offline (availability) status. |
| fields | object | – | Additional documented Olark fields to send in the JSON write body — merged OVER the typed fields above. |
| id | string | yes | The operator id to update (path only; required). |
| nickname | string | – | New display name. |
No output schema declared.
No examples provided.
What is the io.usefulapi/olark MCP server?
io.usefulapi/olark is an MCP server listed in the public MCP registry as io.usefulapi/olark. Manage Olark live-chat operators and groups (teams): list, create, update, and assign to teams. This page covers its hosted endpoint (https://olark.usefulapi.io/mcp).
Is the io.usefulapi/olark MCP server safe to use?
io.usefulapi/olark 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 io.usefulapi/olark MCP server expose?
io.usefulapi/olark exposes 8 tools: list_operators, get_operator, list_groups, olark_request, create_operator, and 3 more. Their descriptions and schemas cost roughly 844 tokens of context every time the server is loaded.
Does the io.usefulapi/olark MCP server require authentication?
No. We connected to io.usefulapi/olark without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.usefulapi/olark MCP server still maintained?
io.usefulapi/olark 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.