OGA Antibody Validation

io.github.onlygoodantibodiesPublished by GitHub account onlygoodantibodiesv1.0.0Updated Oct 24, 2026

Knockout-controlled antibody validation lookups over the Only Good Antibodies dataset

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant look up knockout-controlled antibody validation data from the Only Good Antibodies dataset.

What you can do
  • Look up antibody validation records from the Only Good Antibodies dataset.
  • Retrieve knockout-controlled validation evidence for specific antibodies.
  • No tool list is published, so the exact lookup and search operations are not documented in the supplied material.
When to use it
Useful when you need to check whether an antibody has knockout-controlled validation evidence, for example while planning experiments or choosing reagents.
Requirements
A remote streamable HTTP endpoint at oga-mcp.onrender.com; no local package or runtime is needed. OAuth authentication is required, so an account with the provider is needed. Network access to the endpoint is required.
Before you install
Access requires OAuth sign-in, so the provider will see your account identity and the queries you make. The tool list is not published, so confirm what the server can read or change before relying on it. Validation data is a research aid and should not replace your own verification.

Installation

In SourceWeft

  1. Open OGA Antibody Validation 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.github.onlygoodantibodies%2Foga-antibodies/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": {
    "oga-antibody-validation": {
      "type": "http",
      "url": "https://oga-mcp.onrender.com/readonly/mcp"
    }
  }
}

README

This repository has no README.

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 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.