Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

OpenResearch MCP

PYPI · OPENRESEARCH-MCP

Zero-auth research MCP: web, academic, finance, news, weather, macro, social, SEC. No keys.

Available components

pypi · openresearch-mcp 30
−15 this week 30 Trust /100

Last scanned (19 hours ago)

Scores higher than 17% of PyPI servers

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security32
  • Malware scan not yet available for this package.Unverified
  • CVE check failed: a known high-severity CVE affects pypdf 5.9.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 2 of 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to olanokhin/openresearch-mcp). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 118 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 0
    • CVE-2026-59938 affects this package: high ▼ security
    • CVE-2026-102999 affects this package: high ▼ security
    • CVE-2025-66019 affects this package: high ▼ security
    • CVE-2026-54651 affects this package: high ▼ security
    • CVE-2026-102993 affects this package: high ▼ security
    • CVE-2026-22691 affects this package: high ▼ security
    • CVE-2026-113795 affects this package: high ▼ security
    • CVE-2026-41313 affects this package: high ▼ security
    • CVE-2026-84311 affects this package: high ▼ security
    • CVE-2026-59937 affects this package: high ▼ security
    • CVE-2026-27026 affects this package: high ▼ security
    • CVE-2026-48735 affects this package: high ▼ security
    • CVE-2026-41168 affects this package: high ▼ security
    • CVE-2026-54530 affects this package: high ▼ security
    • CVE-2026-119205 affects this package: high ▼ security
    • CVE-2026-119208 affects this package: high ▼ security
    • CVE-2026-102998 affects this package: high ▼ security
    • CVE-2026-113786 affects this package: high ▼ security
    • CVE-2026-115580 affects this package: high ▼ security
    • CVE-2026-48155 affects this package: high ▼ security
    • CVE-2026-102995 affects this package: high ▼ security
    • CVE-2026-28351 affects this package: high ▼ security
    • CVE-2026-27024 affects this package: high ▼ security
    • CVE-2026-113794 affects this package: high ▼ security
    • CVE-2026-119206 affects this package: high ▼ security
    • CVE-2026-113789 affects this package: high ▼ security
    • CVE-2026-119207 affects this package: high ▼ security
    • CVE-2026-115572 affects this package: high ▼ security
    • CVE-2026-82398 affects this package: high ▼ security
    • CVE-2026-49461 affects this package: high ▼ security
    • CVE-2026-102996 affects this package: high ▼ security
    • CVE-2026-49460 affects this package: high ▼ security
    • CVE-2026-22690 affects this package: high ▼ security
    • CVE-2025-55197 affects this package: high ▼ security
    • CVE-2026-119209 affects this package: high ▼ security
    • CVE-2025-62707 affects this package: high ▼ security
    • CVE-2026-115585 affects this package: high ▼ security
    • CVE-2026-31826 affects this package: high ▼ security
    • CVE-2026-41312 affects this package: high ▼ security
    • CVE-2026-54531 affects this package: high ▼ security
    • CVE-2026-119203 affects this package: high ▼ security
    • CVE-2026-48156 affects this package: high ▼ security
    • CVE-2026-84310 affects this package: high ▼ security
    • CVE-2026-119204 affects this package: high ▼ security
    • CVE-2026-102994 affects this package: high ▼ security
    • CVE-2026-113793 affects this package: high ▼ security
    • CVE-2026-113792 affects this package: high ▼ security
    • CVE-2026-71852 affects this package: high ▼ security
    • CVE-2026-113790 affects this package: high ▼ security
    • CVE-2026-33699 affects this package: high ▼ security
    • CVE-2026-102997 affects this package: high ▼ security
    • CVE-2026-59935 affects this package: high ▼ security
    • CVE-2026-27888 affects this package: high ▼ security
    • CVE-2026-28804 affects this package: high ▼ security
    • CVE-2026-59936 affects this package: high ▼ security
    • CVE-2026-33123 affects this package: high ▼ security
    • CVE-2026-24688 affects this package: high ▼ security
    • CVE-2026-27628 affects this package: high ▼ security
    • CVE-2026-113791 affects this package: high ▼ security
    • CVE-2026-103000 affects this package: high ▼ security
    • CVE-2026-27025 affects this package: high ▼ security
    • CVE-2026-40260 affects this package: high ▼ security
    • CVE-2026-84309 affects this package: high ▼ security
    • CVE-2025-62708 affects this package: high ▼ security
    • CVE-2026-41314 affects this package: high ▼ security
    • CVE-2026-71870 affects this package: high ▼ security
    • CVE-2026-57204 affects this package: high ▼ security
  • 3 Nov 26 0
    • CVE-2026-115585 affects this package: high ▼ security
    • CVE-2025-62707 affects this package: high ▼ security
    • CVE-2026-119209 affects this package: high ▼ security
    • CVE-2025-55197 affects this package: high ▼ security
    • CVE-2026-22690 affects this package: high ▼ security
    • CVE-2026-49460 affects this package: high ▼ security
    • CVE-2026-102996 affects this package: high ▼ security
    • CVE-2026-49461 affects this package: high ▼ security
    • CVE-2026-82398 affects this package: high ▼ security
    • CVE-2026-115572 affects this package: high ▼ security
    • CVE-2026-119207 affects this package: high ▼ security
    • CVE-2026-113789 affects this package: high ▼ security
    • CVE-2026-119206 affects this package: high ▼ security
    • CVE-2026-113794 affects this package: high ▼ security
    • CVE-2026-27024 affects this package: high ▼ security
    • CVE-2026-28351 affects this package: high ▼ security
    • CVE-2026-102995 affects this package: high ▼ security
    • CVE-2026-48155 affects this package: high ▼ security
    • CVE-2026-115580 affects this package: high ▼ security
    • CVE-2026-113786 affects this package: high ▼ security
    • CVE-2026-102998 affects this package: high ▼ security
    • CVE-2026-119208 affects this package: high ▼ security
    • CVE-2026-119205 affects this package: high ▼ security
    • CVE-2026-54530 affects this package: high ▼ security
    • CVE-2026-41168 affects this package: high ▼ security
    • CVE-2026-48735 affects this package: high ▼ security
    • CVE-2026-27026 affects this package: high ▼ security
    • CVE-2026-59937 affects this package: high ▼ security
    • CVE-2026-84311 affects this package: high ▼ security
    • CVE-2026-41313 affects this package: high ▼ security
    • CVE-2026-113795 affects this package: high ▼ security
    • CVE-2026-22691 affects this package: high ▼ security
    • CVE-2026-102993 affects this package: high ▼ security
    • CVE-2026-54651 affects this package: high ▼ security
    • CVE-2025-66019 affects this package: high ▼ security
    • CVE-2026-102999 affects this package: high ▼ security
    • CVE-2026-59938 affects this package: high ▼ security
    • CVE-2026-31826 affects this package: high ▼ security
    • CVE-2026-41312 affects this package: high ▼ security
    • CVE-2026-54531 affects this package: high ▼ security
    • CVE-2026-119203 affects this package: high ▼ security
    • CVE-2026-48156 affects this package: high ▼ security
    • CVE-2026-84310 affects this package: high ▼ security
    • CVE-2026-119204 affects this package: high ▼ security
    • CVE-2026-102994 affects this package: high ▼ security
    • CVE-2026-113793 affects this package: high ▼ security
    • CVE-2026-113792 affects this package: high ▼ security
    • CVE-2026-71852 affects this package: high ▼ security
    • CVE-2026-113790 affects this package: high ▼ security
    • CVE-2026-33699 affects this package: high ▼ security
    • CVE-2026-102997 affects this package: high ▼ security
    • CVE-2026-59935 affects this package: high ▼ security
    • CVE-2026-27888 affects this package: high ▼ security
    • CVE-2026-28804 affects this package: high ▼ security
    • CVE-2026-59936 affects this package: high ▼ security
    • CVE-2026-33123 affects this package: high ▼ security
    • CVE-2026-24688 affects this package: high ▼ security
    • CVE-2026-27628 affects this package: high ▼ security
    • CVE-2026-113791 affects this package: high ▼ security
    • CVE-2026-103000 affects this package: high ▼ security
    • CVE-2026-27025 affects this package: high ▼ security
    • CVE-2026-40260 affects this package: high ▼ security
    • CVE-2026-84309 affects this package: high ▼ security
    • CVE-2025-62708 affects this package: high ▼ security
    • CVE-2026-41314 affects this package: high ▼ security
    • CVE-2026-71870 affects this package: high ▼ security
    • CVE-2026-57204 affects this package: high ▼ security
  • 2 Nov 26 0

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

    • CVE-2026-102995 affects this package: high ▼ security
    • CVE-2026-57204 affects this package: high ▼ security
    • CVE-2026-71870 affects this package: high ▼ security
    • CVE-2026-41314 affects this package: high ▼ security
    • CVE-2025-62708 affects this package: high ▼ security
    • CVE-2026-84309 affects this package: high ▼ security
    • CVE-2026-40260 affects this package: high ▼ security
    • CVE-2026-27025 affects this package: high ▼ security
    • CVE-2026-103000 affects this package: high ▼ security
    • CVE-2026-113791 affects this package: high ▼ security
    • CVE-2026-27628 affects this package: high ▼ security
    • CVE-2026-24688 affects this package: high ▼ security
    • CVE-2026-33123 affects this package: high ▼ security
    • CVE-2026-59936 affects this package: high ▼ security
    • CVE-2026-28804 affects this package: high ▼ security
    • CVE-2026-27888 affects this package: high ▼ security
    • CVE-2026-59935 affects this package: high ▼ security
    • CVE-2026-102997 affects this package: high ▼ security
    • CVE-2026-33699 affects this package: high ▼ security
    • CVE-2026-113790 affects this package: high ▼ security
    • CVE-2026-71852 affects this package: high ▼ security
    • CVE-2026-113792 affects this package: high ▼ security
    • CVE-2026-113793 affects this package: high ▼ security
    • CVE-2026-102994 affects this package: high ▼ security
    • CVE-2026-119204 affects this package: high ▼ security
    • CVE-2026-84310 affects this package: high ▼ security
    • CVE-2026-48156 affects this package: high ▼ security
    • CVE-2026-119203 affects this package: high ▼ security
    • CVE-2026-54531 affects this package: high ▼ security
    • CVE-2026-41312 affects this package: high ▼ security
    • CVE-2026-31826 affects this package: high ▼ security
    • CVE-2026-59938 affects this package: high ▼ security
    • CVE-2026-102999 affects this package: high ▼ security
    • CVE-2025-66019 affects this package: high ▼ security
    • CVE-2026-54651 affects this package: high ▼ security
    • CVE-2026-102993 affects this package: high ▼ security
    • CVE-2026-22691 affects this package: high ▼ security
    • CVE-2026-113795 affects this package: high ▼ security
    • CVE-2026-41313 affects this package: high ▼ security
    • CVE-2026-84311 affects this package: high ▼ security
    • CVE-2026-59937 affects this package: high ▼ security
    • CVE-2026-27026 affects this package: high ▼ security
    • CVE-2026-48735 affects this package: high ▼ security
    • CVE-2026-41168 affects this package: high ▼ security
    • CVE-2026-54530 affects this package: high ▼ security
    • CVE-2026-119205 affects this package: high ▼ security
    • CVE-2026-119208 affects this package: high ▼ security
    • CVE-2026-102998 affects this package: high ▼ security
    • CVE-2026-113786 affects this package: high ▼ security
    • CVE-2026-115580 affects this package: high ▼ security
    • CVE-2026-48155 affects this package: high ▼ security
    • CVE-2026-28351 affects this package: high ▼ security
    • CVE-2026-27024 affects this package: high ▼ security
    • CVE-2026-113794 affects this package: high ▼ security
    • CVE-2026-119206 affects this package: high ▼ security
    • CVE-2026-113789 affects this package: high ▼ security
    • CVE-2026-119207 affects this package: high ▼ security
    • CVE-2026-115572 affects this package: high ▼ security
    • CVE-2026-82398 affects this package: high ▼ security
    • CVE-2026-49461 affects this package: high ▼ security
    • CVE-2026-102996 affects this package: high ▼ security
    • CVE-2026-49460 affects this package: high ▼ security
    • CVE-2026-22690 affects this package: high ▼ security
    • CVE-2025-55197 affects this package: high ▼ security
    • CVE-2026-119209 affects this package: high ▼ security
    • CVE-2025-62707 affects this package: high ▼ security
  • 30 Oct 26 −15

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

  • 14 Oct 26 +15

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

  • 13 Oct 26 −15

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

  • 4 Oct 26 +15

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

  • 1 Oct 26 −15

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Analysed pypi/openresearch-mcp@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo olanokhin/openresearch-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/olanokhin/openresearch-mcp/.github/workflows/release.yml@refs/tags/v0.2.1
Rekor log index 2120327886
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:0bfabca82f1340ec5bd64bf4846d5fe6c2482112013051c8f76ec072ef5f8d1c

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Vulnerabilities 115 findings
ID CVE Severity Vector Fix available
GHSA-23w6-3w8w-8484 CVE-2026-84310 medium yes
GHSA-248m-82v9-q6g6 CVE-2026-48156 low CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L yes
GHSA-2q4j-m29v-hq73 CVE-2026-24688 medium yes
GHSA-2rw7-x74f-jg35 CVE-2026-27628 low yes
GHSA-39mj-jf6j-2qj3 CVE-2026-113794 medium yes
GHSA-3crg-w4f6-42mx CVE-2026-40260 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-42gh-23hr-vphw CVE-2026-119206 high yes
GHSA-4f6g-68pf-7vhv CVE-2026-22691 low yes
GHSA-4pxv-j86v-mhcw CVE-2026-41313 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H yes
GHSA-4vqv-7265-gm2w CVE-2026-119207 high yes
GHSA-4xc4-762w-m6cg CVE-2026-22690 low yes
GHSA-52x6-gq3r-vpf4 CVE-2026-54530 medium yes
GHSA-55h5-xmcq-c37v CVE-2026-59937 medium yes
GHSA-5849-834g-hvw5 CVE-2026-119203 high yes
GHSA-5hgr-hg42-57jg CVE-2026-49460 medium yes
GHSA-5hx5-vpf9-5wcv CVE-2026-113786 low yes
GHSA-5jq2-8x83-x246 CVE-2026-102994 high yes
GHSA-5qjq-93h5-hrgp CVE-2026-59938 medium yes
GHSA-5xf7-4p34-54qr CVE-2026-59936 high yes
GHSA-62m5-6wh8-28x7 CVE-2026-119208 high yes
GHSA-6c7f-9265-g8fw CVE-2026-115572 high yes
GHSA-6vvc-x485-93v7 CVE-2026-113789 medium yes
GHSA-763m-79hh-57f2 CVE-2026-84311 medium yes
GHSA-7gw9-cf7v-778f CVE-2026-41312 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H yes
GHSA-7hfw-26vp-jp8m CVE-2025-55197 medium yes
GHSA-7mh2-4gg2-979f CVE-2026-113795 medium yes
GHSA-87mj-5ggw-8qc3 CVE-2026-33699 medium yes
GHSA-996q-pr4m-cvgq CVE-2026-27024 medium yes
GHSA-9m86-7pmv-2852 CVE-2026-28804 medium yes
GHSA-9mvc-8737-8j8h CVE-2026-27026 medium yes
GHSA-9mx8-4j7g-633p CVE-2026-113793 medium yes
GHSA-cgf9-327m-v77c CVE-2026-113791 medium yes
GHSA-cggf-277g-3q54 CVE-2026-119204 high yes
GHSA-cj93-chg6-vgv8 CVE-2026-48155 medium yes
GHSA-f2v5-7jq9-h8cg CVE-2026-28351 medium yes
GHSA-f54x-cmq8-qg57 CVE-2026-113790 medium yes
GHSA-fc8x-2rww-xw9m CVE-2026-82398 medium yes
GHSA-fp3f-mc75-235c CVE-2026-71870 medium yes
GHSA-fp3h-c4fm-7vvf CVE-2026-102995 high yes
GHSA-fwg2-594c-jp42 CVE-2026-71852 medium yes
GHSA-g867-7843-wf8q CVE-2026-59935 high yes
GHSA-g9cg-prrw-2r8q CVE-2026-102996 high yes
GHSA-g9xf-7f8q-9mcj CVE-2026-54651 medium yes
GHSA-gmh7-3g9r-mjh5 CVE-2026-115580 high yes
GHSA-hqmh-ppp3-xvm7 CVE-2026-31826 medium yes
GHSA-j543-4vmf-qm7v CVE-2026-49461 medium yes
GHSA-jfx9-29x2-rv3j CVE-2025-62708 medium yes
GHSA-jj6c-8h6c-hppx CVE-2026-41168 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-jm82-fx9c-mx94 CVE-2026-57204 medium yes
GHSA-jp53-mhqp-8xcg CVE-2026-84309 medium yes

Showing 50 of 115 vulnerabilities.

Background: What a vulnerability scan can and cannot prove →

Dependencies 31 packages
Packages resolved 31
Stale 2
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Install

How do I install the OpenResearch MCP server?

OpenResearch MCP runs locally as a PyPI package, launched with uvx openresearch-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · openresearch-mcp

# add to Claude Code
claude mcp add olanokhin-openresearch-mcp -- uvx openresearch-mcp
Common questions

What is the OpenResearch MCP server?

OpenResearch MCP is listed in the public MCP registry as io.github.olanokhin/openresearch-mcp. Zero-auth research MCP: web, academic, finance, news, weather, macro, social, SEC. No keys. This page covers its PyPI package (openresearch-mcp).

Is the OpenResearch MCP server safe to use?

OpenResearch MCP scores 30 out of 100 on VerifyMCP. We recorded 115 known advisories against it as of 4 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the OpenResearch MCP server still maintained?

OpenResearch MCP is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the OpenResearch MCP server under?

OpenResearch MCP declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.