Motivation
I represent Helena Bioinformatics, publisher of Folklore Clinical Variant Interpretation MCP.
Biorouter already provides a ClinicalVariantAgent pattern for several public variant resources. We would like to contribute a complementary community extension that connects Biorouter to a hosted, read-only clinical variant evidence endpoint instead of reimplementing upstream APIs or scientific logic.
Proposed contribution
Would BAAM accept a .brxt extension whose bounded responsibility is to register this remote stateless Streamable HTTP endpoint?
https://api.helena.bio/folklore/v1/mcp
The proposed extension would:
- expose the four published read-only tools for variant evidence, variant-linked literature, publication details, and semantic biomedical literature search;
- preserve the server's explicit resolved, ambiguous, not-found, invalid, unsupported, and unavailable outcome states;
- accept public variant-level queries only;
- exclude patient, phenotype, family, segregation, and private case data;
- surface the machine-readable professional-review boundary;
- include a small public smoke fixture with no credentials or clinical records.
Results support qualified professional review. They are not a diagnosis or treatment recommendation.
If this fits BAAM's extension model, Helena Bioinformatics can prepare the narrow connector, manifest, installation notes, and public conformance fixture for maintainer review.
Alternatives considered
A documentation-only recipe would require every Biorouter user to configure the remote endpoint manually. Embedding direct calls to the underlying public APIs inside ClinicalVariantAgent would duplicate an existing MCP contract and make version and safety-boundary synchronization harder.
Public adapter and contract: https://github.com/helena-bioinformatics/folklore-mcp
Connector guide: https://folklore.helena.bio/docs/folklore-connector
Motivation
I represent Helena Bioinformatics, publisher of Folklore Clinical Variant Interpretation MCP.
Biorouter already provides a ClinicalVariantAgent pattern for several public variant resources. We would like to contribute a complementary community extension that connects Biorouter to a hosted, read-only clinical variant evidence endpoint instead of reimplementing upstream APIs or scientific logic.
Proposed contribution
Would BAAM accept a .brxt extension whose bounded responsibility is to register this remote stateless Streamable HTTP endpoint?
https://api.helena.bio/folklore/v1/mcp
The proposed extension would:
Results support qualified professional review. They are not a diagnosis or treatment recommendation.
If this fits BAAM's extension model, Helena Bioinformatics can prepare the narrow connector, manifest, installation notes, and public conformance fixture for maintainer review.
Alternatives considered
A documentation-only recipe would require every Biorouter user to configure the remote endpoint manually. Embedding direct calls to the underlying public APIs inside ClinicalVariantAgent would duplicate an existing MCP contract and make version and safety-boundary synchronization harder.
Public adapter and contract: https://github.com/helena-bioinformatics/folklore-mcp
Connector guide: https://folklore.helena.bio/docs/folklore-connector