# MOFi (pypi · mofi-tools)

Query MOF database survey metadata and connect a bounded MOFi scientific workspace.

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

- pypi · `mofi-tools`: 74/100 (this document), [markdown](https://verifymcp.io/servers/harrisonmo-mofi/mofi-tools.md), [page](https://verifymcp.io/servers/harrisonmo-mofi/mofi-tools)

## Channel facts

- Registry: `pypi`
- Package: `mofi-tools`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-24.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it.
  - 0 of 28 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to harrisonmo/MOFi).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 37/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add harrisonmo-mofi -- uvx mofi-tools
```

### Cursor

```json
{
  "mcpServers": {
    "harrisonmo-mofi": {
      "command": "uvx",
      "args": [
        "mofi-tools"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "harrisonmo-mofi": {
      "command": "uvx",
      "args": [
        "mofi-tools"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add harrisonmo-mofi -- uvx mofi-tools
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "harrisonmo-mofi": {
      "type": "local",
      "command": [
        "uvx",
        "mofi-tools"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add harrisonmo-mofi --command uvx --arg mofi-tools
```

### Hermes

```yaml
mcp_servers:
  harrisonmo-mofi:
    command: "uvx"
    args: ["mofi-tools"]
```

### Netclaw

```json
{
  "McpServers": {
    "harrisonmo-mofi": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "mofi-tools"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add harrisonmo-mofi -t stdio -c uvx -a mofi-tools
```

### Other

```json
{
  "mcpServers": {
    "harrisonmo-mofi": {
      "command": "uvx",
      "args": [
        "mofi-tools"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 74, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-22 (score 59)

First indexed and scored.

## MCP tools (2)

### `mof_database_catalog` (~331 tokens)

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.

Input parameters:

- `data_type_contains` (string|null, required): Case-insensitive substring of the data type column (for example 'Ads', 'Synth', 'Stability'), or null.
- `identifier` (string|null, required): Keep databases that index entries by this identifier scheme, or null.
- `method` (string|null, required): Keep databases whose source methods include this normalized method, or null.
- `name_contains` (string|null, required): Case-insensitive substring of the database name, or null.
- `required_fields` (array|null, required): Coverage flags that must all be Y, or null.
- `usable_link_only` (boolean|null, required): true keeps only rows whose link is a complete DOI or a website; null or false keeps all.

### `mofi_tool_catalog` (~34 tokens)

List available MOFi tools, unavailable engines, guidance and initial controller limits. Use science_budget_status for live scientific budgets.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/harrisonmo-mofi/mofi-tools#diagnostics

## Score history

- 2026-10-24: 74
- 2026-10-23: 74
- 2026-10-22: 59

## Common questions

### 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 24 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 24 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.

## Links

- PyPI project: https://pypi.org/project/mofi-tools/
- Socket report: https://socket.dev/pypi/package/mofi-tools
- Repository: https://github.com/harrisonmo/MOFi
- Changelog RSS feed: https://verifymcp.io/servers/harrisonmo-mofi/mofi-tools.xml
- Changelog JSON feed: https://verifymcp.io/servers/harrisonmo-mofi/mofi-tools.json
- HTML version of this page: https://verifymcp.io/servers/harrisonmo-mofi/mofi-tools