io.github.mifactory-bot/mifactory-logic-verifier
NPM · @MIFACTORY-BOT/LOGIC-VERIFIER · SCANNED SEP 25
Verify AI agent reasoning and logic for errors and contradictions. Pay-per-use.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 33 of 96 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 203 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks 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 we can run it. How we score packages →
How do I install the io.github.mifactory-bot/mifactory-logic-verifier MCP server?
io.github.mifactory-bot/mifactory-logic-verifier runs locally as an npm package, launched with npx -y @mifactory-bot/logic-verifier. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mifactory-bot/logic-verifier
claude mcp add mifactory-bot-mifactory-logic-verifier -- npx -y @mifactory-bot/logic-verifier
{
"mcpServers": {
"mifactory-bot-mifactory-logic-verifier": {
"command": "npx",
"args": [
"-y",
"@mifactory-bot/logic-verifier"
]
}
}
} {
"servers": {
"mifactory-bot-mifactory-logic-verifier": {
"command": "npx",
"args": [
"-y",
"@mifactory-bot/logic-verifier"
]
}
}
} codex mcp add mifactory-bot-mifactory-logic-verifier -- npx -y @mifactory-bot/logic-verifier
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mifactory-bot-mifactory-logic-verifier": {
"type": "local",
"command": [
"npx",
"-y",
"@mifactory-bot/logic-verifier"
],
"enabled": true
}
}
} openclaw mcp add mifactory-bot-mifactory-logic-verifier --command npx --arg -y --arg @mifactory-bot/logic-verifier
mcp_servers:
mifactory-bot-mifactory-logic-verifier:
command: "npx"
args: ["-y", "@mifactory-bot/logic-verifier"] {
"McpServers": {
"mifactory-bot-mifactory-logic-verifier": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@mifactory-bot/logic-verifier"
]
}
}
} assistant mcp add mifactory-bot-mifactory-logic-verifier -t stdio -c npx -a -y @mifactory-bot/logic-verifier
{
"mcpServers": {
"mifactory-bot-mifactory-logic-verifier": {
"command": "npx",
"args": [
"-y",
"@mifactory-bot/logic-verifier"
]
}
}
} 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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 15 Sept 26 +2
- CVE-2026-82562 no longer affects this package ▲ security
- CVE-2026-82417 no longer affects this package ▲ security
- Known CVEs: fail → pass ▲ security
- 3 Sept 26 −2
- CVE-2026-82417 affects this package: medium ▼ security
- CVE-2026-82562 affects this package: medium ▼ security
- Known CVEs: pass → fail ▼ security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 8 Aug 26 0
- Known CVEs: partial → pass ▲ security
- Dependency health: partial → 0.82 functional
- 2 Aug 26 0
- Provenance: 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 could not run this package, so we have no schema to compare. security
- License: unverified → fail ▼ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- Schema quality: Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess. functional
- Capabilities: Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake. functional
- Tool coverage: Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess. functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 25 Sept 2026 · Analysed npm/@mifactory-bot/logic-verifier@1.0.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Deprecated | 1 |
| Stale | 32 |
| 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 →
Tools for package channels are captured by running the package in an isolated sandbox. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package.
What is the io.github.mifactory-bot/mifactory-logic-verifier MCP server?
io.github.mifactory-bot/mifactory-logic-verifier is an MCP server listed in the public MCP registry as io.github.mifactory-bot/mifactory-logic-verifier. Verify AI agent reasoning and logic for errors and contradictions. Pay-per-use. This page covers its npm package (@mifactory-bot/logic-verifier).
Is the io.github.mifactory-bot/mifactory-logic-verifier MCP server safe to use?
io.github.mifactory-bot/mifactory-logic-verifier scores 31 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. 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.
Is the io.github.mifactory-bot/mifactory-logic-verifier MCP server still maintained?
io.github.mifactory-bot/mifactory-logic-verifier is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.