Home / MCP registry index / io.usefulapi/accredible
Accredible MCP by usefulapi
io.usefulapi/accredible in the official MCP registry.
Endpoint https://accredible.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Read Accredible credentials, groups, designs, analytics, skills; issue one credential as a draft.
We read its 19 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
accredible_get_issuer accredible_search_credentials accredible_get_credential accredible_get_credential_analytics accredible_list_analytics accredible_search_groups accredible_get_group accredible_search_designs accredible_get_design accredible_search_departments accredible_get_department accredible_search_collections accredible_search_attribute_keys accredible_list_skill_frameworks accredible_search_skills accredible_list_data_exports accredible_get_data_export accredible_get_team_member accredible_issue_credential
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-accredible)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.