MOFi
PYPI · MOFI-TOOLS
Query MOF database survey metadata and connect a bounded MOFi scientific workspace.
Available components
Last scanned (23 hours ago)
Scores higher than 71% of PyPI servers
Category Health and Science
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to harrisonmo/MOFi). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability37
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 418 tokens (~139/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 23 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 22 Oct 26 59
First indexed and scored.
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 23 Oct 2026 · Analysed pypi/mofi-tools@0.1.0
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 | harrisonmo/MOFi |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/harrisonmo/MOFi/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 3401379964 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:47cf085a60fd92651ded1404889cd3cd95f03cc95a81a934a927a64d08204e1e |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
mof_database_catalog ~331
Filter a survey table of external MOF databases (CoRE MOF, QMOF, hMOF, CSD and others): identifier scheme, source method, data type, size, coverage flags (negative data, topology, LCD/PLD, ASA/VF/density, stability, synthesis/activation, API), formats, license and link with a link_status. Free; it does not count as a tool call and launches nothing. Use it to decide which database could supply structures, labels or negative data for a task and how to cross-link them (MOFid, Refcode). The table is unverified metadata, not evidence: it contains no structures or property values, its sizes and flags were not checked, and only link_status 'doi' or 'website' rows have a usable locator. Pass null for any filter you do not need; all given filters must hold.
| Name | Type | Req | Description |
|---|---|---|---|
| data_type_contains | string|null | yes | Case-insensitive substring of the data type column (for example 'Ads', 'Synth', 'Stability'), or null. |
| identifier | string|null | yes | Keep databases that index entries by this identifier scheme, or null. |
| method | string|null | yes | Keep databases whose source methods include this normalized method, or null. |
| name_contains | string|null | yes | Case-insensitive substring of the database name, or null. |
| required_fields | array|null | yes | Coverage flags that must all be Y, or null. |
| usable_link_only | boolean|null | yes | true keeps only rows whose link is a complete DOI or a website; null or false keeps all. |
No output schema declared.
No examples provided.
mofi_tool_catalog ~34
List available MOFi tools, unavailable engines, guidance and initial controller limits. Use science_budget_status for live scientific budgets.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the MOFi MCP server?
MOFi runs locally as a PyPI package, launched with uvx mofi-tools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mofi-tools
claude mcp add harrisonmo-mofi -- uvx mofi-tools
What is the MOFi MCP server?
MOFi is an MCP server listed in the public MCP registry as io.github.harrisonmo/mofi. Query MOF database survey metadata and connect a bounded MOFi scientific workspace. This page covers its PyPI package (mofi-tools).
Is the MOFi MCP server safe to use?
MOFi scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 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.
What tools does the MOFi MCP server expose?
MOFi exposes 2 tools: mof_database_catalog, mofi_tool_catalog. Their descriptions and schemas cost roughly 365 tokens of context every time the server is loaded.
Is the MOFi MCP server still maintained?
MOFi is still listed as active in the MCP registry. We last reached this channel on 23 October 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 MOFi MCP server under?
MOFi 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.