OpenResearch MCP
PYPI · OPENRESEARCH-MCP · SCANNED AUG 3
Zero-auth research MCP: web, academic, finance, news, weather, macro, social, SEC. No keys.
Available components
−5 this week
19 19 Trust /100
Trust breakdown (6 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 →
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 native-build step with no shell scripting around it. View diagnostics → Pass
- 3 of 39 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 25 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.Unverified
Capabilities0
- Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake.Unverified
Unverified: 4 categories
Categories scored 0 because our sandbox run of this package 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 →
Install
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
pypi · openresearch-mcp
# add to Claude Code
claude mcp add olanokhin-openresearch-mcp -- uvx openresearch-mcp
# add to Codex CLI
codex mcp add olanokhin-openresearch-mcp -- uvx openresearch-mcp
// opencode.json
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"olanokhin-openresearch-mcp": {
"type": "local",
"command": [
"uvx",
"openresearch-mcp"
],
"enabled": true
}
}
} # add to OpenClaw
openclaw mcp add olanokhin-openresearch-mcp --command uvx --arg openresearch-mcp
# ~/.hermes/config.yaml
mcp_servers:
olanokhin-openresearch-mcp:
command: "uvx"
args: ["openresearch-mcp"] // mcp.json
{
"mcpServers": {
"olanokhin-openresearch-mcp": {
"command": "uvx",
"args": [
"openresearch-mcp"
]
}
}
} 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.
- 3 Aug 26 0
- CVE-2026-28351 affects this package: high ▼ security
- CVE-2026-48155 affects this package: high ▼ security
- CVE-2026-54530 affects this package: high ▼ security
- CVE-2026-41168 affects this package: high ▼ security
- CVE-2025-62707 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-49461 affects this package: high ▼ security
- CVE-2026-27024 affects this package: high ▼ security
- CVE-2026-48735 affects this package: high ▼ security
- CVE-2026-57204 affects this package: high ▼ security
- CVE-2026-41314 affects this package: high ▼ security
- CVE-2025-62708 affects this package: high ▼ security
- CVE-2026-40260 affects this package: high ▼ security
- CVE-2026-27025 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-33699 affects this package: high ▼ security
- CVE-2026-48156 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-2025-66019 affects this package: high ▼ security
- CVE-2026-54651 affects this package: high ▼ security
- CVE-2026-22691 affects this package: high ▼ security
- CVE-2026-41313 affects this package: high ▼ security
- CVE-2026-59937 affects this package: high ▼ security
- CVE-2026-27026 affects this package: high ▼ security
- 2 Aug 26 +14
- CVE-2026-22690 affects this package: high ▼ security
- CVE-2025-55197 affects this package: high ▼ security
- CVE-2025-62707 affects this package: high ▼ security
- CVE-2026-41312 affects this package: high ▼ security
- CVE-2026-57204 affects this package: high ▼ security
- CVE-2026-41314 affects this package: high ▼ security
- CVE-2025-62708 affects this package: high ▼ security
- CVE-2026-40260 affects this package: high ▼ security
- CVE-2026-27025 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-33699 affects this package: high ▼ security
- CVE-2026-48156 affects this package: high ▼ security
- CVE-2026-54531 affects this package: high ▼ security
- CVE-2026-31826 affects this package: high ▼ security
- CVE-2026-59938 affects this package: high ▼ security
- CVE-2025-66019 affects this package: high ▼ security
- CVE-2026-54651 affects this package: high ▼ security
- CVE-2026-22691 affects this package: high ▼ security
- CVE-2026-41313 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-48155 affects this package: high ▼ security
- CVE-2026-28351 affects this package: high ▼ security
- CVE-2026-27024 affects this package: high ▼ security
- CVE-2026-49461 affects this package: high ▼ security
- CVE-2026-49460 affects this package: high ▼ security
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare. security
- The scripts that run when this package is installed changed: build_backend security
- Security disclosure: fail → unverified ▼ functional
- License: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → 0.97 ▲ functional
- Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
- Capabilities: Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake. functional
- Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
- Licence: Apache-2.0 functional
- 31 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 28 Jul 26 0
- Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
- Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
- 27 Jul 26 24
First indexed and scored.
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 3 Aug 2026 · Analysed pypi/[email protected]
Provenance none
Ecosystem: pypi · Outcome: none
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Vulnerabilities 65 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| 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-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-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-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-5hgr-hg42-57jg | CVE-2026-49460 | medium | yes | |
| GHSA-5qjq-93h5-hrgp | CVE-2026-59938 | medium | yes | |
| GHSA-5xf7-4p34-54qr | CVE-2026-59936 | high | 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-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-cj93-chg6-vgv8 | CVE-2026-48155 | medium | yes | |
| GHSA-f2v5-7jq9-h8cg | CVE-2026-28351 | medium | yes | |
| GHSA-g867-7843-wf8q | CVE-2026-59935 | high | yes | |
| GHSA-g9xf-7f8q-9mcj | CVE-2026-54651 | medium | 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-m2v9-299j-rv96 | CVE-2026-54531 | medium | yes | |
| GHSA-m449-cwjh-6pw7 | CVE-2025-66019 | medium | yes | |
| GHSA-qpxp-75px-xjcp | CVE-2026-33123 | medium | yes | |
| GHSA-vr63-x8vc-m265 | CVE-2025-62707 | medium | yes | |
| GHSA-wgvp-vg3v-2xq3 | CVE-2026-27025 | medium | yes | |
| GHSA-wjqc-6w8f-h24c | CVE-2026-48735 | medium | yes | |
| GHSA-x284-j5p8-9c5p | CVE-2026-41314 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H | yes |
| GHSA-x7hp-r3qg-r3cj | CVE-2026-27888 | medium | yes | |
| PYSEC-2026-1827 | CVE-2026-24688 | none | yes | |
| PYSEC-2026-1828 | CVE-2026-22691 | none | yes | |
| PYSEC-2026-1829 | CVE-2026-22690 | none | yes | |
| PYSEC-2026-1830 | CVE-2025-55197 | none | yes | |
| PYSEC-2026-1831 | CVE-2025-62708 | none | yes | |
| PYSEC-2026-1832 | CVE-2025-66019 | none | yes | |
| PYSEC-2026-1833 | CVE-2025-62707 | none | yes | |
| PYSEC-2026-3004 | CVE-2026-48156 | low | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L | yes |
| PYSEC-2026-3005 | CVE-2026-27628 | none | yes | |
| PYSEC-2026-3006 | CVE-2026-40260 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| PYSEC-2026-3007 | CVE-2026-41313 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H | yes |
| PYSEC-2026-3009 | CVE-2026-54530 | none | yes | |
| PYSEC-2026-3010 | CVE-2026-49460 | none | yes | |
| PYSEC-2026-3011 | CVE-2026-41312 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H | yes |
| PYSEC-2026-3012 | CVE-2026-33699 | none | yes |
Showing 50 of 65 vulnerabilities.
Dependencies 39 packages
39 packages in the resolved dependency tree · 3 stale.
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.
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.