MCP servers › io.github.MysterionRise › pubchem-finder
MCP server · registry snapshot 2026-11-03 · last checked 2026-11-03
io.github.MysterionRise/pubchem-finder
by MysterionRise · GitHub account (the registry's namespace rule)repository: same ownerSource ↗PyPI ↗Website ↗
Search PubChem by structure: a local similarity/substructure index, live PubChem data, RDKit tools — the publisher's description
Summary
io.github.MysterionRise/pubchem-finder is a local MCP server listed in the official MCP registry at version 2.2.0, under the namespace of the GitHub account MysterionRise. Its linked repository, github.com/MysterionRise/pubchem-finder, belongs to the same GitHub account.
Record checks
8 of 8 record checks met · 1 does not apply
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- met: Repository publishes a security policy (SECURITY.md)
- met: Package names its licence with a standard (SPDX) identifier
- met: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- met: No known critical or high advisory in the package or its dependencies
- #17,621 of 18,234 packages by monthly downloads, tied with 613 others
- Not ranked by stars: 9 stars (ranked from 10)
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself
Key facts
- Runs
- local package
- Transport
- standard input/output
- Your own values
- none declared (not a guarantee)
- Package
- PyPI · listed version current
- License
- MIT
- Dependencies
- no known high or critical advisories
- Repository
- public
- Last tested
- not tested
Tool list
Not read: It could be started, but has not been tested; we call no server's tools for anything we publish. This is our limit, not the server's. So there is no tool-list size and no result from the three APIs.
How fresh this is
- Live-tested
- no
- Last tested
- not tested
- Latest version
- 2.2.0, published 2026-11-02 (registry, as of the 2026-11-03 snapshot)
- First listed version
- 2026-10-26 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 3 versions listed, 2026-10-26 to 2026-11-02; 3 in the 90 days before the 2026-11-03 snapshot.(versions still listed in the registry only)
Most recent 3 versions
2.2.0· 2026-11-022.1.1· 2026-10-282.1.0· 2026-10-26
- Registry data
- snapshot 2026-11-03
- Package and repository
- checked 2026-11-03
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
Version 2.1.1 (published 2026-10-28) → 2.2.0 (published 2026-11-02), between the registry lists of 2026-11-02 and 2026-11-03.
The publisher’s GitHub release note for v2.2.0, published 2026-11-02.
Read the release note (the publisher’s text, shown as plain text)
### Added
- Local similarity and substructure search work on first use: until an index is built,
they search a built-in demo set of 1,932 FDA-approved drugs (PubChem's parent compounds
of what it links to Drugs@FDA, public domain), built into the data directory in about a
second on the first search. Results say so with `search_scope: "demo"` and a `note`
that points to PubChem's live searches and the build command; `index_status` reports
`search_scope` and `demo_compounds`. Once an index is built, searches use it without a
restart. `index build --demo` builds the demo index ahead of time and
`PUBCHEM_FINDER_DEMO=0` turns the fallback off. `scripts/build_demo_set.py` regenerates
the data.
- Three MCP prompts start common workflows by name (in Claude Code,
`/pubchem-finder:compound_dossier aspirin`): `compound_dossier` (a cited profile:
identity, structure, safety, pharmacology, bioassay targets), `find_analogues` (close
analogues grouped by scaffold and drawn with what changed, optional `threshold`) and
`triage_structures` (medicinal-chemistry triage of comma-separated SMILES, ranked).
- Two MCP resources: `pubchem://compound/{cid}` (a PubChem compound record as JSON; in
Claude Code, `@pubchem-finder:pubchem://compound/2244`) and `pubchem://index/status`.
Errors say what went wrong: an unknown CID is "not found", other failures name their
cause.
- The index manifest records an index format version. A pubchem-finder that meets an
index written in a newer format says so and what to do, instead of misreading it.
Indexes from 2.1 and earlier are format 1 and keep working.
### Changed
- When there is no local index, the message (and `index_status`) gives a command that
runs from any terminal: `uvx --python 3.14 pubchem-finder==<version> index build --limit 1
--with-substructure`, with `--home` when the server uses another data directory, and
what it costs (PubChem's first chunk is now a 323 MB download). Plugin and MCP users
have no `pubchem-finder` command on their PATH, so the old hint didn't run for them.
`index build` shows download progress.
- `similarity_search`, `substructure_search` and `pubchem_annotations` ask Claude Code to
show results of up to 100,000 characters inline (`anthropic/maxResultSizeChars`); by
default it saves results over 50,000 characters to a file instead, which large searches
can pass.
- The Claude plugin runs 2.1.1 and passes `--python=3.14` to uvx, like the other
documented launch commands, so plugin users get the tool annotations and stay off
Python 3.15.
### Fixed
- In-memory searches no longer risk failing with "Chunk N worker died: ...
GenericSearch(): incompatible function arguments" or crashing the server. FPSim2 0.7.4
updates the fingerprint arrays' reference counts unsafely when it splits a search
across threads, and can free them mid-search; searches now run in the calling thread.
Seen on Python 3.11, where it made long sessions and batch searches fail; reference
counts drift on 3.12 too.
- The declared minimum versions work again: Pillow 10.1 (`draw_molecules` needs
`ImageFont.load_default(size=...)`; with Pillow 10.0 it failed) and typer 0.16 (0.15
crashed on usage errors with click 8.2 or later). CI now runs the tests against the
lowest allowed version of every direct dependency.Source: the official MCP Registry list on 2026-11-02 and on 2026-11-03; release notes from the GitHub Releases API, checked 2026-11-03.
What it is
How do I add it to my client?
Config from the registry entry
- No config: the PyPI package declares runtime arguments (options for the runner itself), and the registry documentation gives no rule for where they go.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Can it be installed, and is it up to date?
Version pin · advisories
Listed version
- Registry lists
- 2.2.0
- Latest stable
- 2.2.0
- Status
- current
- Withdrawn
- no
Source: pypi.org · 2026-11-03. About the version the registry lists; a manual install may resolve to a different one.
Dependency advisories
Counted in the full dependency tree as resolved on 2026-11-03 (OSV.dev; each bar counts advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).
Integrity, provenance, license
- Integrity
- sha256-452ee4b06c51051d1…
- License
- MIT
Source: the package registry · 2026-11-03.
Usage
- Downloads
- 0 in the last month
Source: pypistats.org · 2026-11-03.
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Version 2.2.0 on PyPI | Exists and can be installed | matches | PyPI · 2026-11-03 |
| Repository github.com/MysterionRise/pubchem-finder | Opens publicly | matches | api.github.com · 2026-11-03 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.MysterionRise
- GitHub owner
- a personal account (MysterionRise)
- Repository
- github.com/MysterionRise/pubchem-finder
- Stars
- 9
- Repository age
- over a year
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- SECURITY.md
Source: the registry entry and api.github.com · 2026-11-03; security policy read from GitHub · 2026-11-03.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating8 of 8 record checks met · 1 does not apply
- #17,621 of 18,234 packages by monthly downloads, tied with 613 others
- Not ranked by stars: 9 stars (ranked from 10)
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
- MetPackage names its licence with a standard (SPDX) identifierMIT
- MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
- Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
- MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-03 (security policy 2026-11-03). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about io.github.MysterionRise/pubchem-finder
Answered from the data aboveWho publishes io.github.MysterionRise/pubchem-finder?
The registry ties the namespace io.github.MysterionRise to the GitHub account MysterionRise; only its owner can publish under it. Its linked repository, github.com/MysterionRise/pubchem-finder, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.
Is io.github.MysterionRise/pubchem-finder safe to install?
We do not rate servers as safe or unsafe. 8 of its 8 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Has io.github.MysterionRise/pubchem-finder been security tested?
No. It could be started, but has not been tested; we call no server's tools for anything we publish. This is our limit, not the server's.
Does io.github.MysterionRise/pubchem-finder publish a security policy?
Yes: its repository has a public security policy (github.com/mysterionrise/pubchem-finder/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.
Is the listed version current?
Yes. The registry lists 2.2.0, the latest stable release on PyPI.
Where is the source code of io.github.MysterionRise/pubchem-finder?
In github.com/MysterionRise/pubchem-finder, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
Has it been tested?
Feature #1It could be started, but has not been tested; we call no server's tools for anything we publish. This is our limit, not the server's. — our limit
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.MysterionRise/pubchem-finder: MCP server record.” Data checked 2026-11-03. https://protocolprobe.com/mcp/servers/io.github.MysterionRise/pubchem-finder
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.MysterionRise/pubchem-finder)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.
Write to hello@protocolprobe.com · corrections log · methodology