Read Accredible credentials, groups, designs, analytics, skills; issue one credential as a draft. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"accredible": {
"url": "https://accredible.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"accredible": {
"type": "http",
"url": "https://accredible.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Accredible API key and Environment.
Create or copy a key in the Accredible Dashboard (dashboard.accredible.com, API keys). An account-wide key sees every department; a department key only its own. Choose the environment your key belongs to: US and EU production accounts use different hosts, and sandbox accounts (Connect and Growth plans) use their own keys. Your key is used only to call the Accredible API on your behalf; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Accredible API key and Environment. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Tool | Type | What it does |
|---|---|---|
accredible_get_issuer | read | 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 | read | 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). |
accredible_get_credential | read | 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}. |
accredible_get_credential_analytics | read | 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}. |
accredible_list_analytics | read | 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. |
accredible_search_groups | read | 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). |
accredible_get_group | read | 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}. |
accredible_search_designs | read | Search designs List badge and certificate designs, optionally by kind or meta_data. POST /v1/designs/search (a read-only search). |
accredible_get_design | read | Get a design One badge or certificate design with its settings. GET /v1/designs/{design_id}. |
accredible_search_departments | read | 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). |
accredible_get_department | read | Get a department One department: name, description, URL, branding and meta_data. GET /v1/departments/{department_id}. |
accredible_search_collections | read | 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). |
accredible_search_attribute_keys | read | 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). |
accredible_list_skill_frameworks | read | 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. |
accredible_search_skills | read | 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. |
accredible_list_data_exports | read | 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 | read | Get a data export One data export: department, status and, once completed, the download links of its files. GET /v1/data_exports/{id}. |
accredible_get_team_member | read | 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}. |
accredible_issue_credential | write | 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. |
accredible_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
accredible_request_feature | Request a missing feature Tell usefulapi that the user needs something the Accredible tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
accredible_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Accredible tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
accredible_cancel_subscription | Cancel the Pro subscription Cancel the caller's Accredible Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run accredible_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper account | $9/mo · $90/yr | Unlimited |
Pro covers this Accredible server only. Subscribe with accredible_upgrade (it returns a Stripe Checkout link). Cancel any time with accredible_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running accredible_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Accredible. The server calls the Accredible API with your own Accredible access, so it sees only the data that your account can see.
The login page asks for your Accredible API key and Environment. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Accredible API key and Environment. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Accredible API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Accredible.
Yes, if you approve it. 1 of the 19 Accredible tools can create or change data. The other 18 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Accredible server only. Run accredible_usage_status to see how many calls you used.
Ask the AI to run accredible_upgrade: it returns a Stripe Checkout link. To cancel, run accredible_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with accredible_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.