ijfw (FerroxLabs/ijfw) is an MCP server listed on the M8ven Trust Index. It scores 89 out of 100, grade B. It declares 12 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
B
Emerging
89/100
7 days ago

ijfw

IJFW — It Just F*cking Works. Ferrox Labs' local-first infrastructure for AI coding agents: shared memory, smart routing, multi-AI cross-audits, disciplined workflow.

→ FerroxLabs/ijfw· listed on github_topic

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

FerroxLabs

Source: github_topic

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configCLAUDE_PROJECT_DIR
configIJFW_ALLOW_SEED_REGISTRY
configIJFW_AUDIT_TIMEOUT_SEC
configIJFW_AUTOLINK_BUDGET_USD
configIJFW_AUTOLINK_OFF
configIJFW_BRAIN_INJECT
configIJFW_COMPUTE_VM_ONLY
configIJFW_DASHBOARD_NO_CACHE
configIJFW_DASHBOARD_PORT
configIJFW_DEBUG_TRIDENT
configIJFW_DEDUP_OFF
configIJFW_DEDUP_THRESHOLD
configIJFW_DEDUP_WINDOW
configIJFW_FEDERATED_CACHE_MAX_BYTES
configIJFW_FEDERATED_CACHE_MAX_SOURCES
configIJFW_GRAPH_AUTO_INDEX
configIJFW_HOME
configIJFW_IDE_ID
configIJFW_INGEST_SCRUB
configIJFW_MINIMAL
configIJFW_NO_CROSS_PROJECT
configIJFW_PID_FILE
configIJFW_PORT_FILE
configIJFW_PROFILE_KILL
configIJFW_PROJECT_DIR
configIJFW_PROJECT_ROOT
configIJFW_SESSION_ID
configIJFW_SYNONYM_EXPAND
configIJFW_TENANT
configIJFW_VECTORS_MODEL
configIJFW_XAUDIT_LIVE
configIJFW_XAUDIT_LIVE_WITH
configSSH_AUTH_SOCK
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

12/12 tools missing one or more hints — ijfw_memory_recall (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); ijfw_memory_store (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); ijfw_memory_search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +9 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

Only 2/12 tools referenced in tests (17%)

Write tests that reference each tool by name so every tool has at least one test.

Domain consistency

npm scope @ijfw doesn't match GitHub owner ferroxlabs

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/ferroxlabs/ijfw)](https://m8ven.ai/mcp/ferroxlabs/ijfw)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: eda62f39f08b3028d824de1d806fe05c1402fd94
code hash: 90e78db5034ca31f8d990ecd9d679202d25b56f7450f022616a4a4b60e50f045
verified: 9/4/2026, 3:21:10 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client