ProteinIQ

io.proteiniqPublished by proteiniq.ioOfficial publisherv1.0.0Updated Oct 24, 2026

Run protein folding, docking, design and sequence analysis tools, and read their results.

VerifiedStreamable HTTPWeb executableAI & ML

Overview

AI-generated overview

Remote MCP server that lets an assistant run protein folding, docking, design and sequence analysis jobs and read their results.

What you can do
  • Run protein folding computations
  • Run molecular docking jobs
  • Run protein design workflows
  • Run sequence analysis
  • Read back the results of submitted jobs
When to use it
Useful when you want an assistant to launch and inspect computational structural-biology work — folding, docking, design or sequence analysis — without leaving the chat, and you are comfortable sending work to a hosted service.
Requirements
A remote endpoint at proteiniq.io over streamable HTTP; OAuth authentication is required. No environment variables or headers are declared.
Before you install
Access requires OAuth sign-in to a third-party hosted service, so your inputs and results are processed on that provider's infrastructure. Jobs may consume paid compute or account quota; check the provider's terms before submitting work. The manifest lists no tools, so confirm the exact operations and their side effects after connecting.

Installation

In SourceWeft

  1. Open ProteinIQ in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.proteiniq%2Fproteiniq/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "proteiniq": {
      "type": "http",
      "url": "https://proteiniq.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 30, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.