Giljo HQ (giljoai/giljo-hq) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 48 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
8 days ago

Giljo HQ

Context engineering for AI coding agents: product context, project missions, and 360 memory.

→ giljoai/giljo-hq· listed on glama

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

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

giljoai

Source: Glama · also listed on Official

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

GlamaOfficial

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 8 credentials: JWT_SECRET, GILJO_MCP_SECRET_KEY, SECRET_KEY, GILJO_PG_PASSWORD, POSTGRES_SUPERUSER_PASSWORD, POSTGRES_PASSWORD, DB_PASSWORD, DEFAULT_TENANT_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.
configGILJO_FRONTEND_PORT
configGILJO_MODE
configPLAYWRIGHT_TEST_BASE_URL
configVITE_FRONTEND_PORT
configLOG_LEVEL
🔐 secretJWT_SECRET
🔐 secretGILJO_MCP_SECRET_KEY
🔐 secretSECRET_KEY
configGILJO_WARM_DB_CONNECTIONS
configGILJO_NETWORK_MODE
🔐 secretGILJO_PG_PASSWORD
configGILJO_DB_NAME
configGILJO_UNATTENDED
configGILJO_INSTALL_DIR
configGILJO_FORCE_HTTP
🔐 secretPOSTGRES_SUPERUSER_PASSWORD
configGILJO_PORT
configGILJO_API_PORT
configSSL_CERT_FILE
configSSL_KEY_FILE
configPOSTGRES_HOST
configPOSTGRES_PORT
configPOSTGRES_DB
configPOSTGRES_USER
🔐 secretPOSTGRES_PASSWORD
configDB_HOST
configDB_PORT
configDB_NAME
configDB_USER
🔐 secretDB_PASSWORD
configDISPLAY
configWAYLAND_DISPLAY
configWSL_DISTRO_NAME
configGILJO_WS_BROKER
configGILJO_WEBSOCKET_BROKER
🔐 secretDEFAULT_TENANT_KEY
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deploySENTRY_AUTH_TOKEN
deploySENTRY_ORG
deploySENTRY_PROJECT
deployDATABASE_URL
deploySENTRY_DSN_FRONTEND
// 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

48/48 tools missing one or more hints — start_chain_run (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_thread (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); join_thread (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +45 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.

Secrets not logged

5 secret values sent to logger.info

Redact or omit secret values from log output.

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 3 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/giljoai/giljo-hq)](https://m8ven.ai/mcp/giljoai/giljo-hq)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 58f0631c59038a8f84d4f39b5480fdf1743ea228
code hash: 5867a8268b6fc41fa2d9abe24eb4cfadac9cd3586a7a380f75eab8ab5c9cd6fc
verified: 9/1/2026, 9:46:59 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