Search / com.retasc/retasc
protogridR2· OAuth, onceRetasc is a work queue for AI coding agents. The next agent picks up where the last one stopped.
v1.0.2 · active · website · descriptor JSON · versions
{
"mcpServers": {
"retasc": {
"type": "http",
"url": "https://mcp.retasc.com/mcp"
}
}
}claude mcp add --transport http retasc https://mcp.retasc.com/mcp[mcp_servers.retasc]
url = "https://mcp.retasc.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"retasc": {
"type": "remote",
"url": "https://mcp.retasc.com/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"retasc": {
"type": "http",
"url": "https://mcp.retasc.com/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=retasc&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbWNwLnJldGFzYy5jb20vbWNwIn0%3D"
}{
"servers": {
"retasc": {
"type": "http",
"url": "https://mcp.retasc.com/mcp"
}
}
}{
"mcpServers": {
"retasc": {
"httpUrl": "https://mcp.retasc.com/mcp"
}
}
}extensions:
"retasc":
enabled: true
name: "retasc"
type: streamable_http
uri: "https://mcp.retasc.com/mcp"
timeout: 300
protocol.modern, protocol.stateless, protocol.transport, protocol.list_ttlno remote answered a protocol handshake (not probed yet, unreachable, or local-only)auth.prmProtected Resource Metadata (RFC 9728) publishedauth.as_metadataauthorization server metadata reachableauth.cimdonly Dynamic Client Registration, deprecated in 2026-07-28 in favour of CIMDauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_lengthdescriptions are concisetools.schemasevery tool has an object input schematools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky onestools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: setup_status (readOnlyHint, destructiveHint, idempotentHint, openWorldHint)tools.token_costabout 238 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changes1 tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packagesetup_statuschangeddescriptionRetasc 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.
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.
Full history: list_changes · trend: quality JSON.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+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. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://mcp.retasc.com/mcp streamable-http | oauth2 AS: https://mcp.retasc.com | yes | 96% | 282 ms | – | 2026-10-20 |
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. |
Schemas: list_tools.
{
"name": "com.retasc/retasc",
"icons": [
{
"src": "https://retasc.com/icon-512.png",
"sizes": [
"512x512"
],
"mimeType": "image/png"
}
],
"title": "Retasc",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://mcp.retasc.com/mcp",
"type": "streamable-http"
}
],
"version": "1.0.2",
"websiteUrl": "https://retasc.com",
"description": "Retasc is a work queue for AI coding agents. The next agent picks up where the last one stopped."
}