Update to Tamarind Bio
Snapshot Oct 27, 2026 · 00:11 UTC · version 2.0.1
Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.
Instructions updated for tamarind-mcp-setup
Skill instructions — Now says: If OAuth never starts - the client's connect or authenticate control does nothing, or the tools stay missing after installing this plugin from its git...
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 3 plugins free · no card required.
All fields and original values.
Skill instructions
Sep 30, 2026 · 22:50 UTC
No removed lines (ordering may have changed)
Oct 27, 2026 · 00:11 UTC
If OAuth never starts - the client's connect or authenticate control does nothing, or the tools stay missing after installing this plugin from its git marketplace rather than the published listing - the server has to be added by hand ins...
Supporting files
Sep 30, 2026 · 22:50 UTC
[]
Oct 27, 2026 · 00:11 UTC
[{"relative_path":"agents/openai.yaml","size_in_bytes":418}]
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -24,9 +24,12 @@ After OAuth completes, repeat the no-spend checks. There is no separate MCP `auth status` tool; a successful account-scoped catalog call is the connectivity signal. +If OAuth never starts - the client's connect or authenticate control does nothing, or the tools stay missing after installing this plugin from its git marketplace rather than the published listing - the server has to be added by hand instead. Send the user to <https://app.tamarind.bio/api-docs/mcp-server> for their client's exact steps, and do not attempt the setup on their behalf or accept a key in chat. + ## Diagnose failures - Missing tools: install or enable the `tamarind-mcp` plugin/server, then start a new task if the client requires tool discovery at task creation. +- Missing tools after a git-marketplace install, or a connect control that does nothing: the server needs to be added manually - point the user at <https://app.tamarind.bio/api-docs/mcp-server> rather than retrying the control. - Unauthorized: reconnect through the client and complete OAuth once; do not loop authentication attempts. - Tool not found: query the live catalog instead of assuming a remembered tool name. - File upload egress blocked: use `uploadFile` inline for files up to its inline limit, or allow the exact host returned by `uploadFile` before retrying the streaming upload.
Full technical diff · 2 changed fields
changed /included_files
[]
[
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 418
}
]changed /skill_md_contents
"---\nname: tamarind-mcp-setup\ndescription: Connect, authenticate, or troubleshoot the Tamarind Bio MCP server and run a no-spend connectivity check. Use when Tamarind MCP tools are missing, OAuth is incomplete or rejected, or the user wants MCP rather than the Tamarind CLI. Not for selecting a scientific model or submitting compute.\n---\n\n# Connect Tamarind MCP\n\nUse the remote MCP server configured by this plugin. Do not install the Tamarind CLI, request an API key, or recreate Tamarind HTTP calls.\n\n## Check availability\n\nConfirm that these server tools are callable:\n\n1. Call `listModalities`.\n2. Call `listTags`.\n3. Call `getAvailableTools` with a narrow `search` such as `boltz`.\n4. Call `getJobSchema` for one returned tool.\n\nThese calls do not create jobs or consume compute. Do not call `submitJob` or `submitBatch` as a setup test.\n\n## Authenticate\n\nIf a tool reports unauthorized or the client shows that Tamarind is disconnected, use the MCP client's connection UI to reconnect `https://mcp.tamarind.bio/mcp` and complete OAuth. Never ask the user to paste a client secret, access token, refresh token, authorization code, or API key into chat.\n\nAfter OAuth completes, repeat the no-spend checks. There is no separate MCP `auth status` tool; a successful account-scoped catalog call is the connectivity signal.\n\n## Diagnose failures\n\n- Missing tools: install or enable the `tamarind-mcp` plugin/server, then start a new task if the client requires tool discovery at task creation.\n- Unauthorized: reconnect through the client and complete OAuth once; do not loop authentication attempts.\n- Tool not found: query the live catalog instead of assuming a remembered tool name.\n- File upload egress blocked: use `uploadFile` inline for files up to its inline limit, or allow the exact host returned by `uploadFile` before retrying the streaming upload.\n- Rate limit or service error: stop and report it. Never turn a connectivity failure into a compute submission.\n\nAfter setup succeeds, route selection to `tamarind-mcp-tool-discovery` and a known single job to `tamarind-mcp-submit-and-poll`.\n"
"---\nname: tamarind-mcp-setup\ndescription: Connect, authenticate, or troubleshoot the Tamarind Bio MCP server and run a no-spend connectivity check. Use when Tamarind MCP tools are missing, OAuth is incomplete or rejected, or the user wants MCP rather than the Tamarind CLI. Not for selecting a scientific model or submitting compute.\n---\n\n# Connect Tamarind MCP\n\nUse the remote MCP server configured by this plugin. Do not install the Tamarind CLI, request an API key, or recreate Tamarind HTTP calls.\n\n## Check availability\n\nConfirm that these server tools are callable:\n\n1. Call `listModalities`.\n2. Call `listTags`.\n3. Call `getAvailableTools` with a narrow `search` such as `boltz`.\n4. Call `getJobSchema` for one returned tool.\n\nThese calls do not create jobs or consume compute. Do not call `submitJob` or `submitBatch` as a setup test.\n\n## Authenticate\n\nIf a tool reports unauthorized or the client shows that Tamarind is disconnected, use the MCP client's connection UI to reconnect `https://mcp.tamarind.bio/mcp` and complete OAuth. Never ask the user to paste a client secret, access token, refresh token, authorization code, or API key into chat.\n\nAfter OAuth completes, repeat the no-spend checks. There is no separate MCP `auth status` tool; a successful account-scoped catalog call is the connectivity signal.\n\nIf OAuth never starts - the client's connect or authenticate control does nothing, or the tools stay missing after installing this plugin from its git marketplace rather than the published listing - the server has to be added by hand instead. Send the user to <https://app.tamarind.bio/api-docs/mcp-server> for their client's exact steps, and do not attempt the setup on their behalf or accept a key in chat.\n\n## Diagnose failures\n\n- Missing tools: install or enable the `tamarind-mcp` plugin/server, then start a new task if the client requires tool discovery at task creation.\n- Missing tools after a git-marketplace install, or a connect control that does nothing: the server needs to be added manually - point the user at <https://app.tamarind.bio/api-docs/mcp-server> rather than retrying the control.\n- Unauthorized: reconnect through the client and complete OAuth once; do not loop authentication attempts.\n- Tool not found: query the live catalog instead of assuming a remembered tool name.\n- File upload egress blocked: use `uploadFile` inline for files up to its inline limit, or allow the exact host returned by `uploadFile` before retrying the streaming upload.\n- Rate limit or service error: stop and report it. Never turn a connectivity failure into a compute submission.\n\nAfter setup succeeds, route selection to `tamarind-mcp-tool-discovery` and a known single job to `tamarind-mcp-submit-and-poll`.\n"
Full snapshot data
{
"description": "Connect, authenticate, or troubleshoot the Tamarind Bio MCP server and run a no-spend connectivity check. Use when Tamarind MCP tools are missing, OAuth is incomplete or rejected, or the user wants MCP rather than the Tamarind CLI. Not for selecting a scientific model or submitting compute.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 418
}
],
"name": "tamarind-mcp-setup",
"skill_md_contents": "---\nname: tamarind-mcp-setup\ndescription: Connect, authenticate, or troubleshoot the Tamarind Bio MCP server and run a no-spend connectivity check. Use when Tamarind MCP tools are missing, OAuth is incomplete or rejected, or the user wants MCP rather than the Tamarind CLI. Not for selecting a scientific model or submitting compute.\n---\n\n# Connect Tamarind MCP\n\nUse the remote MCP server configured by this plugin. Do not install the Tamarind CLI, request an API key, or recreate Tamarind HTTP calls.\n\n## Check availability\n\nConfirm that these server tools are callable:\n\n1. Call `listModalities`.\n2. Call `listTags`.\n3. Call `getAvailableTools` with a narrow `search` such as `boltz`.\n4. Call `getJobSchema` for one returned tool.\n\nThese calls do not create jobs or consume compute. Do not call `submitJob` or `submitBatch` as a setup test.\n\n## Authenticate\n\nIf a tool reports unauthorized or the client shows that Tamarind is disconnected, use the MCP client's connection UI to reconnect `https://mcp.tamarind.bio/mcp` and complete OAuth. Never ask the user to paste a client secret, access token, refresh token, authorization code, or API key into chat.\n\nAfter OAuth completes, repeat the no-spend checks. There is no separate MCP `auth status` tool; a successful account-scoped catalog call is the connectivity signal.\n\nIf OAuth never starts - the client's connect or authenticate control does nothing, or the tools stay missing after installing this plugin from its git marketplace rather than the published listing - the server has to be added by hand instead. Send the user to <https://app.tamarind.bio/api-docs/mcp-server> for their client's exact steps, and do not attempt the setup on their behalf or accept a key in chat.\n\n## Diagnose failures\n\n- Missing tools: install or enable the `tamarind-mcp` plugin/server, then start a new task if the client requires tool discovery at task creation.\n- Missing tools after a git-marketplace install, or a connect control that does nothing: the server needs to be added manually - point the user at <https://app.tamarind.bio/api-docs/mcp-server> rather than retrying the control.\n- Unauthorized: reconnect through the client and complete OAuth once; do not loop authentication attempts.\n- Tool not found: query the live catalog instead of assuming a remembered tool name.\n- File upload egress blocked: use `uploadFile` inline for files up to its inline limit, or allow the exact host returned by `uploadFile` before retrying the streaming upload.\n- Rate limit or service error: stop and report it. Never turn a connectivity failure into a compute submission.\n\nAfter setup succeeds, route selection to `tamarind-mcp-tool-discovery` and a known single job to `tamarind-mcp-submit-and-poll`.\n"
}SHA-256 of public snapshot: e291fd577164a3c705611e778454145dac49687c967d27620e4b289e80dc6a93