Puxitatug Biologics Sequence Review Report 2026: VTCN1 Similarity and Patent-Risk Signals
This Puxitatug Biologics Sequence Review Report was produced with PatSnap Biology Modality MCP workflows. It connects patent-scale similarity search, sequence retrieval, pairwise alignment and antibody–antigen evidence in a reproducible screen. Explore the PatSnap MCP servers used in this report.
Review date: 23 July 2026. This report supports R&D and IP triage; it is not a legal opinion, freedom-to-operate conclusion or validity analysis. A sequence hit does not establish infringement. “Claimed” is a database annotation that still requires family consolidation, live-claim review and jurisdiction-specific claim construction.
Executive sequence-risk thesis
Puxitatug is an antibody directed to VTCN1. Public therapeutic sequence data from Thera-SAbDab PL132, Oxford Protein Informatics Group supplied the query material: VH 117 aa, VL 107 aa. No record met the configured 70–100% identity and 80–100% query-coverage window in this screening run. This is a bounded no-hit result, not evidence of patent clearance or sequence uniqueness.
The screening conclusion is continued evidence-development priority, not “blocked” or “clear.” Similarity is most informative when interpreted by chain, CDR/framework location, construct architecture, target evidence and the language of live claims. Constant-region reuse or a common light chain can produce high percentages without proving asset-level collision, while a small number of substitutions in a CDR or linker junction can be disproportionately important.
Sequence scope and MCP workflow
The review began with traceable Thera-SAbDab PL132, Oxford Protein Informatics Group query sequences. Each available VH, VL and secondary arm was submitted with ls_sequence_search_submit against ALLPATENT protein records, using gaps, E-value ≤1×10−5, identity 70–100%, query coverage 80–100% and a 500-record task cap. Results were retrieved with ls_sequence_search_get_results; the closest informative hit was resolved with ls_sequence_fetch and compared using ls_sequence_alignment. ls_patent_sequence_fetch and ls_antibody_antigen_search supplied patent and target context.
Similarity search readout
| Query | Search volume | Leading evidence |
|---|---|---|
| VH (117 aa) | 0 returned records | No qualifying hit in the configured window |
| VL (107 aa) | 0 returned records | No qualifying hit in the configured window |
The largest chain-level result set contained 0 records. These are search records, not unique inventions, enforceable claims or independent families. Publications can repeat the same sequence across jurisdictions, examples, comparators and continuations. Deduplication by earliest priority, applicant, simple family and legal status is required before business conclusions.
Module-level reading of the construct
The available query set contains 2 independently searchable chain module(s). For this single-pair format, heavy- and light-variable evidence should still be interpreted together. A highly conserved light chain can be shared across unrelated heavy chains, while a heavy-chain match may include common framework and constant-region sequence outside the specificity-defining CDRs.
The chain totals also provide a practical specificity check. A chain that repeatedly reaches the task cap is less discriminating at the raw-sequence level than a chain with a smaller, concentrated result set. Reviewers should therefore prioritize the rarest domain or junction, then use the more widely reused chain as corroboration. This ordering reduces the risk of treating platform-level or germline similarity as evidence of an asset-level collision.
Pairwise alignment: what the closest hit means
Because no sequence passed the configured screen, no subject sequence was promoted to pairwise alignment. A follow-up review should test CDR-only, junction, nucleotide and lower-threshold queries while preserving the stricter run as the primary screening record.
Percentage identity alone is not a claim chart. The next review should map every mismatch to IMGT/Kabat position, CDR or framework, constant region, linker boundary and any claimed SEQ ID. For multispecific assets, each arm should also be searched independently because a full-construct query can obscure highly conserved binding modules.
Antibody–antigen and patent-sequence evidence
The exact asset-name filter did not return a direct antibody–antigen relation. Because naming and alias coverage varies across patent records, the result should be supplemented with target-level and development-code searches; it must not be read as negative biological or patent evidence.
No directly named patent sequence set was resolved from the first antibody–antigen record. That absence is an evidence-coverage limitation, not evidence of patent clearance; family and alias searches remain necessary.
Evidence strength and blind spots
The evidence is strongest for the exact query sequences, the returned alignment coordinates and the patent records directly resolved by the MCP tools. It is weaker where therapeutic aliases are absent, where a publication supplies fragments instead of the administered construct, or where the result set is capped before all lower-ranked families are reviewed. Antibody names can also refer to a parental molecule, biosimilar, anti-drug antibody or comparator; the underlying sequence and target annotation must be read before attributing a record to Puxitatug.
Patent sequence listings are deliberately broad and can contain screening libraries, consensus sequences, controls, antigens, primers and manufacturing elements alongside candidate therapeutics. Conversely, relevant claims may define a molecule through CDR combinations, percentage-identity thresholds, functional binding language or genus formulas without reproducing the exact commercial sequence. This is why the report combines sequence similarity with antibody–antigen evidence and still stops short of a legal conclusion.
Patent-risk interpretation
| Dimension | Screening signal | Required next check |
|---|---|---|
| Sequence proximity | No qualifying hit in the configured window | Broaden to CDR, junction, nucleotide and lower-threshold searches. |
| Claim annotation | Not specified | Read live independent and dependent claims in relevant jurisdictions. |
| Target evidence | No exact-name hit | Search aliases, development codes and each target separately. |
| Legal conclusion | Not determined | Assess priority, ownership, licensing, prosecution, validity and territorial status with counsel. |
Diligence actions
- Confirm that the reviewed sequence matches the clinical or commercial construct rather than an early lead or analytical reference.
- Repeat searches for CDR-only queries, junctions and nucleotide sequences, then cluster records by patent family.
- Annotate each high-identity hit by VH/VL domain, CDR, framework, Fc and linker position.
- Retrieve the underlying sequence listing and verify the returned sequence number and “claimed” annotation against the filed document.
- Build jurisdiction-specific claim charts for live families and document licenses or platform rights affecting VTCN1 programs.
- Rerun the MCP workflow at the transaction or development decision date because sequence and legal-status coverage changes.
Bottom line
Puxitatug has a traceable therapeutic sequence. The absence of a qualifying hit in the strict window, together with an exact-name evidence gap and 0 directly fetched patent sequences, supports continued evidence-development priority rather than a clearance conclusion. The defensible outcome is a prioritized, domain-aware family and claim review—not a binary clearance statement.
Sources and methodology notes
Query sequences: Thera-SAbDab PL132, Oxford Protein Informatics Group. Core similarity, sequence, alignment, patent-sequence and antibody–antigen evidence was retrieved through PatSnap Biology Modality MCP on 23 July 2026. Database annotations and legal status can change; rerun at the decision date.
