spl-backend (Titipon5013/spl-backend) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Limited view
71/100
29 days ago

spl-backend

→ Titipon5013/spl-backend· listed on github_code

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

How we verified

Code 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

Titipon5013

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 →

⚡ 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.
✅
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 9 credentials: MQTT_PASSWORD, SECRET_KEY, GOOGLE_CLIENT_SECRET, POSTGRES_PASSWORD, AWS_ACCESS_KEY, AWS_SECRET_ACCESS_KEY, LINE_CHANNEL_SECRET, LINE_CHANNEL_ACCESS_TOKEN, GEMINI_API_KEY
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.
configMCP_ALLOWED_HOSTS
configMCP_HTTP_ENABLED
configSQL_ECHO
configMQTT_BROKER_HOST
configMQTT_USER
🔐 secretMQTT_PASSWORD
configMCP_RATE_LIMIT_PER_MINUTE
configMCP_API_TOKENS/mcp/: The MCP server endpoint for AI agents. Requires a bearer token from .
configOPENCV_FFMPEG_READ_ATTEMPTS
🔐 secretSECRET_KEY
configGOOGLE_CLIENT_ID
🔐 secretGOOGLE_CLIENT_SECRET
configFRONTEND_URL
configPOSTGRES_USER
🔐 secretPOSTGRES_PASSWORD
configPOSTGRES_DB
configMQTT_CLIENT
🔐 secretAWS_ACCESS_KEY
🔐 secretAWS_SECRET_ACCESS_KEY
configS3_REGION
configS3_BUCKET
configCLOUDFRONT_URL
🔐 secretLINE_CHANNEL_SECRET
🔐 secretLINE_CHANNEL_ACCESS_TOKEN
configANOMALY_STUCK_SLOT_HOURS
configANOMALY_PIPELINE_INACTIVE_MINUTES
configANOMALY_DEVICE_OFFLINE_SECONDS
configLINE_BOT_URL
configEMAIL_DISABLED
configWEEKLY_REPORT_DAY
configWEEKLY_REPORT_HOUR
configWEEKLY_REPORT_MINUTE
configANOMALY_SCAN_INTERVAL_MINUTES
🔐 secretGEMINI_API_KEY
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
deploySMTP_HOST
deploySMTP_PORT
deploySMTP_USER
deploySMTP_PASSWORD
deploySMTP_FROM
// 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 — get_live_occupancy (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); check_slot_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); find_available_slots (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 handlers catch errors

Only 0/8 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

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/titipon5013-spl-backend-1wcgzb)](https://m8ven.ai/mcp/titipon5013-spl-backend-1wcgzb)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 66ef347286ba37949b453aa1c23826732c576369
code hash: 9337652d425ec051bf1a0de56ec91dbef65771b7523300e0551e053fdcaf4f57
verified: 8/8/2026, 8:36:34 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