Accredible MCP by usefulapi
io.usefulapi/accredibleusefulapi.iostreamable-httpv1.27.4Scanned
Read Accredible credentials, groups, designs, analytics, skills; issue one credential as a draft.
19 tools: 1 can delete or cancel things and 18 only read.
- Reads private data · 10
- Reads text others write · 5
- Can send data out · 0
- 37 findings, 4 high
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
1 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Accredible MCP by usefulapi can do
The Accredible MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 19 tools. It can delete or cancel things (1 tool: accredible_issue_credential). 18 tools only read.
10 tools read private data (accredible_get_issuer, accredible_search_credentials, accredible_get_credential and 7 more); 5 tools bring in text other people can write (accredible_get_issuer, accredible_get_credential, accredible_get_department and 2 more).
The fixed checks matched 37 findings, 4 of them high severity (credentials-mention and sensitive-path). Each one comes with the text it matched.
Last scanned Oct 25, 2026, version 1.27.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
19 tools
Deletes or cancels 1Claude Code: deny
accredible_issue_credentialWRITE: creates ONE credential (badge or certificate) for ONE recipient in an existing group.11 findings
Why it is in this group
- The description's first verb is "write": a word for a change.
- The server marks it destructive (destructiveHint: true).
Findings
- Info
The title mentions "credential".
What this check looks forMatched text
title: "Issue a credential to ONE recipient"
- Info
The annotations title mentions "credential".
What this check looks forMatched text
annotations.title: "Issue a credential to ONE recipient"
- High
The description refers to "/v1/credentials".
What this check looks forMatched text
description: "...s, bulk issuing, edits or deletes. POST /v1/credentials."
- Info
The description mentions "credential".
What this check looks forMatched text
description: "WRITE: creates ONE credential (badge or certificate) for ONE recipien..."
- Info
The input schema at properties.group_id.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.group_id.description: "The group the credential belongs to (accredible_search_groups);..."
- Info
The input schema at properties.recipient_name.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.recipient_name.description: "...recipient's full name as printed on the credential."
- Info
The input schema at properties.recipient_id.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.recipient_id.description: "...d for the recipient (maps recipients to credentials across e-mail changes)."
- Info
The input schema at properties.credential_id.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.credential_id.description: "Your own unique id for this credential (license_id); Accredible assigns one if..."
- Info
The input schema at properties.name.description mentions "Credential".
What this check looks forMatched text
inputSchema.properties.name.description: "Credential/course name; required only when the gro..."
- Info
The input schema at properties.description.description mentions "Credential".
What this check looks forMatched text
inputSchema.properties.description.description: "Credential/course description; required only when..."
- Info
The input schema at properties.private.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.private.description: "Make the credential private: visible only to the recipient..."
Description, as the server wrote it 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.
Annotations the server declares
- title: Issue a credential to ONE recipient
- readOnlyHint: false
- destructiveHint: true
Only reads 18Show 18 read-only tools
accredible_get_credentialOne credential in full: recipient, group, issue and expiry dates, published state, public URL, evidence items, references, custom attributes and skills.Reads private dataReads text others write5 findings
Why it is in this group
- The name "accredible_get_credential" says "get": a word for reading.
What it can reach
- private-dataThe name "accredible_get_credential" says "get" and "credential": it reads secrets.
- private-dataThe description's first sentence says "credential": it reads secrets.
- untrusted-inputThe description's first sentence says "issue": it reads issues, which other people can write.
Findings
- Info
The title mentions "credential".
What this check looks forMatched text
title: "Get a credential"
- Info
The annotations title mentions "credential".
What this check looks forMatched text
annotations.title: "Get a credential"
- High
The description refers to "/v1/credentials/".
What this check looks forMatched text
description: "...he custom id your organization set. GET /v1/credentials/{id}."
- Info
The description mentions "credential".
What this check looks forMatched text
description: "One credential in full: recipient, group, issue and ex..."
- Info
The input schema at properties.id.description mentions "Credential".
What this check looks forMatched text
inputSchema.properties.id.description: "Credential id (numeric) or the custom credential i..."
Description, as the server wrote it 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}.
Annotations the server declares
- title: Get a credential
- readOnlyHint: true
accredible_get_credential_analyticsThe analytics events of one credential (recipient views, shares, privacy changes, verification and so on) with timestamps.Reads private data5 findings
Why it is in this group
- The name "accredible_get_credential_analytics" says "get": a word for reading.
What it can reach
- private-dataThe name "accredible_get_credential_analytics" says "get" and "credential": it reads secrets.
- private-dataThe description's first sentence says "credential": it reads secrets.
Findings
- Info
The title mentions "credential".
What this check looks forMatched text
title: "Get a credential's analytics events"
- Info
The annotations title mentions "credential".
What this check looks forMatched text
annotations.title: "Get a credential's analytics events"
- High
The description refers to "/v1/credentials/analytics/".
What this check looks forMatched text
description: "...s. Read-only despite being a POST. POST /v1/credentials/analytics/{id}."
- Info
The description mentions "credential".
What this check looks forMatched text
description: "The analytics events of one credential (recipient views, shares, privacy chang..."
- Info
The input schema at properties.id.description mentions "Credential".
What this check looks forMatched text
inputSchema.properties.id.description: "Credential id (numeric) or the custom credential i..."
Description, as the server wrote it 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}.
Annotations the server declares
- title: Get a credential's analytics events
- readOnlyHint: true
accredible_get_data_exportOne data export: department, status and, once completed, the download links of its files.Reads private dataNo findings
Why it is in this group
- The name "accredible_get_data_export" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "file": it reads files.
Description, as the server wrote it One data export: department, status and, once completed, the download links of its files. GET /v1/data_exports/{id}.
Annotations the server declares
- title: Get a data export
- readOnlyHint: true
accredible_get_departmentOne department: name, description, URL, branding and meta_data.Reads text others writeNo findings
Why it is in this group
- The name "accredible_get_department" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
Description, as the server wrote it One department: name, description, URL, branding and meta_data. GET /v1/departments/{department_id}.
Annotations the server declares
- title: Get a department
- readOnlyHint: true
accredible_get_designOne badge or certificate design with its settings.No findings
Why it is in this group
- The name "accredible_get_design" says "get": a word for reading.
Description, as the server wrote it One badge or certificate design with its settings. GET /v1/designs/{design_id}.
Annotations the server declares
- title: Get a design
- readOnlyHint: true
accredible_get_groupOne group in full: name, course name and description, learning outcomes, design ids, language, skills and dates.No findings
Why it is in this group
- The name "accredible_get_group" says "get": a word for reading.
Description, as the server wrote it One group in full: name, course name and description, learning outcomes, design ids, language, skills and dates. GET /v1/issuer/groups/{group_id}.
Annotations the server declares
- title: Get a group
- readOnlyHint: true
accredible_get_issuerThe Accredible issuer (organization) behind the API key: id, name, e-mail, remaining credential credits (certificate_left), language and URL.Reads private dataReads text others write1 finding
Why it is in this group
- The name "accredible_get_issuer" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "mail": it reads mail.
- untrusted-inputThe description's first sentence says "mail": it reads inbound email, which other people can write.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...he API key: id, name, e-mail, remaining credential credits (certificate_left), language an..."
Description, as the server wrote it 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.
Annotations the server declares
- title: Get the issuer (account)
- readOnlyHint: true
accredible_get_team_memberOne team member of the account: name, e-mail and permissions per department.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "accredible_get_team_member" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "mail": it reads mail.
- untrusted-inputThe description's first sentence says "mail": it reads inbound email, which other people can write.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Get a team member
- readOnlyHint: true
accredible_list_analyticsAccount-wide credential analytics events (views, shares, downloads and similar), optionally for a date range, group or department.Reads private data5 findings
Why it is in this group
- The name "accredible_list_analytics" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "credential": it reads secrets.
Findings
- Info
The title mentions "credential".
What this check looks forMatched text
title: "List credential analytics events"
- Info
The annotations title mentions "credential".
What this check looks forMatched text
annotations.title: "List credential analytics events"
- Info
The description mentions "credential".
What this check looks forMatched text
description: "Account-wide credential analytics events (views, shares, downlo..."
- Info
The input schema at properties.group_id.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.group_id.description: "Only events of credentials in this group."
- Info
The input schema at properties.department_id.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.department_id.description: "Only events of credentials in this department."
Description, as the server wrote it 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.
Annotations the server declares
- title: List credential analytics events
- readOnlyHint: true
accredible_list_data_exportsData exports of the departments the key can access: department, status (scheduled, processing, completed, errored) and download links of completed files.Reads private dataNo findings
Why it is in this group
- The name "accredible_list_data_exports" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "file": it reads files.
Description, as the server wrote it 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.
Annotations the server declares
- title: List data exports
- readOnlyHint: true
accredible_list_skill_frameworksThe skills frameworks (O*NET, ESCO, NACE or your own) enabled for a department, each with its published versions.No findings
Why it is in this group
- The name "accredible_list_skill_frameworks" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List skill frameworks
- readOnlyHint: true
accredible_search_attribute_keysList 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.Reads private dataReads text others write1 finding
Why it is in this group
- The name "accredible_search_attribute_keys" says "search": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "credential": it reads secrets.
- untrusted-inputThe description's first sentence says "list" and "mail": it reads inbound email, which other people can write.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...aceholders such as a grade or date that credential designs and e-mails merge in); useful t..."
Description, as the server wrote it 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).
Annotations the server declares
- title: Search custom attribute keys
- readOnlyHint: true
accredible_search_collectionsList collections (sets of groups shown together).No findings
Why it is in this group
- The name "accredible_search_collections" says "search": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- title: Search collections
- readOnlyHint: true
accredible_search_credentialsSearch issued credentials (badges and certificates) with filters that combine with AND, newest first by default.Reads private data8 findings
Why it is in this group
- The name "accredible_search_credentials" says "search": a word for reading.
What it can reach
- private-dataThe name "accredible_search_credentials" says "search" and "credential": it reads secrets.
- private-dataThe description's first sentence says "search" and "credential": it reads secrets.
Findings
- Info
The title mentions "credentials".
What this check looks forMatched text
title: "Search credentials"
- Info
The annotations title mentions "credentials".
What this check looks forMatched text
annotations.title: "Search credentials"
- High
The description refers to "/v2/credentials/search".
What this check looks forMatched text
description: "...or and offset cannot be combined). POST /v2/credentials/search (a read-only search)."
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "Search issued credentials (badges and certificates) with filters..."
- Info
The input schema at properties.group_id.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.group_id.description: "Only credentials of this group (accredible_search_groups..."
- Info
The input schema at properties.license_id.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.license_id.description: "The custom credential id your organization set when issuing."
- Info
The input schema at properties.uuid.description mentions "Credential".
What this check looks forMatched text
inputSchema.properties.uuid.description: "Credential UUID."
- Info
The input schema at properties.published.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.published.description: "true = only published credentials, false = only unpublished drafts; omit..."
Description, as the server wrote it 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).
Annotations the server declares
- title: Search credentials
- readOnlyHint: true
accredible_search_departmentsList departments (independent organization units with their own designs, groups and branding).No findings
Why it is in this group
- The name "accredible_search_departments" says "search": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- title: Search departments
- readOnlyHint: true
accredible_search_designsList badge and certificate designs, optionally by kind or meta_data.No findings
Why it is in this group
- The name "accredible_search_designs" says "search": a word for reading.
Description, as the server wrote it List badge and certificate designs, optionally by kind or meta_data. POST /v1/designs/search (a read-only search).
Annotations the server declares
- title: Search designs
- readOnlyHint: true
accredible_search_groupsSearch groups (an achievement such as a course or qualification that credentials belong to).Reads private data1 finding
Why it is in this group
- The name "accredible_search_groups" says "search": a word for reading.
What it can reach
- private-dataThe description's first sentence says "search" and "credential": it reads secrets.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...such as a course or qualification that credentials belong to). Filters combine with AND; n..."
Description, as the server wrote it 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).
Annotations the server declares
- title: Search groups
- readOnlyHint: true
accredible_search_skillsSearch the skills of one published skills-framework version by name or the publisher's identifier (partial, case-insensitive, at least 2 characters).No findings
Why it is in this group
- The name "accredible_search_skills" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Search skills in a framework version
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data10
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write5
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:31 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://accredible.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://accredible.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
The description refers to "/v2/credentials/search".
What this check looks forMatched text
description: "...or and offset cannot be combined). POST /v2/credentials/search (a read-only search)."
The description refers to "/v1/credentials/".
What this check looks forMatched text
description: "...he custom id your organization set. GET /v1/credentials/{id}."
The description refers to "/v1/credentials/analytics/".
What this check looks forMatched text
description: "...s. Read-only despite being a POST. POST /v1/credentials/analytics/{id}."
The description refers to "/v1/credentials".
What this check looks forMatched text
description: "...s, bulk issuing, edits or deletes. POST /v1/credentials."
The description mentions "credential".
What this check looks forMatched text
description: "...he API key: id, name, e-mail, remaining credential credits (certificate_left), language an..."
The title mentions "credentials".
What this check looks forMatched text
title: "Search credentials"
Show 31 more findingsShow fewer
The annotations title mentions "credentials".
What this check looks forMatched text
annotations.title: "Search credentials"
The description mentions "credentials".
What this check looks forMatched text
description: "Search issued credentials (badges and certificates) with filters..."
The input schema at properties.group_id.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.group_id.description: "Only credentials of this group (accredible_search_groups..."
The input schema at properties.license_id.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.license_id.description: "The custom credential id your organization set when issuing."
The input schema at properties.uuid.description mentions "Credential".
What this check looks forMatched text
inputSchema.properties.uuid.description: "Credential UUID."
The input schema at properties.published.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.published.description: "true = only published credentials, false = only unpublished drafts; omit..."
The title mentions "credential".
What this check looks forMatched text
title: "Get a credential"
The annotations title mentions "credential".
What this check looks forMatched text
annotations.title: "Get a credential"
The description mentions "credential".
What this check looks forMatched text
description: "One credential in full: recipient, group, issue and ex..."
The input schema at properties.id.description mentions "Credential".
What this check looks forMatched text
inputSchema.properties.id.description: "Credential id (numeric) or the custom credential i..."
The title mentions "credential".
What this check looks forMatched text
title: "Get a credential's analytics events"
The annotations title mentions "credential".
What this check looks forMatched text
annotations.title: "Get a credential's analytics events"
The description mentions "credential".
What this check looks forMatched text
description: "The analytics events of one credential (recipient views, shares, privacy chang..."
The input schema at properties.id.description mentions "Credential".
What this check looks forMatched text
inputSchema.properties.id.description: "Credential id (numeric) or the custom credential i..."
The title mentions "credential".
What this check looks forMatched text
title: "List credential analytics events"
The annotations title mentions "credential".
What this check looks forMatched text
annotations.title: "List credential analytics events"
The description mentions "credential".
What this check looks forMatched text
description: "Account-wide credential analytics events (views, shares, downlo..."
The input schema at properties.group_id.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.group_id.description: "Only events of credentials in this group."
The input schema at properties.department_id.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.department_id.description: "Only events of credentials in this department."
The description mentions "credentials".
What this check looks forMatched text
description: "...such as a course or qualification that credentials belong to). Filters combine with AND; n..."
The description mentions "credential".
What this check looks forMatched text
description: "...aceholders such as a grade or date that credential designs and e-mails merge in); useful t..."
The title mentions "credential".
What this check looks forMatched text
title: "Issue a credential to ONE recipient"
The annotations title mentions "credential".
What this check looks forMatched text
annotations.title: "Issue a credential to ONE recipient"
The description mentions "credential".
What this check looks forMatched text
description: "WRITE: creates ONE credential (badge or certificate) for ONE recipien..."
The input schema at properties.group_id.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.group_id.description: "The group the credential belongs to (accredible_search_groups);..."
The input schema at properties.recipient_name.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.recipient_name.description: "...recipient's full name as printed on the credential."
The input schema at properties.recipient_id.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.recipient_id.description: "...d for the recipient (maps recipients to credentials across e-mail changes)."
The input schema at properties.credential_id.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.credential_id.description: "Your own unique id for this credential (license_id); Accredible assigns one if..."
The input schema at properties.name.description mentions "Credential".
What this check looks forMatched text
inputSchema.properties.name.description: "Credential/course name; required only when the gro..."
The input schema at properties.description.description mentions "Credential".
What this check looks forMatched text
inputSchema.properties.description.description: "Credential/course description; required only when..."
The input schema at properties.private.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.private.description: "Make the credential private: visible only to the recipient..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://accredible.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://accredible.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.27.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http accredible https://accredible.usefulapi.io/mcpclaude mcp add --transport http accredible https://accredible.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__accredible__accredible_get_issuer",
"mcp__accredible__accredible_search_credentials",
"mcp__accredible__accredible_get_credential",
"mcp__accredible__accredible_get_credential_analytics",
"mcp__accredible__accredible_list_analytics",
"mcp__accredible__accredible_search_groups",
"mcp__accredible__accredible_get_group",
"mcp__accredible__accredible_search_designs",
"mcp__accredible__accredible_get_design",
"mcp__accredible__accredible_search_departments",
"mcp__accredible__accredible_get_department",
"mcp__accredible__accredible_search_collections",
"mcp__accredible__accredible_search_attribute_keys",
"mcp__accredible__accredible_list_skill_frameworks",
"mcp__accredible__accredible_search_skills",
"mcp__accredible__accredible_list_data_exports",
"mcp__accredible__accredible_get_data_export",
"mcp__accredible__accredible_get_team_member"
],
"ask": [],
"deny": [
"mcp__accredible__accredible_issue_credential"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as accredible. Review it before you use it.
Capability tags behind 11 rules
- mcp__accredible__accredible_get_issuer private-data, untrusted-input
- mcp__accredible__accredible_search_credentials private-data
- mcp__accredible__accredible_get_credential private-data, untrusted-input
- mcp__accredible__accredible_get_credential_analytics private-data
- mcp__accredible__accredible_list_analytics private-data
- mcp__accredible__accredible_search_groups private-data
- mcp__accredible__accredible_get_department untrusted-input
- mcp__accredible__accredible_search_attribute_keys private-data, untrusted-input
- mcp__accredible__accredible_list_data_exports private-data
- mcp__accredible__accredible_get_data_export private-data
- mcp__accredible__accredible_get_team_member private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/accredible/verify?hash=972adf3d3ef4283c4adb22c03f27d45c610adc4457c10e184a8747fe27e3945a" | jq -e '.changed == false'Pinned hash 972adf3d3ef4, from Oct 25, 2026, 23:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/accredible/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/accredible)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.
Accredible MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Accredible MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 19 tools, 1 of which can change, send or delete something, and 37 findings (4 high) from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Accredible MCP by usefulapi delete data?
- Yes. 1 tool can delete, cancel or revoke something: accredible_issue_credential.
Can the Accredible MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Accredible MCP by usefulapi have?
- 19 tools: 1 destructive, 18 read. accredible_issue_credential, accredible_get_issuer, accredible_search_credentials, accredible_get_credential, accredible_get_credential_analytics, accredible_list_analytics, accredible_search_groups, accredible_get_group and 11 more.
Does the Accredible MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Accredible MCP by usefulapi send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Accredible MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.