MarketScope AI: Healthcare Product Analytics

Created By
BigDataTeam5a year ago
This is our final project , in this we have utlized langgraph coupled with various mcp server mounted of fastapi using fastmcp to create mutlifaceted application for healthcare vendor to make them understand more about their product performance and provide suggestions and strategies
Overview

What is MarketScope AI?

MarketScope AI is an intelligent analytics platform designed to help healthcare vendors analyze and understand their product performance across various market segments using advanced AI and natural language processing.

How to use MarketScope AI?

To use MarketScope AI, set up the application by following the installation instructions, then run the server and access the Streamlit frontend to start analyzing your healthcare data.

Key features of MarketScope AI?

  • Market Segmentation Analysis: Understand different healthcare market segments.
  • Strategic Query Optimization: Get optimized answers to strategic questions.
  • Product Comparison: Compare products across various segments.
  • Sales & Marketing Analysis: Upload sales data for AI-powered insights.

Use cases of MarketScope AI?

  1. Analyzing product performance in the diagnostic segment.
  2. Comparing OTC pharmaceutical products.
  3. Gaining insights from sales data for marketing strategies.

FAQ from MarketScope AI?

  • What are the prerequisites for using MarketScope AI?

You need Python 3.8 or higher and the required packages will be installed automatically during setup.

  • How do I analyze my sales data?

Select your segment, go to the Sales & Marketing Analysis page, upload your CSV file, and click "Analyze Data."

  • Is there support for troubleshooting?

Yes, the documentation includes troubleshooting tips for common issues.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
BigDataTeam5
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago