Home / MCP registry index / io.usefulapi/axis-lms
Axis LMS MCP by usefulapi
io.usefulapi/axis-lms in the official MCP registry.
Endpoint https://axis-lms.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Read Axis LMS users, courses, learning paths, certifications and reports; manage enrollments.
We read its 44 tools on 2026-10-31. 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.
Connect it
The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:
claude mcp add --transport http axis-lms https://axis-lms.usefulapi.io/mcp{
"mcpServers": {
"axis-lms": {
"url": "https://axis-lms.usefulapi.io/mcp"
}
}
}code --add-mcp '{"name":"axis-lms","type":"http","url":"https://axis-lms.usefulapi.io/mcp"}'Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.
Let Claude Code check servers as it adds them
With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.
claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-pluginsTools it advertises
axislms_list_users axislms_get_user axislms_search_users axislms_count_users axislms_list_courses axislms_count_courses axislms_get_course axislms_list_course_users axislms_list_usergroups axislms_get_usergroup axislms_list_usergroup_members axislms_list_learningpaths axislms_list_learningpath_users axislms_list_certifications axislms_get_certification axislms_list_certification_users axislms_list_user_certificates axislms_list_user_ceus axislms_list_ilt_programs axislms_get_ilt_program axislms_list_ilt_sessions axislms_list_ilt_meetings axislms_list_ilt_completions axislms_list_user_ilt_sessions axislms_list_organizations axislms_list_organization_branches axislms_list_organization_users axislms_course_report axislms_certification_report axislms_learningpath_report axislms_ilt_report axislms_user_report axislms_enroll_user_in_course axislms_unenroll_user_from_course axislms_enroll_user_in_learningpath axislms_unenroll_user_from_learningpath axislms_enroll_user_in_ilt_session axislms_unenroll_user_from_ilt_session axislms_mark_ilt_attendance axislms_create_user axislms_update_user axislms_create_usergroup axislms_add_usergroup_member axislms_remove_usergroup_member
Tool changes
We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.
Fingerprint of its tools at our last full read (2026-10-31):
096de9da43fd583a. A client can hash the tools it is served the same way and compare;
the full value and a hash per tool are in this page as JSON.
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-axis-lms)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.