app.slxd/training
SLXD Training
Is the SLXD Training MCP server down? No. It is up and needs your URL, probed 2026-10-26.
Manage training records, groups, enrolments and certificates from an AI assistant.
needs your URL probed 2026-11-15 · unchanged since 2026-10-26
The URL has placeholders that each user fills in: {tenant}.- Endpoint
- https://{tenant}.slxd.app/mcp/training (streamable-http)
- Host
- {tenant}.slxd.app
- Website
- https://slxd.app/training
- Registry
- active, updated 2026-10-18 · registry entry
- Changes
- 2 recorded, reachable in 0 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Other registry entries on {tenant}.slxd.app.
- SLXD People app.slxd/people · needs your URL
- SLXD Projects app.slxd/projects · needs your URL
- SLXD ShareSCORM app.slxd/sharescorm · needs your URL
- SLXD Tender app.slxd/tender · needs your URL
Servers that mention training.
- Coach MCP ai.iamcoach/coach · needs auth
- Povver — Strength Training ai.povver/mcp-server · needs auth
- Servana ai.servana/servana · alive
- Evertrain app.evertrain/evertrain · needs auth
- MoveMate: Gym Workout Tracker app.movemate/movemate · needs auth
- NoteFit app.notefit/notefit · needs auth
- Somvia app.somvia/health · needs auth
- TriPeak app.tripeak/tripeak · needs auth
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-10-26 08:58 | needs your URL | ||||
| 2026-10-19 09:59 | no DNS |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- Every URL of the registry entry has a placeholder that each user fills in, such as a tenant, a project or a host of their own. Without that value there is nothing to call, so the probe does not call the URL, and the entry is not counted as down. A client asks the user for the value.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.