← Index

SAS Viya

io.github.sassoftware/sas-mcp-serverv1.17.0Other

Execute SAS code and query Compute, CAS, and model APIs on SAS Viya via OAuth 2.0.

The current version, v1.17.0, was published to the official MCP registry on 2026-09-25. It is distributed as the Docker image ghcr.io/sassoftware/sas-mcp-server:1.17.0, filed under Other by this index, and declares 8 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using SAS Viya in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
REVIEWstatus: PARTIALfresh until 2026-10-03 00:38 UTC
screened 2026-08-12tier: scannedgranularity: description-levelsource: registry

Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.

mcpindex.integrity.descriptionpassINFO

evidence“Declared OAuth 2.0 precondition, no secret file access”via static_description

Limits of this verdict
  • - Semantic screen only - the deterministic conformance probe has not run on this server
  • - Confidence is reported but not yet calibrated (v1)
  • - Screen reads the tool description, not the live behavior
  • - advisory
  • - registry description only no input schema
  • - screen model 8b
  • - Still current: the description we screened is unchanged, re-checked against the registry
  • - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not

Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-09-26).

Contracts can change after screening, with no version bump. The gate pins SAS Viya’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Cite this record

People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.

Markdown
[Independent trust record for SAS Viya](https://mcpindex.ai/server/io-github-sassoftware-sas-mcp-server) - screening verdict, registry provenance, and contract drift monitoring.
HTML
<a href="https://mcpindex.ai/server/io-github-sassoftware-sas-mcp-server">Independent trust record for SAS Viya</a> - screening verdict, registry provenance, and contract drift monitoring.
Embed this badge

A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.

Markdown
[![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-sassoftware-sas-mcp-server)](https://mcpindex.ai/server/io-github-sassoftware-sas-mcp-server)
HTML
<a href="https://mcpindex.ai/server/io-github-sassoftware-sas-mcp-server"><img src="https://mcpindex.ai/api/v1/badge/io-github-sassoftware-sas-mcp-server" alt="mcpindex verdict" height="20" /></a>
Environment variables
VIYA_ENDPOINT
required

Base URL of your SAS Viya environment, e.g. https://viya.example.com. No trailing slash.

SSL_VERIFY

Set false only for a self-signed Viya certificate. Disables verification for the whole process, so prefer a trusted certificate.

CLIENT_ID

SASLogon OAuth client id used for the token refresh exchange.

COMPUTE_CONTEXT_NAME

Compute context that backs SAS code execution.

MCP_TIERS

Expose only some tool tiers, e.g. 0-4 or 0,1,7. Empty exposes all 92 tools. Tiers: 0 Compute, 1 Data Discovery, 2 Data Operations, 3 Reports, 4 Batch Jobs, 5 AutoML, 6 Models, 7 Decisioning, 8 Workbench, 9 Business Glossary.

MCP_READ_ONLY

Expose only tools that neither change server-side state nor cause server-side work (51 of 92). Composes with MCP_TIERS.

MCP_APPS

Register interactive views (MCP Apps) for the data, SAS log and glossary tools. Additive: text-only clients are unaffected. Set false to register none.

MCP_STATELESS_HTTP

Serve HTTP requests without an MCP session. Needed by clients that speak only the sessionless 2026-07-28 protocol revision (claude.ai custom connectors); the legacy handshake works either way.

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
15
installability
25
documentation
15
stability
10
Alternatives in Other