SAS MCP Server (raedaldweik/SAS_MCP_Server_personal) is an MCP server listed on the M8ven Trust Index. It scores 69 out of 100, grade C. It declares 28 tools. No publisher has claimed this listing.

C
Limited view
69/100

SAS MCP Server

An MCP server for executing SAS code and managing SAS Viya resources, including data, CAS tables, models, and batch jobs, with support for multiple deployment modes and authentication options.

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

raedaldweik

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 →

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 5 credentials: VIYA_PASSWORD, VIYA_REFRESH_TOKEN, MCP_API_KEY, CLIENT_SECRET, MCP_SIGNING_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.
configMAX_SYNTHETIC_ROWS
configVIYA_USERNAMEUsing .env (set VIYA_ENDPOINT, , VIYA_PASSWORD):
🔐 secretVIYA_PASSWORDUsing .env (set VIYA_ENDPOINT, VIYA_USERNAME, ):
🔐 secretVIYA_REFRESH_TOKEN
🔐 secretMCP_API_KEY
configMCP_TRANSPORT
configSSL_VERIFY
configVIYA_ENDPOINTdocker run -e =https://your-viya-server.com -p 8134:8134 sas-mcp-server
configCLIENT_ID
🔐 secretCLIENT_SECRET
configHOST_PORT
🔐 secretMCP_SIGNING_KEY
configCOMPUTE_CONTEXT_NAME
configMAX_SAS_OUTPUT_CHARS
configMCP_BASE_URL
configSCOPE_ENFORCEtrue (default) blocks out-of-scope access; false only hides it from listings
configUSE_CASE_NAME/ USE_CASE_DESCRIPTION Identify the use case (returned by get_use_case)
configUSE_CASE_DESCRIPTIONUSE_CASE_NAME / Identify the use case (returned by get_use_case)
configALLOWED_TABLESCAS tables — table, caslib.table, or server.caslib.table
configALLOWED_MODELSModel IDs or names
configALLOWED_DECISIONSDecision / MAS-module IDs or names
configJOB_POLL_TIMEOUT
// 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

28/28 tools missing one or more hints — get_use_case (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); execute_sas_code (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); render_chart (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +25 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

26/28 tool handlers declare input schemas (93%)

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

Tool handlers catch errors

Only 2/28 tool handlers wrap calls in try/catch (7%)

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 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/raedaldweik/sas_mcp_server_personal)](https://m8ven.ai/mcp/raedaldweik/sas_mcp_server_personal)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 2271a4f46ae426b1493efdd0e8d9fd03175e345e
code hash: 37a351da1d6256c6ef6bc3b6257e83f901aab3143bd6f659be50708d2b45bcc5
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