love (balabm/love) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 8 tools. No publisher has claimed this listing.

C
Emerging
74/100
10 days ago

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

balabm

Source: github_code

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 →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 4 credentials: LOVE_API_KEY, BINGX_API_KEY, GITHUB_TOKEN, TELEGRAM_BOT_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// 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.
configEXPO_PUBLIC_API_URL
config_LOVE_DEPS_INSTALLED
configLOVE_AUTO_INSTALL_DEPS
configDAILY_BRIEF_TIME
configLOVE_SUPERVISOR_INTERVAL_SECSupervisor tick interval in seconds (5 min)
configLOVE_API_BASE_URL
🔐 secretLOVE_API_KEY
configOLLAMA_NUM_PREDICT
configOLLAMA_TIMEOUT
configCHAT_LLM_TIMEOUT_SEC
configTAILSCALE_IP
configBINGX_PAPER_MODE
🔐 secretBINGX_API_KEY
configGOOGLE_CREDENTIALS_PATH
configMS_CLIENT_ID
🔐 secretGITHUB_TOKEN
🔐 secretTELEGRAM_BOT_TOKEN
configNTFY_TOPIC
configOLLAMA_AUTO_FALLBACK
configOLLAMA_FORCE_HIGH_QUALITY
configLOVE_WORK_PROJECT
configLOVE_DOTNET_PROJECT
configLOVE_FLUTTER_PROJECT
configLOVE_AUTO_COMPUTER_CONTROL
configJARVIS_ENABLE_COMPUTER_USE
configLOVE_DEVICE_ID
configMAX_PROMPT_CHARS
configATE_GENERATE_INTERVAL_MINUTES
configATE_PAPER_TRADE_INTERVAL_MINUTES
configATE_MAX_STRATEGIES
configATE_TOP_COUNT
configLOVE_DAEMON_INTERVAL_MINSelf-improvement daemon interval (minutes)
configLOVE_GOAL_INTERVAL_SECGoal engine cycle interval (seconds)
configLOVE_WAVE_INTERVAL_HWave engine cycle interval (hours)
configLOVE_RESEARCH_INTERVAL_MINResearch engine cycle interval (minutes)
configLOVE_SELF_WORK_ON_TICKEnable self-diagnostics on each tick
configLOVE_INTELLIGENCE_TICKSRun intelligence loop every N ticks
configLOVE_MODEL_TIER
configPROCESSOR_ARCHITECTURE
configPROCESSOR_IDENTIFIER
// 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

8/8 tools missing one or more hints — love_chat (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); love_memory_search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); love_get_context (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +5 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.

Tool test coverage

Only 0/8 tools referenced in tests (0%)

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

Shell command execution

2 calls in production code run through a shell (love-agent/agent.js:153, love-agent/install-service.js:30)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

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 4 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/balabm/love)](https://m8ven.ai/mcp/balabm/love)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: c74fa4573f7e8b0540653c52b2ab75f6fa529aaa
code hash: 930ed0236e962c87e2ac019d295de266a398fddb84e9af7f3af9b93511a4a51e
verified: 9/2/2026, 8:03:49 PM
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