Horizon (hamzakammar/mcp-workspace) 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
Caution
74/100
2 months ago

Horizon

An MCP server that connects AI assistants to university D2L Brightspace and Piazza, enabling query of courses, grades, assignments, deadlines, files, and Piazza posts.

→ hamzakammar/mcp-workspace· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. 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

hamzakammar

Source: Glama

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

Glama

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

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: SUPABASE_SERVICE_ROLE_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 9 credentials: D2L_PASSWORD, D2L_TOKEN, EXPO_PUBLIC_SUPABASE_ANON_KEY, NOTION_CLIENT_SECRET, OPENAI_API_KEY, PIAZZA_PASSWORD, STUDY_MCP_TOKEN, SUPABASE_JWT_SECRET, SUPABASE_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.
configAPI_HOST
configAWS_EXECUTION_ENV
configAWS_REGION
configCOGNITO_CLIENT_ID
configCOGNITO_USER_POOL_ID
configD2L_COURSE_ID
configD2L_HOST
🔐 secretD2L_PASSWORD
🔐 secretD2L_TOKEN
configD2L_USERNAME
configDISPLAY
configEXPO_PUBLIC_API_BASE_URL
configEXPO_PUBLIC_PROJECT_ID
🔐 secretEXPO_PUBLIC_SUPABASE_ANON_KEY
configEXPO_PUBLIC_SUPABASE_URL
configKMS_KEY_ARN
configMCP_PORT
configMCP_TRANSPORT
configMCP_USER_IDSKIP_JWT_AUTH=1 =dev npm start
configNOTES_REPO_PATH
configNOTES_REPO_WEB_BASE
configNOTION_CLIENT_ID
🔐 secretNOTION_CLIENT_SECRET
configNOTION_REDIRECT_URI
🔐 secretOPENAI_API_KEYFill in SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY, , S3_BUCKET, etc.
🔐 secretPIAZZA_PASSWORD
configPIAZZA_USERNAME
configPLAYWRIGHT_CHROMIUM_EXECUTABLE_PATH
configPUBLIC_BASE_HOST
configREMOTE_DEBUG
configS3_BUCKETFill in SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY, OPENAI_API_KEY, , etc.
configS3_REGION
configSESSIONS_PATH
configSKIP_JWT_AUTH1 MCP_USER_ID=dev npm start
🔐 secretSTUDY_MCP_TOKEN
🔐 secretSUPABASE_JWT_SECRET
🔐 secretSUPABASE_KEY
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
deploySUPABASE_ANON_KEY
deploySUPABASE_SERVICE_ROLE_KEY
deploySUPABASE_URL
// 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

46/46 tools missing one or more hints — get_assignments (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_assignment (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_assignment_submissions (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +43 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 inputs are validated

Only 0/1 tool handlers declare input schemas (0%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

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

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

Tool test coverage

Only 10/46 tools referenced in tests (22%)

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

Secrets stay with their owner

1 secret/sensitive value flow into network calls (SUPABASE_SERVICE_ROLE_KEY → dynamic)

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Secrets not logged

2 secret values sent to console.log

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 7 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 Verified](https://m8ven.ai/badge/mcp/hamzakammar-mcp-workspace-knylay?variant=verified)](https://m8ven.ai/mcp/hamzakammar-mcp-workspace-knylay)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 7966d79e9c9af9a5c2b2f9ea9ded0dd4a052ed73
code hash: bd0ecba95cb64b9e30477dfe274211ef6566bf24ad8c00ce9b5475c755ee5f0d
verified: 6/22/2026, 12:23:58 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