Bring Lims
to VS Code Copilot
Create your Vinkius account to connect Scispot to VS Code Copilot and start using all 12 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.
Compatible with every major AI agent and IDE
What is the Scispot MCP Server?
Connect your Scispot API-first Cannabis Testing Laboratory LIMS to any AI agent and take full control of your laboratory operations, quality assurance workflows, and regulatory compliance through natural conversation.
What you can do
- Sample Management — Track all cannabis samples received with chain of custody, testing priority, and real-time status updates
- Test Panels — Browse available analytical methods including potency, terpenes, pesticides, heavy metals, mycotoxins, and microbials
- Analytical Results — Access complete test findings with pass/fail determinations against state-specific regulatory limits
- Certificates of Analysis — Retrieve all issued CoAs with QR codes for consumer verification and automatic Metrc submission
- Batch Traceability — Monitor production batches through laboratory testing with full seed-to-sale linkage
- Plate Management — Oversee high-throughput batch processing with 96-well and 384-well plate tracking
- Analytical Runs — Review instrument run data including QC metrics, system suitability, and analyst assignments
- Order Tracking — Monitor client testing orders from submission through invoicing with ETA predictions
- Instrument Health — Verify calibration status, maintenance schedules, and operational readiness for HPLC, GC-MS, ICP-MS systems
- Workflow Automation — Track standardized laboratory processes from sample intake to CoA approval with bottleneck identification
- Client Directory — Access complete client profiles including license types, testing history, and custom panel configurations
- Audit Trails — Retrieve comprehensive operation logs for FDA 21 CFR Part 11 compliance and ISO/IEC 17025 inspection readiness
How it works
- Subscribe to this server
- Enter your Scispot API key (generated from Account Settings)
- Start managing your cannabis laboratory from Claude, Cursor, or any MCP-compatible client
No more navigating complex LIMS dashboards or manually reconciling sample queues. Your AI acts as a dedicated laboratory information systems analyst.
Who is this for?
- Laboratory Directors — verify instrument calibration, review pending CoAs, monitor throughput metrics, and ensure ISO/IEC 17025 compliance without logging into Scispot
- Quality Managers — audit test results, investigate deviations, track non-conformance workflows, and prepare inspection documentation through conversational queries
- Analytical Chemists — check sample queues, verify test panel configurations, access run histories, and review QC metrics directly from the bench
- Client Relations — provide cultivators and processors with real-time sample status updates, CoA delivery confirmations, and order progress reports
Built-in capabilities (12)
Each audit log entry contains the precise timestamp (ISO 8601), performing user name and ID, action type (sample created, result modified, CoA issued, workflow step completed, user permission changed, instrument calibration recorded), affected record ID and type, previous and new values for any modifications, IP address and user agent, and justification comment (if required for critical changes). Fundamental for regulatory inspections, data integrity investigations, deviation root cause analysis, FDA 21 CFR Part 11 compliance, and ISO/IEC 17025 quality system requirements. AI agents use this to reconstruct event sequences during quality investigations, identify unauthorized or suspicious changes, monitor user activity patterns, generate audit-ready documentation packages, and demonstrate data integrity to regulatory inspectors. List all audit trail entries for laboratory operations and data modifications
Each batch entry contains the batch ID, producing facility license number, batch size and unit of measure, cannabis product type, harvest or manufacture date, linked samples submitted for testing, batch testing status (pending, partial, complete, failed), final disposition (released, quarantined, rejected, destroyed, reworked), and seed-to-sale tracking identifiers (Metrc UID, state compliance tags). Essential for batch-level compliance monitoring, recall management, regulatory reporting, and inventory reconciliation. AI agents reference this when tracing contamination issues, verifying batch clearance for distribution, generating lot-based compliance reports, or investigating quality deviations. List all cannabis production batches tracked through laboratory testing
Each CoA record includes the certificate number, linked sample and batch, issuing laboratory name and accreditation number, comprehensive analytical results (potency profile with THC/CBD percentages, terpene fingerprint with individual concentrations, contaminant screening results for pesticides, heavy metals, mycotoxins, and microbials), regulatory compliance statement, authorized signatory name and signature, issuance date, expiration date, and QR code for consumer verification. Critical for product release decisions, regulatory audit documentation, consumer transparency programs, and integration with state traceability systems (Metrc) and retail platforms (WeedMaps). AI agents use this to verify CoA authenticity, confirm batch compliance status, generate client-facing documentation packages, and ensure automatic regulatory submissions. List all Certificates of Analysis (CoA) issued by the laboratory
Each client record contains company name, license number and type (cultivation facility, processing plant, dispensary, distributor, third-party tester), primary contact information, account status (active, suspended, pending), billing terms, sample volume history, preferred communication methods, and any special testing requirements or custom panels configured. Essential for laboratory client relationship management, sample intake workflows, account-based reporting, and regulatory compliance documentation. AI agents should reference this when identifying sample ownership, generating client-specific reports, verifying active testing contracts, communicating results, and analyzing client testing patterns. List all clients (cultivators, processors, retailers) using laboratory services
Each instrument record contains the instrument name (HPLC system, GC-MS, ICP-MS, qPCR thermocycler, spectrophotometer), manufacturer, model number, serial number, installation location, calibration status, last calibration date, next scheduled maintenance, qualification status (IQ/OQ/PQ completion), associated test methods, and current operational status (active, under maintenance, offline, decommissioned). Critical for instrument qualification management, preventive maintenance scheduling, analytical data integrity verification, and regulatory inspection readiness. AI agents should reference this to verify instrument readiness before assigning tests, schedule calibration activities, troubleshoot analytical failures, and generate equipment utilization reports. List all laboratory instruments with calibration and maintenance status
Each order record contains the order ID, requesting client company, order date, requested test panels, number of samples included, priority level (standard, rush, priority), order status (pending, in-progress, completed, invoiced), assigned laboratory team, estimated completion date, and billing information. Critical for order management, client communication, laboratory capacity planning, and revenue tracking. AI agents use this to monitor order progress, identify bottlenecks, prioritize workflow assignments, communicate status updates to clients, and generate order fulfillment reports. List all testing orders and service requests from clients
Each plate entry contains the plate ID, plate format (96-well, 384-well), assay type assigned, number of samples loaded, number of standards and controls, run date, associated instrument, and processing status (prepared, in-run, completed, failed). Critical for managing high-volume testing operations, optimizing throughput, tracking reagent usage, and ensuring data integrity for multi-sample analytical runs. AI agents use this to monitor plate preparation status, identify incomplete runs, optimize well assignments, and troubleshoot analytical failures at the plate level. List all laboratory plates used for batch sample processing
Each result contains the result ID, linked sample and batch, test panel performed, comprehensive analytical findings (THC/CBD potency percentages, full terpene profiles, pesticide residue levels, heavy metal concentrations, mycotoxin detection, microbial counts), pass/fail determination against regulatory limits, analyst who performed the test, reviewer approval status, and date of completion. Fundamental for quality assurance workflows, client notification processes, regulatory data submissions, and product release decisions. AI agents should query this to verify sample compliance before releasing Certificates of Analysis, advising clients on product disposition, or preparing regulatory reports. List all laboratory test results with complete analytical data
Each run entry contains the run ID, instrument name and type (HPLC, GC-MS, ICP-MS, spectrophotometer), method or assay performed, start and end timestamps, operating analyst or technician, number of samples processed, quality control results (standard recoveries, blank checks, duplicate precision), system suitability status, and overall run disposition (accepted, rejected, requires review). Essential for instrument utilization tracking, method performance monitoring, analyst productivity assessment, and regulatory audit preparation. AI agents should query this to verify run completion status, identify failed runs requiring reanalysis, schedule instrument maintenance, and generate throughput reports. List all analytical runs executed on laboratory instruments
Each sample contains the unique sample ID, submitting client or cultivator, sample type (flower, edible, concentrate, topical, cartridge), received date, testing priority level, sample condition upon receipt, chain of custody documentation, and current testing status (received, in-progress, completed, failed, on-hold). Critical for laboratory workflow management, sample intake tracking, turnaround time monitoring, and seed-to-sale traceability compliance. AI agents use this to manage sample queues, predict completion dates, prioritize rush orders, and notify clients about status changes. List all cannabis samples submitted for laboratory testing
Each test entry includes the test name (potency, terpenes, pesticides, heavy metals, mycotoxins, microbials, residual solvents, water activity, moisture content, homogeneity), test methodology (HPLC, GC-MS, ICP-MS, ELISA, qPCR, LC-MS/MS), accreditation status, standard turnaround time, pricing tier, and regulatory limits per jurisdiction. Essential for test panel configuration, method validation, ISO/IEC 17025 compliance, and state-specific cannabis testing requirements. AI agents reference this when configuring sample test orders, explaining testing scopes to clients, verifying analytical method accreditation, and ensuring compliance with regulatory testing mandates. List all analytical test panels and methods available in the laboratory
Each workflow entry contains the workflow name (sample intake and login, potency testing, contaminant screening, CoA review and approval, sample disposal, non-conformance investigation), step definitions with sequential order, assigned roles and responsibilities at each step, quality control checkpoints and decision gates, average completion time, current instances in progress, and bottleneck indicators. Essential for laboratory operations management, staff task assignment, process optimization, and ISO/IEC 17025 quality management system compliance. AI agents use this to guide technicians through standardized testing procedures, identify workflow bottlenecks causing delays, ensure quality checkpoints are not bypassed, and generate process efficiency reports. List all laboratory workflow templates and active processes
Why VS Code Copilot?
GitHub Copilot Agent mode brings Scispot data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Scispot in VS Code Copilot
Why run Scispot with Vinkius?
The Scispot connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 12 tools are ready to work instantly without any complex setup.
You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.

* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure
Over 4,000 integrations ready for AI agents
Explore a vast library of pre-built integrations, optimized and ready to deploy.
Connect securely in under 30 seconds
Generate tokens to authenticate and link external services in a single step.
Complete visibility into every agent action
Audit live requests, latency, success rates, and active security compliance policies.
Optimize spending and track token ROI
Analyze real-time token consumption and cost metrics detailed by connection.




Explore our live AI Agents Analytics dashboard to see it all working
This dashboard is included when you connect Scispot using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.
Scispot and 4,000+ other AI tools. No hosting, no code, ready to use.
Professionals who connect Scispot to VS Code Copilot through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.
Raw MCP | Vinkius | |
|---|---|---|
| Ready-to-use MCPs | Find and configure each manually | 4,000+ MCPs ready to use |
| Connection Setup | Manual coding & server setup | 1-click instant connection |
| Server Hosting | You host it yourself (needs 24/7 uptime) | 100% hosted & managed by Vinkius |
| Security & Privacy | Stored in plaintext config files | Bank-grade encrypted vault |
| Activity Visibility | Blind execution (no logs or tracking) | Live dashboard with real-time logs |
| Cost Control | Runaway AI token spend risk | Automatic budget limits |
| Revoking Access | Must delete files or code to stop | 1-click disconnect button |
How Vinkius secures
Scispot for VS Code Copilot
Every request between VS Code Copilot and Scispot is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.
Frequently asked questions
Can my AI automatically verify if a cannabis sample has passed all required tests and is ready for Certificate of Analysis issuance?
Yes! Use the list_results tool to fetch all completed analytical findings for a specific sample. Your AI agent will respond with comprehensive pass/fail determinations across potency, terpenes, pesticides, heavy metals, mycotoxins, and microbial panels. Once all state-mandated tests show passing results, use list_certificates to verify CoA generation status and confirm automatic Metrc submission. Always verify regulatory limit compliance before releasing products to distribution or retail channels.
How do I quickly identify which laboratory instruments are approaching calibration expiry or require preventive maintenance?
Simply ask the agent to run the list_instruments action. It will compile all analytical equipment tracked via Scispot GLUE integration with calibration status, last service date, next scheduled maintenance, IQ/OQ/PQ qualification records, and current operational state. The AI will proactively highlight any HPLC, GC-MS, ICP-MS, or other systems approaching calibration expiry or overdue for preventive maintenance. This ensures your laboratory maintains ISO/IEC 17025 compliance, analytical data integrity, and inspection readiness at all times.
Does the Scispot integration allow modifying test results, deleting samples, or revoking issued Certificates of Analysis?
No. The current toolset focuses strictly on read-only querying and analytical operations — listing samples, reviewing results, checking certificates, monitoring workflows, and tracking instrument health. State alteration operations (modifying test data, deleting samples, revoking certificates, or changing approvals) are not currently exposed. This design assures your laboratory records remain secure against destructive queries, maintains complete audit trail integrity for regulatory inspections, and preserves data immutability required by FDA 21 CFR Part 11 and ISO/IEC 17025 standards.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
Figshare
20 toolsManage research data and scholarly outputs via Figshare — list public articles, manage private uploads, and organize collections directly from your AI agent.

Douyin Local Life API / 抖音生活服务
8 toolsChina's leading local life platform — manage shops, process orders, and verify coupons via AI.

DOL (Department of Labor)
5 toolsAccess US Department of Labor data including OSHA inspections, MSHA safety records, and wage compliance directly from your AI agent.

Open Library Alternative
3 toolsUniversal open book database — search millions of books, authors, and editions via AI.
