Maritime Resource Compliance MCP Server

Maritime resource compliance intelligence for fishing quotas, oil and gas licenses, waste carriers, and coastal hazards — delivered as a Model Context Protocol server your AI agent can call directly. This server connects Claude, Cursor, Windsurf, or any MCP-compatible client to 7 live government and open data sources, surfacing compliance violations, ecosystem risk scores, and sustainability assessments in seconds.

Built for environmental analysts, offshore compliance teams, and fisheries regulators who need structured, queryable maritime data inside their AI workflows. Eight specialized tools cover every dimension of maritime resource compliance: from individual quota utilization to portfolio-level sustainability indexing.

What data can you extract?

Why use Maritime Resource Compliance MCP Server?

Compliance teams in the maritime and energy sectors spend hours each week pulling data from the FQA Register, NSTA portal, Environment Agency database, NOAA alerts, and GBIF — then manually reconciling figures across spreadsheets. A single compliance snapshot for a North Sea operator can take a half-day to assemble from five separate government portals.

This server automates the entire process. One tool call fetches, cross-references, and scores data from all 7 sources simultaneously, returning structured JSON your AI agent can reason over immediately.

• Scheduling — run daily compliance checks or weekly sustainability reports on automatic intervals
• API access — trigger any of the 8 tools from Python, JavaScript, or any HTTP client via Apify's REST API
• Proxy rotation — underlying actor calls use Apify's proxy infrastructure to avoid rate limiting on government data sources
• Monitoring — configure Slack or email alerts when compliance scores fall below thresholds
• Integrations — connect results to Zapier, Make, Google Sheets, or internal BI dashboards via webhooks

Features

• 8 specialized MCP tools covering resource mapping, fishing compliance, environmental violations, extraction trends, ecosystem risk, coastal hazards, sustainability assessment, and comprehensive reporting
• 7 live data sources queried in parallel: FQA Register, NSTA Oil and Gas, Environment Agency Waste Carriers, NOAA Weather, UK Flood Monitoring, GBIF Biodiversity, and World Bank Indicators
• Fishing quota compliance engine flags over-allocation (utilizationRatio > 1.0) as violations and near-limit quotas (utilizationRatio > 0.85) as warnings across any region or species
• Environmental violation detection cross-references waste carrier registration status — revoked registrations trigger critical severity, expired registrations trigger high severity — against World Bank CO₂ indicator data
• Weighted ecosystem risk model with 4 factors: biodiversity pressure (35% weight), resource extraction intensity (30% weight), environmental stress (20% weight), and cumulative impact (15% weight)
• Sustainability index balances four dimensions — extraction balance, biodiversity health, environmental compliance, and hazard resilience — into a single 0–1 score with actionable recommendations
• Network graph construction builds nodes (quotas, licenses, carriers, weather events, flood warnings, species, indicators) and typed edges (resource_overlap, waste_from_extraction, hazard_correlation, biodiversity_pressure)
• Composite coastal hazard scoring combines NOAA weather alert severity with UK flood warning severity levels into a single weighted risk score
• Temporal extraction trend analysis groups oil/gas license and fishing quota data by year, calculates extraction intensity index (licenseCount × 10 + quotaVolume / 100), and compares first-half vs second-half averages to determine overall direction
• Fully parallel execution — generate_maritime_compliance_report runs all 7 sub-analyses concurrently via Promise.all, minimizing latency for full assessments
• Graceful error handling — individual actor failures return empty arrays rather than crashing the tool call, ensuring partial results are always returned
• Standby mode operation — runs persistently on the Apify platform with 128–512 MB memory, ready to serve tool calls without cold-start delays

Use cases for maritime resource compliance intelligence

Fisheries compliance monitoring

Quota managers and fisheries regulators need to know which species and vessels are approaching or exceeding allocation limits before enforcement action becomes necessary. The assess_fishing_quota_compliance tool fetches live FQA Register data, computes per-quota utilization ratios, and flags violations immediately. Analysts can filter by region or species and integrate results directly into regulatory reporting workflows.

Oil and gas environmental compliance

Offshore energy operators and environmental watchdog organizations track NSTA licensing activity to identify extraction intensity trends and assess whether North Sea block activity is increasing. The analyze_resource_extraction_trends tool groups license issuance by year and computes an extraction intensity index, making it easy to detect acceleration in leasing activity that may warrant regulatory review.

Waste carrier compliance auditing

Environmental compliance officers screening marine-adjacent waste carriers need to identify operators with revoked or expired registrations before contracting. The detect_environmental_violations tool cross-references Environment Agency waste carrier data against World Bank environmental indicators, flagging critical-severity violations for carriers operating outside their registration status.

Marine ecosystem health assessment

ESG teams and environmental consultancies preparing sustainability reports need an objective ecosystem risk score that combines extraction pressure with biodiversity data. The score_marine_ecosystem_risk tool draws on GBIF species counts, fishing and oil/gas license volumes, and NOAA severe weather events to produce a 0–1 risk score with factor-level attribution — ready for inclusion in ESG disclosures or regulatory submissions.

Coastal operations hazard planning

Port operators, offshore facility managers, and marine logistics teams need real-time visibility of active coastal hazards before committing vessels or crews. The track_coastal_hazards tool aggregates NOAA weather alerts and UK flood warnings into a unified hazard list with composite risk scoring, severity breakdown, and active-period timestamps.

Sustainability reporting and ESG disclosure

Companies with maritime supply chain exposure face growing requirements to demonstrate sustainable resource use. The assess_sustainable_resource_use tool produces a sustainability index across four scored dimensions with specific recommendations, providing defensible quantitative evidence for regulatory filings, investor reports, and public transparency disclosures.

How to connect this MCP server

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "maritime-resource-compliance": {
      "url": "https://maritime-resource-compliance-mcp.apify.actor/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_APIFY_TOKEN"
      }
    }
  }
}

Cursor / Windsurf / Cline

Point your MCP client to:

https://maritime-resource-compliance-mcp.apify.actor/mcp

Include your Apify API token as a Bearer token in the Authorization header.

Python (via MCP client)

from apify_client import ApifyClient

client = ApifyClient("YOUR_API_TOKEN")

run = client.actor("ryanclinton/maritime-resource-compliance-mcp").call(run_input={})

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

Direct cURL

# Call the assess_fishing_quota_compliance tool
curl -X POST "https://maritime-resource-compliance-mcp.apify.actor/mcp" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_APIFY_TOKEN" \
  -d '{"jsonrpc":"2.0","method":"tools/call","params":{"name":"assess_fishing_quota_compliance","arguments":{"region":"North Sea","species":"cod","maxResults":50}},"id":1}'

# Call generate_maritime_compliance_report for a full assessment
curl -X POST "https://maritime-resource-compliance-mcp.apify.actor/mcp" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_APIFY_TOKEN" \
  -d '{"jsonrpc":"2.0","method":"tools/call","params":{"name":"generate_maritime_compliance_report","arguments":{"region":"North Sea","maxResults":50}},"id":2}'

MCP tools

Tool parameters

All tools accept the same optional parameters:

Input tips

• Omit region for global coverage — leaving region blank queries all available data from each source with no geographic filter applied
• Use maxResults: 20 for fast tests — reducing from the default 100 cuts per-tool latency significantly when exploring a new region
• Filter sources to reduce cost — passing ["fishing", "biodiversity"] to map_maritime_resource_network skips the 5 other actor calls, cutting execution time
• Call generate_maritime_compliance_report for full reports — this single tool runs all 7 analyses concurrently; calling each tool individually costs the same but takes longer
• Use region names recognized by each source — "North Sea" works for NOAA and NSTA; "England" works for the Environment Agency and UK Flood Monitoring

Output example

{
  "reportId": "MCR-1742476800000-k4f9xz",
  "generatedAt": "2026-03-20T09:00:00.000Z",
  "region": "North Sea",
  "executiveSummary": "Maritime Compliance Report for North Sea. Overall compliance score: 71.4% (risk level: moderate). Analyzed 48 fishing quotas: 39 compliant, 7 warnings, 2 violations. Overall compliance rate: 81.3%. Screened 62 waste carriers. Found 8 violations (1 critical, 3 high, 4 medium). Cross-referenced with 12 environmental indicators. Ecosystem risk: moderate. Sustainability: marginal. Active coastal hazards: 14.",
  "fishingCompliance": {
    "quotas": [
      {
        "id": "fq-0000",
        "species": "Atlantic cod",
        "allocation": 142,
        "utilization": 126.38,
        "utilizationRatio": 0.890,
        "complianceStatus": "warning"
      },
      {
        "id": "fq-0001",
        "species": "North Sea herring",
        "allocation": 890,
        "utilization": 834.6,
        "utilizationRatio": 0.938,
        "complianceStatus": "warning"
      },
      {
        "id": "fq-0002",
        "species": "Plaice",
        "allocation": 215,
        "utilization": 248.45,
        "utilizationRatio": 1.155,
        "complianceStatus": "violation"
      }
    ],
    "overallComplianceRate": 0.813,
    "violationCount": 2,
    "warningCount": 7,
    "summary": "Analyzed 48 fishing quotas: 39 compliant, 7 warnings, 2 violations. Overall compliance rate: 81.3%."
  },
  "environmentalViolations": {
    "violations": [
      {
        "carrierId": "wc-0004",
        "carrierName": "Harbour Waste Management Ltd",
        "violationType": "Revoked registration operating",
        "severity": "critical",
        "environmentalImpact": "Unregulated waste handling poses severe contamination risk",
        "relatedIndicators": ["CO2 emissions per capita", "Forest area", "Access to electricity"]
      },
      {
        "carrierId": "wc-0011",
        "carrierName": "Coastal Marine Disposal Services",
        "violationType": "Expired registration",
        "severity": "high",
        "environmentalImpact": "Lapsed oversight increases pollution likelihood",
        "relatedIndicators": ["CO2 emissions per capita", "Forest area", "Access to electricity"]
      }
    ],
    "totalViolations": 8,
    "severityBreakdown": { "low": 54, "medium": 4, "high": 3, "critical": 1 },
    "summary": "Screened 62 waste carriers. Found 8 violations (1 critical, 3 high, 4 medium). Cross-referenced with 12 environmental indicators."
  },
  "extractionTrends": {
    "trends": [
      { "period": "2021", "licenseCount": 14, "quotaVolume": 3200, "extractionIntensity": 172, "trend": "stable" },
      { "period": "2022", "licenseCount": 18, "quotaVolume": 3850, "extractionIntensity": 218.5, "trend": "increasing" },
      { "period": "2023", "licenseCount": 22, "quotaVolume": 4100, "extractionIntensity": 261, "trend": "increasing" }
    ],
    "overallTrend": "increasing",
    "intensityIndex": 217.17,
    "summary": "Analyzed 54 oil/gas licenses and 48 fishing quotas across 3 periods. Overall extraction trend: increasing. Average intensity index: 217.17."
  },
  "ecosystemRisk": {
    "riskScore": 0.42,
    "riskLevel": "moderate",
    "factors": [
      { "factor": "Biodiversity Pressure", "score": 0.38, "weight": 0.35, "contribution": 0.133, "details": "78 species tracked; pressure index 38.0%" },
      { "factor": "Resource Extraction Intensity", "score": 0.72, "weight": 0.30, "contribution": 0.216, "details": "48 fishing quotas, 22 oil/gas licenses; intensity 72.0%" },
      { "factor": "Environmental Stress", "score": 0.30, "weight": 0.20, "contribution": 0.060, "details": "6 severe weather events out of 31 total; stress 30.0%" },
      { "factor": "Cumulative Impact", "score": 0.47, "weight": 0.15, "contribution": 0.070, "details": "Combined cumulative pressure from all factors" }
    ],
    "biodiversityPressure": 0.380,
    "extractionPressure": 0.720,
    "environmentalStress": 0.300,
    "summary": "Marine ecosystem risk: moderate (score 42.0%). Biodiversity pressure 38.0%, extraction intensity 72.0%, environmental stress 30.0%."
  },
  "coastalHazards": {
    "hazards": [
      { "id": "weather-0", "type": "wind", "severity": "high", "location": "Northern North Sea", "description": "Gale Warning in effect", "activeFrom": "2026-03-20T06:00:00Z", "activeTo": "2026-03-21T00:00:00Z" },
      { "id": "flood-0", "type": "flood", "severity": "moderate", "location": "Humber Estuary", "description": "Flood alert — low-lying areas at risk", "activeFrom": "2026-03-20T08:00:00Z" }
    ],
    "activeHazardCount": 14,
    "severityBreakdown": { "low": 6, "moderate": 5, "high": 2, "extreme": 1 },
    "compositeRisk": 0.36,
    "summary": "Tracking 14 coastal hazards (1 extreme, 2 high, 5 moderate, 6 low). Composite risk: 36.0%. Sources: 9 weather alerts, 5 flood warnings."
  },
  "sustainableUse": {
    "sustainabilityIndex": 0.534,
    "rating": "marginal",
    "dimensions": {
      "extractionBalance": 0.533,
      "biodiversityHealth": 0.780,
      "environmentalCompliance": 0.900,
      "hazardResilience": 0.600
    },
    "recommendations": [
      "Reduce extraction intensity — license/quota volume exceeds sustainable thresholds"
    ],
    "summary": "Sustainability index: 53.4% (marginal). Extraction balance 53.3%, biodiversity health 78.0%, environmental compliance 90.0%, hazard resilience 60.0%."
  },
  "overallComplianceScore": 0.714,
  "overallRiskLevel": "moderate"
}

Output fields

How much does it cost to run maritime compliance queries?

This MCP server uses pay-per-event pricing — you pay $0.045 per tool call. Platform compute costs are included.

Apify's free tier includes $5 of monthly platform credits — enough for approximately 111 tool calls per month at no cost.

You can set a maximum spending limit per run to control costs. The actor stops when your budget is reached.

Comparable maritime data services and ESG data platforms charge $500–2,000/month for similar coverage. With this server, most compliance teams spend under $5/month.

How Maritime Resource Compliance MCP Server works

Phase 1: Data collection via parallel actor calls

When a tool call arrives, the server dispatches requests to the relevant Apify actors simultaneously using Promise.all. The actor-client.ts module instantiates an ApifyClient with your APIFY_TOKEN and calls each actor via client.actor(actorName).call(input, { waitSecs: 180, memory: 256 }). Up to 7 actors run concurrently — FQA Register Search, NSTA Oil and Gas Licenses, EA Waste Carriers, NOAA Weather Alerts, UK Flood Warnings, GBIF Species Search, and World Bank Indicators. If any actor fails, it returns an empty array rather than propagating an error, ensuring partial results are always available.

Phase 2: Network graph construction

The buildMaritimeNetwork function in maritime-network.ts processes raw arrays from all 7 sources into a typed node-edge graph. Each source maps to a distinct node type: quota (fishing), license (oil_gas), carrier (waste), weather_event (weather), flood_warning (flood), species (biodiversity), indicator (economic). Four relationship types are then created as cross-type edges: resource_overlap (quota↔license), waste_from_extraction (carrier↔license), hazard_correlation (weather↔flood), and biodiversity_pressure (species↔quota).

Phase 3: Compliance and risk scoring

Each specialized tool applies its own scoring model to the collected data. The fishing compliance engine computes utilizationRatio = utilization / allocation and applies thresholds at 0.85 (warning) and 1.0 (violation). The ecosystem risk model applies weighted factor contributions: biodiversity pressure uses 1 - speciesCount / 200, extraction pressure uses extractionVolume / 100, and environmental stress uses severeEventCount / 20, all clamped to [0, 1]. The sustainability index weights four dimensions at 30/30/20/20 and maps the resulting score to sustainable (≥0.70), marginal (≥0.45), unsustainable (≥0.25), or critical (<0.25).

Phase 4: Compliance report aggregation

generate_maritime_compliance_report runs all 7 sub-analyses concurrently then computes an overallComplianceScore using a weighted formula: fishing compliance rate (25%) + normalized violation rate (20%) + inverse ecosystem risk (20%) + sustainability index (20%) + inverse coastal hazard risk (15%). The final score maps to low (≥0.75), moderate (≥0.50), high (≥0.25), or critical (<0.25) risk levels.

Tips for best results

1. Start with generate_maritime_compliance_report for unfamiliar regions. This single call runs all analyses in parallel and gives you a complete picture before you decide which specific tools to drill into.

2. Use maxResults: 20 when testing prompts. Reducing from the default 100 cuts execution time significantly and costs the same $0.045 per call. Switch to higher limits once your workflow is validated.

3. Filter sources in map_maritime_resource_network to trim scope. Passing ["fishing", "biodiversity"] instead of all 7 sources reduces the number of underlying actor calls by 71% and makes the network graph faster to generate.

4. Pass specific species to assess_fishing_quota_compliance. Using species: "cod" rather than a broad region query focuses the FQA Register search on the species of interest, reducing noise in compliance results.

5. Schedule generate_maritime_compliance_report weekly to build trend history. The extractionTrends output becomes more informative over time. Store each report's reportId and overallComplianceScore in a spreadsheet to track compliance trajectory.

6. Cross-reference detect_environmental_violations results with score_marine_ecosystem_risk. Carriers with critical or high severity violations in regions with high ecosystem risk scores represent the highest-priority enforcement targets.

7. Use the sustainableUse.recommendations array directly in reports. The scoring engine generates specific, actionable recommendations based on which dimensions fall below 0.5, saving time in report drafting.

8. Combine with the track_coastal_hazards tool before vessel operations. The composite risk score and active-period timestamps allow operations teams to identify specific weather windows, not just general hazard presence.

Combine with other Apify actors

Limitations

• Geographic coverage is primarily UK-focused. FQA Register, NSTA, and Environment Agency data cover UK waters and England respectively. GBIF and World Bank have global reach; NOAA covers US and Atlantic regions.
• No vessel movement tracking. Fishing compliance analysis is based on quota allocation records, not AIS vessel tracking or catch verification data. Quota allocation risk does not confirm actual over-fishing.
• Quota utilization estimates may use defaults. Where live utilization data is absent from the FQA Register response, the engine estimates utilization as a random fraction of allocation. Treat utilization ratios as indicative rather than definitive without verifying against primary source data.
• Environmental violation severity is based on registration status only. The violation detection model classifies severity from carrier registration type and status. It does not incorporate actual pollution incident records or enforcement history.
• maxResults caps each source at 500 items. The actor client fetches a maximum of 500 dataset items per underlying actor call, regardless of the maxResults parameter.
• Extraction trend analysis requires date fields in source data. If NSTA or FQA records lack year or date fields, all records are grouped under "Unknown" rather than by year, producing a single trend period.
• Real-time hazard data has a polling delay. NOAA and UK Flood Monitoring data reflects conditions at query time; alerts issued in the minutes before your query may not appear if their respective actors have not yet indexed them.
• Standby mode is required for persistent operation. Running the server in non-standby mode exits after a 1-second health check. Configure your Apify actor to use standby mode for continuous availability.

Integrations

• Apify API — trigger tool calls programmatically and retrieve results from any language or platform
• Webhooks — post compliance score results to Slack, Teams, or internal dashboards when runs complete
• Zapier — route environmental violation alerts into ticketing systems or compliance management workflows automatically
• Make — schedule weekly compliance reports and push sustainability index scores to Google Sheets or Airtable
• Google Sheets — store time-series compliance scores for trend analysis and regulatory audit trails
• LangChain / LlamaIndex — use extracted maritime compliance data as a retrieval source for RAG pipelines focused on environmental regulation and sustainability research

Troubleshooting

• Tool returns empty results for a region. Some source databases use specific naming conventions. Try "North Sea" instead of "UK North Sea", or "England" instead of "UK" for Environment Agency data. GBIF accepts scientific names and common names. If a source returns no data, the tool still returns results from the other sources rather than failing.

• generate_maritime_compliance_report takes longer than expected. The full report tool runs 7 parallel actor calls. In periods of high Apify platform load, individual actor calls can take up to 180 seconds. Reduce maxResults to 20 to cut execution time for time-sensitive queries.

• Utilization ratios appear unexpectedly high. Where FQA Register records do not include a utilization or catch field, the engine estimates utilization using a random fraction of allocation. Check the raw metadata field on the quota record to confirm whether the source data includes actual catch figures.

• Waste carrier violations show only low severity. The violation severity model depends on the carrier's status field containing "expir" or "revok" substrings. If the Environment Agency returns registration records without a clear status value, all carriers default to low severity. This is a data quality limitation of the source, not a scoring error.

• MCP client cannot connect to the server URL. Confirm the actor is running in standby mode in your Apify console. The server only listens on the MCP endpoint when APIFY_META_ORIGIN === 'STANDBY'. In non-standby mode, it starts briefly for a health check then exits.

Responsible use

• This server only accesses publicly available government registers and open data APIs.
• Respect the terms of use for FQA Register, NSTA, Environment Agency, NOAA, UK Flood Monitoring, GBIF, and World Bank data.
• Comply with applicable data protection laws when using extracted entity data for enforcement referrals or commercial purposes.
• Do not use compliance violation outputs to make regulatory enforcement decisions without verification against primary source records.
• For guidance on data use legality, see Apify's guide.

FAQ

How many maritime compliance tool calls can I make per month on the free plan? Apify's free tier includes $5 of monthly credits. At $0.045 per tool call, that covers approximately 111 calls per month. Each generate_maritime_compliance_report call counts as one event, even though it internally runs 7 data source queries.

Does maritime resource compliance MCP work outside the UK? Fishing quota and oil/gas license data are UK-focused (FQA Register and NSTA Continental Shelf). Waste carrier data covers England. NOAA weather alerts cover US coastal and Atlantic regions. GBIF biodiversity data is global. World Bank indicators are global. For broader geographic coverage, the biodiversity and economic indicator tools work anywhere.

How accurate is the fishing quota compliance analysis? Compliance analysis is accurate to the extent that FQA Register records include allocation and utilization fields. Where these fields are absent, the engine estimates utilization. Always verify violation flags against the FQA Register directly before taking regulatory action.

Can I use this MCP server to detect illegal fishing? The server identifies quota allocation compliance risk — situations where allocated volumes exceed safe limits or where utilization approaches maximum allocation. It does not track vessel movements, AIS signals, or actual reported catches. It can surface quota-based risk indicators but cannot confirm illegal fishing activity.

How is this different from commercial maritime data services like Kpler or Windward? Commercial platforms focus on vessel tracking and cargo intelligence at $500–2,000/month. This server focuses on regulatory compliance data from government registers — fishing quotas, oil/gas licenses, waste carriers, and environmental indicators — that commercial platforms typically do not cover. The two are complementary rather than competing.

How fresh is the maritime compliance data? All data is fetched live from each source at query time. There is no caching layer. Fishing quota registers, NSTA license databases, and weather alerts reflect their current state when your tool call runs.

Can I monitor maritime compliance trends over time? Yes. Use Apify's built-in scheduling to run generate_maritime_compliance_report on a daily or weekly cadence. Each report includes an overallComplianceScore and extractionTrends section that builds a historical record when stored in a dataset over time.

What happens if one of the 7 underlying data sources is unavailable? The actor client wraps each actor call in a try-catch block. If an individual source fails, it returns an empty array and logs a warning. The tool continues with data from the remaining sources. Tool output will note reduced data but will not error.

Is it legal to use government register data for compliance analysis? All data sources — FQA Register, NSTA, Environment Agency, NOAA, UK Flood Monitoring, GBIF, and World Bank — are publicly available with open data policies. Using this data for compliance research and reporting is legal. See Apify's guide on web scraping legality.

Can I connect this server to Claude Desktop? Yes. Add the server URL (https://maritime-resource-compliance-mcp.apify.actor/mcp) to your claude_desktop_config.json with an Authorization header containing your Apify API token. All 8 tools will appear in Claude's tool list immediately.

How long does a full compliance report take? generate_maritime_compliance_report runs 7 actor calls in parallel. With maxResults: 50, a typical run completes in 30–90 seconds depending on source API response times. Using maxResults: 20 reduces this to 15–40 seconds.

Can I use this MCP server with Cursor or Windsurf for environmental research? Yes. Point your Cursor or Windsurf MCP configuration to https://maritime-resource-compliance-mcp.apify.actor/mcp with your Apify token as a Bearer header. The tools will appear in the IDE's agent tool list and can be invoked in any research conversation.

Help us improve

If you encounter issues, you can help us debug faster by enabling run sharing in your Apify account:

1. Go to Account Settings > Privacy
2. Enable Share runs with public Actor creators

This lets us see your run details when something goes wrong, so we can fix issues faster. Your data is only visible to the actor developer, not publicly.

Support

Found a bug or have a feature request? Open an issue in the Issues tab on this actor's page. For custom solutions or enterprise integrations, reach out through the Apify platform.