updated 2026-11-10 04:07 UTC

Oxylabs MCP

Repository Website by oxylabs

Official Oxylabs MCP integration

MCP Servers Python Needs review MIT

Is Oxylabs MCP safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 3.1 / 10
Provenance Attested
Signed commits 73%
Last push 5d ago
Advisories None known
Compare Oxylabs MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Oxylabs MCP scores 75.5/100 (Grade B), ranked #261 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 3.1/10; 73% of recent commits are signed; no published advisory affects its latest release (oxylabs-mcp); last pushed 2026-11-05. Every point is earned from checkable signals — never paid placement. How scoring works →

How Oxylabs MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge
Active listing, but review is needed
  • [5.1] repository is archived

Chain of custody

Scanners check what the code says. This traces who ships Oxylabs MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/oxylabs/oxylabs-mcp, MIT, last pushed 2026-11-05. 73% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.1/10 (scanned Nov 7, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection3
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 3
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked and attested

    • PyPI oxylabs-mcp Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: oxylabs-mcp 0.10.2. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-10-29 Package provenance attestation detected
  • 2026-09-02 OSSF Scorecard: 4.7/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Oxylabs MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Oxylabs MCP compares in MCP Servers

  1. #149 UK Legal Research 75.7 +0.2
  2. #150 Code Index MCP 75.5 ±0
  3. #151 Oxylabs MCP 75.5 this agent
  4. #152 Sec Edgar MCP 75.4 −0.1
  5. #153 Cronometer Api MCP 75.4 −0.1

Bars show each HVTrust score; the tick marks Oxylabs MCP’s 75.5.

Where the 75.5 comes from

HVTrust dimensions vs the MCP Servers average

75.5 / 100 · 100.0% confidence

Oxylabs MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
15.0 / 25
4.2 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
11.1 / 17
1.2 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
16.0 / 20
3.8 above avg 12.2
AdoptionLog-scaled stars · package downloads
10.4 / 20
2.8 above avg 7.6

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-11-06
Rank Moved
Rank dropped 25 spots (#231 → #256)
2026-11-05
Warning Issued
Warning: eligibility issues detected
2026-10-30
Rank Moved
Rank rose 35 spots (#256 → #221)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.1/10. Tighten the weakest checks to improve public safety evidence.
Review Flags
[5.1] repository is archived
Compare with another agent
View MCP Servers Report missing data
56.7
Activity sub-score · out of 100
#151
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 5 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
104
Forks
26
Last Push
2026-11-05
5 days ago
Commits (4 wk)
11
Downloads (7d)
14,906
pypi
HN mentions (30d)
—
Open Issues
2
Rank Change
▼1
was #260

Analysis

Activity Inputs

56.7 / 100
StarsRepository reach
12.1 / 30
FreshnessLast push recency
24.3 / 25
ActivityRecent commits
13.5 / 25
CommunityFork signal
6.7 / 20

Common questions about Oxylabs MCP

Public supply-chain signals for Oxylabs MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Oxylabs MCP carries less obvious unverified-evidence risk than projects with thin signals.
Does Oxylabs MCP publish package provenance?
Yes. Oxylabs MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Oxylabs MCP have an OpenSSF Scorecard?
Oxylabs MCP has an OpenSSF Scorecard score of 3.1/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Oxylabs MCP actively maintained?
Actively maintained. The repository was pushed to within the last 5 day(s).
What license does Oxylabs MCP use?
Oxylabs MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Oxylabs MCP's commits signed?
73% of the last 100 commits to Oxylabs MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Oxylabs MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Oxylabs MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-10-29
Provenance Added
Package provenance attestation detected
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Oxylabs MCP?

For maintainers

HVTrust scores Oxylabs MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 37Warning Issued 5HVTrust 4Grade 3Warning Cleared 3Score 2Scorecard 1Delisted 1Listed 1MCP 1Provenance 1
2026-11-06
Rank Moved
Rank dropped 25 spots (#231 → #256)
2026-11-05
Warning Issued
Warning: eligibility issues detected
2026-10-30
Rank Moved
Rank rose 35 spots (#256 → #221)
2026-10-29
Provenance Added
Package provenance attestation detected
2026-10-29
Grade Changed
Trust grade C → B
2026-10-29
Rank Moved
Rank rose 377 spots (#633 → #256)
2026-10-29
HVTrust Changed
HVTrust up 13.1pts (62.2 → 75.3)
2026-10-28
Rank Moved
Rank rose 43 spots (#676 → #633)
2026-10-24
Rank Moved
Rank rose 59 spots (#727 → #668)
2026-10-19
Rank Moved
Rank rose 36 spots (#760 → #724)
2026-10-16
Rank Moved
Rank dropped 53 spots (#701 → #754)
2026-10-15
Warning Cleared
Warning cleared: eligibility issues resolved
2026-10-15
Rank Moved
Rank rose 172 spots (#873 → #701)
2026-10-15
HVTrust Changed
HVTrust up 5.4pts (53.6 → 59.0)
2026-10-15
Activity Score Changed
Activity score up 14pts (39 → 52)
2026-10-13
Rank Moved
Rank dropped 46 spots (#819 → #865)
2026-10-09
Rank Moved
Rank dropped 14 spots (#814 → #828)
2026-10-08
Rank Moved
Rank rose 16 spots (#830 → #814)
2026-10-07
Rank Moved
Rank dropped 64 spots (#766 → #830)
2026-10-07
Activity Score Changed
Activity score down 6pts (46 → 40)
2026-10-05
Warning Issued
Warning: eligibility issues detected
2026-10-04
Rank Moved
Rank dropped 11 spots (#747 → #758)
2026-10-03
Warning Cleared
Warning cleared: eligibility issues resolved
2026-10-02
Rank Moved
Rank dropped 13 spots (#743 → #756)
2026-09-30
Warning Issued
Warning: eligibility issues detected
2026-09-29
Warning Cleared
Warning cleared: eligibility issues resolved
2026-09-28
Warning Issued
Warning: eligibility issues detected
2026-09-25
Rank Moved
Rank dropped 17 spots (#701 → #718)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 311 spots (#1003 → #692)
2026-09-23
HVTrust Changed
HVTrust up 32.8pts (24.9 → 57.7)
2026-09-22
Newly Listed
First tracked at rank #1003
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank dropped 28 spots (#645 → #673)
2026-09-17
Rank Moved
Rank dropped 52 spots (#584 → #636)
2026-09-16
Warning Issued
Warning: eligibility issues detected
2026-09-16
Rank Moved
Rank rose 19 spots (#603 → #584)
2026-09-12
Rank Moved
Rank dropped 13 spots (#576 → #589)
2026-09-11
Rank Moved
Rank dropped 14 spots (#562 → #576)
2026-09-10
Rank Moved
Rank dropped 72 spots (#490 → #562)
2026-09-09
Rank Moved
Rank dropped 26 spots (#464 → #490)
2026-09-07
Rank Moved
Rank rose 14 spots (#473 → #459)
2026-09-06
Rank Moved
Rank dropped 46 spots (#427 → #473)
2026-09-05
Rank Moved
Rank dropped 67 spots (#360 → #427)
2026-09-04
Rank Moved
Rank dropped 13 spots (#347 → #360)
2026-09-03
Rank Moved
Rank dropped 31 spots (#316 → #347)
2026-09-02
Scorecard Added
OSSF Scorecard: 4.7/10
2026-09-02
Grade Changed
Trust grade D → C
2026-09-02
Rank Moved
Rank rose 660 spots (#976 → #316)
2026-09-02
HVTrust Changed
HVTrust up 26.3pts (38.0 → 64.3)
2026-09-01
Rank Moved
Rank dropped 44 spots (#932 → #976)
2026-08-31
Rank Moved
Rank dropped 30 spots (#902 → #932)
2026-08-30
Rank Moved
Rank dropped 40 spots (#862 → #902)
2026-08-29
Rank Moved
Rank dropped 47 spots (#815 → #862)
2026-08-28
Rank Moved
Rank dropped 24 spots (#791 → #815)
2026-08-27
Rank Moved
Rank dropped 23 spots (#768 → #791)
2026-08-26
Rank Moved
Rank dropped 93 spots (#675 → #768)
2026-08-16
Rank Moved
Rank dropped 13 spots (#657 → #670)
GitHub → Website → PyPI: oxylabs-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 75.5 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/oxylabs-mcp.svg)](https://hvtracker.net/agents/oxylabs-mcp)
HTML:
<a href="https://hvtracker.net/agents/oxylabs-mcp"><img src="https://hvtracker.net/badge/oxylabs-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON