protogrid

Search / io.github.pipeworx-io/fda-drug-competition

Fda Drug Competition

R0· no sign-in

Orange Book competitive intelligence from FDA's monthly official data ZIP.

v0.1.0 · active · repository · website · descriptor JSON · versions

An agent can connect right now, no human step.Remote endpoint, no authentication, reachable on the last probe.
Quality–not scored
Trust94of 100
Uptime, 30 days97%
Latency p5036 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "fda-drug-competition": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/fda-drug-competition/mcp"
    }
  }
}
claude mcp add --transport http fda-drug-competition https://gateway.pipeworx.io/fda-drug-competition/mcp
[mcp_servers.fda-drug-competition]
url = "https://gateway.pipeworx.io/fda-drug-competition/mcp"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fda-drug-competition": {
      "type": "remote",
      "url": "https://gateway.pipeworx.io/fda-drug-competition/mcp",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "fda-drug-competition": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/fda-drug-competition/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=fda-drug-competition&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vZ2F0ZXdheS5waXBld29yeC5pby9mZGEtZHJ1Zy1jb21wZXRpdGlvbi9tY3AifQ%3D%3D"
}
{
  "servers": {
    "fda-drug-competition": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/fda-drug-competition/mcp"
    }
  }
}
{
  "mcpServers": {
    "fda-drug-competition": {
      "httpUrl": "https://gateway.pipeworx.io/fda-drug-competition/mcp"
    }
  }
}
extensions:
  "fda-drug-competition":
    enabled: true
    name: "fda-drug-competition"
    type: streamable_http
    uri: "https://gateway.pipeworx.io/fda-drug-competition/mcp"
    timeout: 300

Quality – / 100not scored

Not scored: fewer than three checks apply, usually because no remote answered a credential-free probe or the server is a local package.

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2025-03-26; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygienen/a · weight 30
  • n/a
    tools.descriptions, tools.description_length, tools.schemas, tools.annotations, tools.directory_hints, tools.token_cost, tools.api_dumptool list unknown (behind auth, not probed, or empty)
stabilityn/a · weight 15
  • n/a
    stability.changes, stability.rug_pulltool list unknown
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

Tool list unknown · tools last changed 2026-10-13 · checked 2026-10-20 21:51 UTC

Tool changes

  • drug_patent_challenge_profileremoved

    How exposed is one brand drug's patent protection, in a single call. Joins the three sources a generics or biotech analyst otherwise queries by hand: FDA Orange Book listed patents and their expiry dates, USPTO PTAB proceedings (IPR/PGR) filed against those exact patent numbers, and federal ANDA / Hatch-Waxman district-court dockets naming the brand. Returns the earliest expiry NOT under challenge, which patents are actively contested, and which generic firms are litigating. Use for loss-of-exclusivity diligence, generic-entry timing, or "who is attacking this drug and where". Listed dates are FDA/USPTO/court records, not a legal conclusion about enforceability or actual launch.

  • resolution_auditremoved

    Extract the settlement clause of a single Polymarket or Kalshi market: who publishes the settling number (source), the clock time + timezone it is taken at, the precision of the computation (e.g. "1-minute candle close" vs "60-second trailing average" vs "election outcome"), the evidence standard (official_source | consensus_reporting | any_credible_report | unspecified), and void_handling (cancellation/postponement settlement — reused verbatim from bet_research's cancellation_rule detector, not re-derived). Parses Polymarket's `description` field (fetched via polymarket_market) or Kalshi's `rules_primary` + `rules_secondary` fields (fetched via kalshi_market) with regex + a small vocabulary — no LLM pass, so an unusual clause reports confidence:"low" rather than a guess. Pass `market` as a Polymarket slug/URL or a Kalshi market ticker (e.g. "KXBTCD-26SEP1317-T66999.99"); a Kalshi EVENT ticker (e.g. "KXBTCD-26SEP1317") also works — it picks one representative market under that event, since the settlement mechanism is normally shared across all strikes/legs in one event. Use this before treating a polymarket_kalshi_spread row as a real arbitrage: two ladders that look alike can settle on different sources, at different times, with different precision — this tool is how you check. Pair with resolution_diff to compare two markets directly. KNOWN GAP: idiosyncratic phrasing that doesn't match the vocabulary returns confidence:"low" and evidence_standard:"unspecified" rather than an LLM-guessed answer.

  • bet_researchremoved

    Research a Polymarket bet by pulling the relevant Pipeworx data for it in one call. Pass a market slug ("will-kristi-noem-win-the-2028-republican-presidential-nomination"), a polymarket.com URL, or a question text. Prefer an UNDATED slug: a dated one ("...-by-june-30-2026") stops resolving the day it settles, because Polymarket de-indexes resolved markets. The tool resolves the market, classifies the bet, fans out to category-specific data packs in parallel, and returns an evidence packet + simple market-vs-model comparison. Use for "should I bet on X", "what does the data say about Y", or "is there edge in Z". CLASSIFIERS: crypto_price, fed_rate, geopolitical, sports, sports_championship, drug_approval, election_candidate, tech_launch, space_launch, corporate, corporate_earnings, corporate_event, public_figure_speech, weather, other. FAN-OUT EXAMPLES: BTC bet → coingecko + fred + gdelt+gnews; Fed bet → fred (DFEDTARU + EFFR + CPIAUCSL) + kalshi_macro (KXFED implied probs) + recent_fed_actions (federal-register rules, last 365d); Hormuz bet → imf_portwatch + airspace + gdelt; Yankees WS → mlb_stats_standings + parent_event partition + news; hottest-year bet → climate_projection_nyc + gistemp_latest (NASA global anomaly, rank since 1880) + news; NVDA-vs-AAPL → finnhub get_quote + edgar shares-outstanding (derived market cap) + edgar filings + news. RESPONSE SHAPES: result.market carries best_bid/best_ask/spread_pp/liquidity/price_change_1h/1d/1w; result.analysis carries model_probability/edge_pp/kelly_fraction_half when a closed-form model fires PLUS a 24h-move warning ("Market moved X.Xpp in 24h, comparable to model edge — your edge may already be priced in") when relevant; result.evidence is keyed by source. RESOLVER CONTRACT: result.market_match_confidence ∈ {high, medium, low, none}, market_match_score (0-1 token-overlap), market_match_alternatives[] (other candidate markets the resolver considered), and suggestions[] (explicit re-query hints when the match is fuzzy) — ALWAYS inspect these before trusting the analysis block, because medium/low matches can still surface other fields. PARENT_EVENT EXTRACTOR: when the bet is one leg of a partition (Yankees WS, Romania election), result.parent_event{matched_candidate, top_legs_by_price[], partition_size, placeholders_filtered} gives you the peer prices in one place — that's the headline for elections/championships. NEWS FIELDS: news entries carry _fallback_attempted / _fallback_failed_reason / retry_after_sec when GDELT 429s and GNews backfill ran or failed. SAFETY: low-confidence resolutions short-circuit with status:"low_confidence_match" and suppress analysis fields so agents can't accidentally size on phantom matches. Closed/dead markets that ARE still indexed by Polymarket (yes_price≈0, no volume, no liquidity) return status:"market_closed_or_inactive" and skip fan-out. A market whose own deadline has already passed returns status:"market_expired_or_resolved" + expired_deadline (the date), which is deliberately NOT the same answer as low_confidence_match: your slug was right and is merely settled, so the useful retry is the successor market for the same question, not a corrected spelling. In practice resolved markets are usually de-indexed and instead surface via one of those two paths — both routes are BLOCKING, just different mechanisms. Wide-spread markets (>10pp) carry tradeability:"illiquid_wide_spread" + an explanatory note. RESOLUTION-RULE RISK: market.cancellation_rule parses the void/postponement settlement out of the resolution text — refund_50_50 (shares settle flat 50¢ on void; EV-material for any entry away from 50¢, with ev_impact quantified), resolves_no_on_cancel, resolves_yes_on_cancel, carries_to_reschedule, or mentioned_unclear. null means the description never mentions cancellation. Check this before sizing sports/esports/event-occurrence bets — audited arb-bot ledgers show flat-50¢ void settlements are a recurring pure-rules loss.

  • search_withinremoved

    Semantic search INSIDE a fetched record. Pass the text you already pulled (e.g. a SEC 10-K body, an article, a long tool result) plus a natural-language query; get back the top-N passages with character offsets and similarity scores. Use when the record is too big to cram into the prompt — search_within saves context, returns only the passages that matter, and every passage carries an offset so the agent can verify a verbatim quote. Pairs with ask_pipeworx_grounded: fetch with the gateway, ground over the relevant passages instead of the whole document. BGE-base-en embeddings + cosine over 500-char overlapping windows; cap is 200K chars (longer inputs are truncated and flagged).

  • purple_book_biosimilar_entry_timelineremoved

    Chronologically summarize unique FDA-licensed 351(k) BLAs associated with a reference biologic. Returns approval dates, applicants, product names, reference products, and biosimilar versus interchangeable designations for entry analysis.

  • purple_book_recent_changesremoved

    Return the changes section of FDA’s latest monthly Purple Book report: N=newly approved, R=added in current release, U=updated. Updated or added does not necessarily mean newly licensed.

  • purple_book_reference_productremoved

    Find a reference biologic and its FDA-licensed 351(k) products by proper or proprietary name. Product rows and BLA counts must not be interpreted as market participants, launches, or market share.

  • purple_book_interchangeablesremoved

    List FDA Purple Book products designated 351(k) Interchangeable, optionally filtered by reference product, applicant, or product name. Interchangeability is an FDA designation; pharmacy substitution remains subject to applicable law and circumstances.

  • purple_book_biosimilarsremoved

    List FDA-licensed 351(k) biosimilar and interchangeable products for an optional reference product, applicant, or product name. Approval/licensure does not establish commercial launch or current availability.

  • purple_book_competition_profileremoved

    Profile FDA-licensed biologic competition around a proper, proprietary, or reference-product name. Counts unique BLAs as sponsors/applications and separates reference products, biosimilars, and interchangeables. It does not measure launches, availability, sales, or market share.

Showing the latest 10. Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 94 / 100

provenance90
liveness99
freshness85
hygiene100

+repository +namespace-matches-repo +website +reachable +uptime-97% ~updated-85d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://gateway.pipeworx.io/fda-drug-competition/mcp streamable-httpnoneyes97%36 ms2025-03-262026-10-20

Tools (0)

No tools observed. Tools appear once a credential-free probe can list them.

Schemas: list_tools.

Similar MCP servers

More from io.github.pipeworx-io

And 1,855 more from this publisher.

Official server.json
{
  "name": "io.github.pipeworx-io/fda-drug-competition",
  "title": "Fda Drug Competition",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://gateway.pipeworx.io/fda-drug-competition/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "0.1.0",
  "repository": {
    "url": "https://github.com/pipeworx-io/mcp-fda-drug-competition",
    "source": "github"
  },
  "websiteUrl": "https://pipeworx.io/packs/fda-drug-competition",
  "description": "Orange Book competitive intelligence from FDA's monthly official data ZIP."
}