The issue tracker AI coding agents pull work from: atomic claims, dependency-aware dispatch.
Listed on
- Official MCP Registry
- Smithery
- mcp.sovia MCP Toplist
First seen 2 Oct 2026. One server, whatever directories list it: each directory listing keeps its own page and history.
3
Directories
1 via MCP Toplist
1
Tools
From an anonymous probe
-
ToolBench grade
Not graded by Arcade
-
GitHub stars
No repository data
Tools
| Tool | Description | Behaviour |
|---|---|---|
| setup_status | No Retasc credential has reached this connection yet, so this is the only tool available and the only one that will work. Call it and follow what it returns. If your Retasc connection was added by URL in a platform's settings (a hosted agent, a claude.ai connector) rather than read from a config file on this machine, do NOT run bind: your human mints a key with `npx @retasc/cli@latest key mint --hosted --org-id <org> --project-id <project>` and adds it to that connection as the header `Authorization: Bearer <key>`. Otherwise, in short: YOU run `npx @retasc/cli@latest bind --json` in this folder, in the background, having first told your human that a browser is about to open. Post the approve URL it prints to them as a link, act on what it reports back, and when it finishes ask them to restart you so the rest of the tools load. The click and the restart are theirs; everything else is yours. | Not declared |
| Directory | Listing | Tier | First seen |
|---|---|---|---|
| Official MCP Registry | com.retasc/retasc | - | 2 Oct 2026 |
| Smithery | Retasc | - | 2 Oct 2026 |
| mcp.so | Listed there according to MCP Toplist’s dataset; not collected by InvokeRank. | ||