# Retasc > Retasc is a work queue for AI coding agents. The next agent picks up where the last one stopped. - name: com.retasc/retasc - version: 1.0.2 - connection class: R2 (oauth_consent_once) - trust: 82/100 flags: no-repository - quality: 82/100 (good) - owner: not claimed - descriptor: https://api.protogrid.dev/v1/servers/com.retasc%2Fretasc - tools: https://api.protogrid.dev/v1/servers/com.retasc%2Fretasc/tools **An agent can connect after a one-time OAuth consent by a human.** Remote endpoint behind OAuth 2. Tokens stay with the agent; the registry only exposes the authorization metadata. ## Connection (mcpServers) ```json { "mcpServers": { "retasc": { "type": "http", "url": "https://mcp.retasc.com/mcp" } } } ``` ## Trust - hygiene: 80 - liveness: 98 - freshness: 100 - provenance: 55 - drivers: +dns-namespace +website +reachable +uptime-96% +updated-0d-ago -no-repository - Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. ## Quality 82/100 (good) ### protocol: n/a (weight 25) - n/a `protocol.modern`, `protocol.stateless`, `protocol.transport`, `protocol.list_ttl`: no remote answered a protocol handshake (not probed yet, unreachable, or local-only) ### authorization: 83 (weight 15) - pass `auth.prm`: Protected Resource Metadata (RFC 9728) published - pass `auth.as_metadata`: authorization server metadata reachable - warn `auth.cimd`: only Dynamic Client Registration, deprecated in 2026-07-28 in favour of CIMD - n/a `auth.secret_in_url`: no templated URL ### tool hygiene: 71 (weight 30) - pass `tools.descriptions`: every tool has a description - pass `tools.description_length`: descriptions are concise - pass `tools.schemas`: every tool has an object input schema - fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones - fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: setup_status (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) - pass `tools.token_cost`: about 238 tokens to load every tool - pass `tools.api_dump`: tools are not a one-to-one API dump ### stability: 100 (weight 15) - pass `stability.changes`: 1 tool changes in 30 days - pass `stability.rug_pull`: no tool changed its meaning under the same name ### dependencies: n/a (weight 15) - n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package - tools: 1, about 238 tokens to load them all - tool set hash: 1fd06a20aeac1568572c1da822173bc7 - tools last changed: 2026-09-29T10:51:13.231Z - badge: [![protogrid quality](https://protogrid.dev/badge/com.retasc/retasc.svg)](https://protogrid.dev/servers/com.retasc/retasc) - Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. ### Tool changes - 2026-09-29 `setup_status` changed (description) - before: Retasc is not set up in this folder yet, so this is the only tool available and the only one that will work. Call it and follow what it returns. 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. - after: 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 --project-id ` and adds it to that connection as the header `Authorization: Bearer `. 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. Full history: https://api.protogrid.dev/v1/servers/com.retasc%2Fretasc/changes ## Remotes - https://mcp.retasc.com/mcp (streamable-http, auth oauth2, reachable true, uptime30d 0.95689654) ## Packages _none_ ## Tools (1) - `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 --project-id ` and adds it to that connection as the header `Authorization: Bearer `. 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.