# Accredible MCP by usefulapi (remote · accredible.usefulapi.io)

Read Accredible credentials, groups, designs, analytics, skills; issue one credential as a draft.

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `accredible.usefulapi.io`: 64/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-accredible/accredible.md), [page](https://verifymcp.io/servers/io-usefulapi-accredible/accredible)

## Channel facts

- Endpoint: `https://accredible.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2940 tokens (~154/item across 19 items; 19 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Accredible MCP by usefulapi server?

Accredible MCP by usefulapi is a hosted endpoint at https://accredible.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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-accredible 'https://accredible.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-accredible": {
      "url": "https://accredible.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-accredible": {
      "type": "http",
      "url": "https://accredible.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-accredible]
url = "https://accredible.usefulapi.io/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add io-usefulapi-accredible --url 'https://accredible.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-accredible:
    url: "https://accredible.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-accredible": {
      "Transport": "http",
      "Url": "https://accredible.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-accredible -t streamable-http -u 'https://accredible.usefulapi.io/mcp'
```

### Other

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

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 63, +3)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “getting_started”
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-13 (score 60, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 60)

First indexed and scored.

## MCP tools (19)

### `accredible_get_issuer` (~53 tokens)

Get the issuer (account)

The Accredible issuer (organization) behind the API key: id, name, e-mail, remaining credential credits (certificate_left), language and URL. Good first call. GET /v1/issuer/details.

### `accredible_search_credentials` (~433 tokens)

Search credentials

Search issued credentials (badges and certificates) with filters that combine with AND, newest first by default. Returns id, uuid, encoded_id, recipient name/e-mail, group, issued_on, expired_on, published state (approve), whether the recipient opened or engaged, and meta. Paging: size + offset (first 10 000 results) OR cursor: when the reply has next_cursor pass it as cursor for the next page (cursor and offset cannot be combined). POST /v2/credentials/search (a read-only search).

Input parameters:

- `created_after` (string): Created on or after this date (YYYY-MM-DD).
- `cursor` (string): The next_cursor of the previous reply. Not with offset.
- `expires_after` (string): Expires on or after this date (YYYY-MM-DD).
- `expires_before` (string): Expires on or before this date (YYYY-MM-DD).
- `group_id` (integer): Only credentials of this group (accredible_search_groups lists group ids).
- `issued_after` (string): Issued on or after this date (YYYY-MM-DD).
- `issued_before` (string): Issued on or before this date (YYYY-MM-DD).
- `license_id` (string): The custom credential id your organization set when issuing.
- `offset` (integer): Records to skip (offset paging, max 9950). Not with cursor.
- `published` (boolean): true = only published credentials, false = only unpublished drafts; omit for both.
- `recipient_email` (string): Exact recipient e-mail address.
- `recipient_id` (string): The recipient id your organization set when issuing.
- `recipient_name` (string): Exact recipient name.
- `size` (integer): Results per page, 1-100 (default 50).
- `sort_by` (string): Sort field (default: the API's order).
- `sort_order` (string): Sort direction (default desc when sort_by is set).
- `updated_after` (string): Updated on or after this date (YYYY-MM-DD).
- `uuid` (string): Credential UUID.

### `accredible_get_credential` (~85 tokens)

Get a credential

One credential in full: recipient, group, issue and expiry dates, published state, public URL, evidence items, references, custom attributes and skills. The id is the numeric credential id or the custom id your organization set. GET /v1/credentials/{id}.

Input parameters:

- `id` (string, required): Credential id (numeric) or the custom credential id (license_id).

### `accredible_get_credential_analytics` (~71 tokens)

Get a credential's analytics events

The analytics events of one credential (recipient views, shares, privacy changes, verification and so on) with timestamps. Read-only despite being a POST. POST /v1/credentials/analytics/{id}.

Input parameters:

- `id` (string, required): Credential id (numeric) or the custom credential id.

### `accredible_list_analytics` (~156 tokens)

List credential analytics events

Account-wide credential analytics events (views, shares, downloads and similar), optionally for a date range, group or department. Paged (default 100 per page). GET /v1/analytics.

Input parameters:

- `department_id` (integer): Only events of credentials in this department.
- `end_date` (string): Only events before this date (YYYY-MM-DD).
- `group_id` (integer): Only events of credentials in this group.
- `page` (integer): Page number, 1-based (default 1). Use meta.next_page from the previous reply.
- `page_size` (integer): Results per page (default 100).
- `start_date` (string): Only events after this date (YYYY-MM-DD).

### `accredible_search_groups` (~263 tokens)

Search groups

Search groups (an achievement such as a course or qualification that credentials belong to). Filters combine with AND; name and course_name match partially. Returns id, name, course name and description, design ids, language and dates. Paged: pass meta.next_page as page. POST /v1/issuer/groups/search (a read-only search).

Input parameters:

- `collection_ids` (array): Only groups linked to any of these collection UUIDs.
- `course_name` (string): Part of the course name.
- `department_id` (integer): Only groups of this department (must be accessible to the key).
- `ids` (array): Only these group ids.
- `meta_data` (object): Key/value strings you attached to the object's meta_data when you created it; matches objects carrying these pairs.
- `name` (string): Part of the group name.
- `page` (integer): Page number, 1-based (default 1). Use meta.next_page from the previous reply.
- `page_size` (integer): Results per page, 1-100 (default 50).
- `updated_after` (string): Only groups updated after this date (YYYY-MM-DD).
- `updated_before` (string): Only groups updated before this date (YYYY-MM-DD).

### `accredible_get_group` (~62 tokens)

Get a group

One group in full: name, course name and description, learning outcomes, design ids, language, skills and dates. GET /v1/issuer/groups/{group_id}.

Input parameters:

- `group_id` (integer, required): Group id (accredible_search_groups lists them).

### `accredible_search_designs` (~80 tokens)

Search designs

List badge and certificate designs, optionally by kind or meta_data. POST /v1/designs/search (a read-only search).

Input parameters:

- `kind` (string): Design kind, for example badge or certificate.
- `meta_data` (object): Key/value strings you attached to the object's meta_data when you created it; matches objects carrying these pairs.

### `accredible_get_design` (~50 tokens)

Get a design

One badge or certificate design with its settings. GET /v1/designs/{design_id}.

Input parameters:

- `design_id` (integer, required): Design id (accredible_search_designs or a group's design_id).

### `accredible_search_departments` (~139 tokens)

Search departments

List departments (independent organization units with their own designs, groups and branding). An account-wide key sees all, a department key only its own. Paged: pass meta.next_page as page. POST /v1/departments/search (a read-only search).

Input parameters:

- `meta_data` (object): Key/value strings you attached to the object's meta_data when you created it; matches objects carrying these pairs.
- `page` (integer): Page number, 1-based (default 1). Use meta.next_page from the previous reply.
- `page_size` (integer): Results per page, 1-100 (default 50).

### `accredible_get_department` (~53 tokens)

Get a department

One department: name, description, URL, branding and meta_data. GET /v1/departments/{department_id}.

Input parameters:

- `department_id` (integer, required): Department id (accredible_search_departments lists them).

### `accredible_search_collections` (~166 tokens)

Search collections

List collections (sets of groups shown together). Filters: ids, name (substring), public. Paged: pass meta.next_page as page. POST /v1/collections/search (a read-only search).

Input parameters:

- `ids` (array): Only these collection ids (UUIDs).
- `name` (string): Part of the collection name.
- `page` (integer): Page number, 1-based (default 1). Use meta.next_page from the previous reply.
- `page_size` (integer): Results per page, 1-100 (default 50).
- `public` (boolean): true = only public collections, false = only non-public.
- `sort_by` (string): Sort field.
- `sort_order` (string): Sort direction (default asc).

### `accredible_search_attribute_keys` (~147 tokens)

Search custom attribute keys

List the custom attribute keys (placeholders such as a grade or date that credential designs and e-mails merge in); useful to know which custom_attributes a credential can carry. Paged: pass meta.next_page as page. POST /v1/attribute_keys/search (a read-only search).

Input parameters:

- `department_id` (integer): Only keys of this department.
- `kind` (string): Attribute kind.
- `name` (string): Attribute key name.
- `page` (integer): Page number, 1-based (default 1). Use meta.next_page from the previous reply.
- `page_size` (integer): Results per page, 1-100 (default 50).

### `accredible_list_skill_frameworks` (~141 tokens)

List skill frameworks

The skills frameworks (O*NET, ESCO, NACE or your own) enabled for a department, each with its published versions. Needs a plan that includes skills frameworks (otherwise HTTP 403 plan_not_entitled). Paged, max 10 per page. GET /v1/skill_frameworks.

Input parameters:

- `department_id` (integer, required): Department to list frameworks for (required, also for department keys).
- `page` (integer): Page number, 1-based (default 1). Use meta.next_page from the previous reply.
- `page_size` (integer): Results per page, 1-10 (default 5).

### `accredible_search_skills` (~163 tokens)

Search skills in a framework version

Search the skills of one published skills-framework version by name or the publisher's identifier (partial, case-insensitive, at least 2 characters). Paged, max 50 per page. GET /v1/skill_frameworks/{id}/versions/{version_id}/skills.

Input parameters:

- `framework_id` (integer, required): Skill framework id (accredible_list_skill_frameworks).
- `page` (integer): Page number, 1-based (default 1). Use meta.next_page from the previous reply.
- `page_size` (integer): Results per page, 1-50 (default 50).
- `query` (string, required): Text to search for (min 2 characters).
- `version_id` (integer, required): Version id from the framework's versions array.

### `accredible_list_data_exports` (~58 tokens)

List data exports

Data exports of the departments the key can access: department, status (scheduled, processing, completed, errored) and download links of completed files. Exports are created in the Accredible Dashboard. GET /v1/data_exports.

### `accredible_get_data_export` (~55 tokens)

Get a data export

One data export: department, status and, once completed, the download links of its files. GET /v1/data_exports/{id}.

Input parameters:

- `id` (integer, required): Data export id (accredible_list_data_exports).

### `accredible_get_team_member` (~69 tokens)

Get a team member

One team member of the account: name, e-mail and permissions per department. Which members are visible depends on the key (an account-wide key sees all, a department key its own department). GET /v1/team_members/{id}.

Input parameters:

- `id` (integer, required): Team member id.

### `accredible_issue_credential` (~490 tokens)

Issue a credential to ONE recipient

WRITE: creates ONE credential (badge or certificate) for ONE recipient in an existing group. By default it is created UNPUBLISHED (a draft: no e-mail is sent and no credit is used); publish it later in the Accredible Dashboard. With publish=true the credential is published immediately: Accredible then SENDS AN E-MAIL to the recipient (as configured in the group's e-mail settings) and uses one credential credit of the account; an account without credits keeps it unpublished. A sandbox-mode setting in the Dashboard overrides publish. Not idempotent: calling twice creates two credentials (set credential_id to your own unique id to be able to find it again). No evidence, references, bulk issuing, edits or deletes. POST /v1/credentials.

Input parameters:

- `complete` (boolean): Whether the achievement is complete (default true); false marks it in progress.
- `credential_id` (string): Your own unique id for this credential (license_id); Accredible assigns one if omitted.
- `custom_attributes` (object): Custom attribute values merged into the design, e.g. {"Location": "London"} (keys must exist: accredible_search_attribute_keys).
- `description` (string): Credential/course description; required only when the group has no course description.
- `expired_on` (string): Expiry date YYYY-MM-DD (default none).
- `group_id` (integer, required): The group the credential belongs to (accredible_search_groups); it supplies the design and course texts.
- `issued_on` (string): Issue date YYYY-MM-DD (default today).
- `meta_data` (object): Key/value strings you attached to the object's meta_data when you created it; matches objects carrying these pairs.
- `name` (string): Credential/course name; required only when the group has no course name.
- `private` (boolean): Make the credential private: visible only to the recipient after signing in to credential.net.
- `publish` (boolean): Default false: create an unpublished draft (no e-mail). true: publish now, which e-mails the recipient and uses one credit.
- `recipient_email` (string, required): The recipient's e-mail address (exactly one recipient).
- `recipient_id` (string): Your own id for the recipient (maps recipients to credentials across e-mail changes).
- `recipient_name` (string, required): The recipient's full name as printed on the credential.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-accredible/accredible#diagnostics

## Score history

- 2026-10-17: 64
- 2026-10-16: 64
- 2026-10-15: 63
- 2026-10-14: 63
- 2026-10-13: 60
- 2026-10-12: 60

## Common questions

### What is the Accredible MCP by usefulapi server?

Accredible MCP by usefulapi is listed in the public MCP registry as io.usefulapi/accredible. Read Accredible credentials, groups, designs, analytics, skills; issue one credential as a draft. This page covers its hosted endpoint (https://accredible.usefulapi.io/mcp).

### Is the Accredible MCP by usefulapi server safe to use?

Accredible MCP by usefulapi scores 64 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 Accredible MCP by usefulapi server expose?

Accredible MCP by usefulapi exposes 19 tools: accredible_get_issuer, accredible_search_credentials, accredible_get_credential, accredible_get_credential_analytics, accredible_list_analytics, and 14 more. Their descriptions and schemas cost roughly 2,734 tokens of context every time the server is loaded.

### Does the Accredible MCP by usefulapi server require authentication?

Yes. Accredible 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 Accredible MCP by usefulapi server still maintained?

Accredible MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://accredible.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/accredible/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-accredible/accredible.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-accredible/accredible.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-accredible/accredible