# ResiMind (mcpb · resimind-0.16.0.mcpb)

Exact polynomial checks, sparse expansion and verified rule memory. Local MCP tools, no model key.

- Trust score: 48/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- mcpb · `resimind-0.16.0.mcpb`: 48/100 (this document), [markdown](https://verifymcp.io/servers/1105216375-alt-resimind/resimind.md), [page](https://verifymcp.io/servers/1105216375-alt-resimind/resimind)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/1105216375-alt/resimind/releases/download/v0.16.0/resimind-0.16.0.mcpb`
- Transport: `stdio`
- SHA-256: `5270994576b4a12467ce826cd7d678d4865c700df856e9b955b66f771979814d`

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

- **Supply Chain Security**: 12/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs were checked across the 27 of 27 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - Install-script risk not yet assessed.
  - 1 of 27 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 21 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 55/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 248 tokens (~49/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the ResiMind MCP server?

ResiMind ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 5270994576b4a12467ce826cd7d678d4865c700df856e9b955b66f771979814d; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/1105216375-alt/resimind/releases/download/v0.16.0/resimind-0.16.0.mcpb`
- SHA-256: `5270994576b4a12467ce826cd7d678d4865c700df856e9b955b66f771979814d`

### Verify on macOS / Linux

```bash
echo "5270994576b4a12467ce826cd7d678d4865c700df856e9b955b66f771979814d  resimind-0.16.0.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\resimind-0.16.0.mcpb).Hash -eq "5270994576b4a12467ce826cd7d678d4865c700df856e9b955b66f771979814d"
```

## 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-11-05 (score 48, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 47, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 46, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 45, +1)

- [security regression] Provenance: unverified → fail
- [functional improvement] Security disclosure: unverified → pass

### 2026-10-30 (score 44, 0)

- [security regression] Provenance: fail → unverified
- [functional regression] Security disclosure: pass → unverified

### 2026-10-28 (score 44, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 43, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 42, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `verify_identity` (~48 tokens)

Check whether two bounded rational polynomials are identically equal; return a coefficient mismatch when false.

Input parameters:

- `lhs` (string, required)
- `rhs` (string, required)
- `variables` (array, required)

### `expand_polynomial` (~38 tokens)

Expand a bounded rational polynomial into independently checked sparse terms without calling a model.

Input parameters:

- `expression` (string, required)
- `variables` (array, required)

### `learn_polynomial` (~43 tokens)

Solve an expansion and explicitly update process-local rule memory; compatible examples may yield a universally checked schema.

Input parameters:

- `expression` (string, required)
- `variables` (array, required)

### `recall_polynomial` (~44 tokens)

Try only verified rules in process-local memory, rechecking the application; no fallback computation or model call.

Input parameters:

- `expression` (string, required)
- `variables` (array, required)

### `list_rules` (~26 tokens)

List process-local verified rule statements and fingerprints; listing is not proof of any new task.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/1105216375-alt-resimind/resimind#diagnostics

## Score history

- 2026-11-05: 48
- 2026-11-04: 47
- 2026-11-03: 47
- 2026-11-02: 46
- 2026-11-01: 46
- 2026-10-31: 45
- 2026-10-30: 44
- 2026-10-29: 44
- 2026-10-28: 44
- 2026-10-27: 43
- 2026-10-26: 43
- 2026-10-25: 43
- 2026-10-24: 42
- 2026-10-23: 42
- 2026-10-22: 41
- 2026-10-21: 41
- 2026-10-20: 40
- 2026-10-19: 40
- 2026-10-18: 39
- 2026-10-17: 39
- 2026-10-16: 13
- 2026-10-15: 13
- 2026-10-14: 13

## Common questions

### What is the ResiMind MCP server?

ResiMind is an MCP server listed in the public MCP registry as io.github.1105216375-alt/resimind. Exact polynomial checks, sparse expansion and verified rule memory. Local MCP tools, no model key. This page covers its MCPB bundle (https://github.com/1105216375-alt/resimind/releases/download/v0.16.0/resimind-0.16.0.mcpb).

### Is the ResiMind MCP server safe to use?

ResiMind scores 48 out of 100 on VerifyMCP. 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 ResiMind MCP server expose?

ResiMind exposes 5 tools: verify_identity, expand_polynomial, learn_polynomial, recall_polynomial, list_rules. Their descriptions and schemas cost roughly 199 tokens of context every time the server is loaded.

### What licence is the ResiMind MCP server under?

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

## Links

- Repository: https://github.com/1105216375-alt/resimind
- Changelog RSS feed: https://verifymcp.io/servers/1105216375-alt-resimind/resimind.xml
- Changelog JSON feed: https://verifymcp.io/servers/1105216375-alt-resimind/resimind.json
- HTML version of this page: https://verifymcp.io/servers/1105216375-alt-resimind/resimind