Server definition

Hash: sha256:03ff0190972847f8c3c6806d39317509cd6c3d3ce78bcab50b051ea86253e3ae
What it is: What a remote MCP server returned when asked what it offers: 1 tools

The blob, as servednamed by its sha256

{
  "instructions": "You are connected to Retasc, but no working credential reached it, so none of the tools will work yet. FIRST work out which kind of connection you are on, because the fix is different:\nA. Your Retasc MCP server is defined in a config file on the machine or container your shell runs in, loaded when your client starts. This is Claude Code, Codex, Cursor, Gemini CLI, Grok, OpenCode or Pi run locally or in a container. Then set up this folder now, without waiting to be asked (steps 1–5).\nB. Your Retasc connection was added by URL in a platform's settings: a hosted agent, a web or phone chat, or a claude.ai connector. Nothing you write to disk changes it. Then do NOT run bind. It would sign your human in and bind a folder this connection never reads, and every new session would land back here. The connection needs a Retasc key in its settings, and only your human can put it there. On any computer with Node 18+, they sign in with `npx @retasc/cli@latest login`, then run `npx @retasc/cli@latest key mint --hosted --org-id <org> --project-id <project>`. `npx @retasc/cli@latest whoami` prints the org id, and the project id can be copied from the Projects page at https://dash.retasc.com. The key is shown only once. Then, in the platform's settings for this Retasc connection, they add a header named `Authorization` whose value is `Bearer ` followed by the key, and start a new session. If the platform cannot add a header to a remote MCP server, tell them plainly that it cannot connect to Retasc yet. Do not send them round the setup again.\nNot sure which? If you already ran bind to the end and a NEW session still lands here, you are on B.\nSteps for A:\n1. FIRST tell your human that a browser window is about to open and they will need to click Approve. Say it before you start, not after — they cannot click something they were not told was coming.\n2. Then run this yourself, IN THE BACKGROUND, from the folder you are working in: `npx @retasc/cli@latest bind --json`\nBackground it, do not block on it: it waits for that click, and while it waits it prints the approve URL. Read that URL from its output and post it to your human as a link — the browser also opens on its own, but the link is what works when it does not.\n3. It needs Node 18+. If Node is missing, ASK before installing it. Say it takes about a minute and needs no admin password, and only install it if they agree.\n4. It reports what it did and what it still needs, and when it stops to ask, it hands you the QUESTIONS as data in `askHuman`: exact wording, exact options, and the flag each answer fills. They are meant to be asked TOGETHER, as one set — most carry a suggested value already filled in, so answering is usually a click each. Use your question or picker tool, passing ALL of them in a single call if it takes more than one; fall back to a numbered list only if you have no such tool. Labels VERBATIM. If the human picks the \"Something else\" option, ask them for that one value in their own words and pass THAT in the flag. One question is NOT a default and must not be clicked past: the one naming the folder about to be connected. Read the path out and wait for a real answer — a folder bound to the wrong project has no symptom afterwards. Do not reword them, do not add or drop options, do not answer any of them yourself, and do not narrate the state instead of asking. Then run the command again with each answer in its named flag. Only a non-zero exit means stop.\n5. When it finishes, TELL YOUR HUMAN TO RESTART YOU. You cannot restart yourself, and Retasc's tools only load when your client starts, so setup is not finished until they do. A resumed session does not count — it keeps the tools it launched with.\nThen call setup_status, which will tell you what is left.",
  "tools": [
    {
      "description": "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.",
      "inputSchema": {
        "properties": {},
        "type": "object"
      },
      "name": "setup_status",
      "outputSchema": null
    }
  ]
}

Verify it yourself

curl -s https://api.teppi.xyz/v1/evidence/sha256:03ff0190972847f8c3c6806d39317509cd6c3d3ce78bcab50b051ea86253e3ae | sha256sum