# io.github.andypgray/sliderule (nuget · SlideRule.Cli)

A .NET architecture checker that enforces one C# spec and renders the same rules for coding agents.

- Trust score: 90/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- nuget · `SlideRule.Cli`: 90/100 (this document), [markdown](https://verifymcp.io/servers/andypgray-sliderule/sliderule-cli.md), [page](https://verifymcp.io/servers/andypgray-sliderule/sliderule-cli)

## Channel facts

- Registry: `nuget`
- Package: `SlideRule.Cli`
- Version: `0.3.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to andypgray/sliderule).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 70/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3236 tokens (~647/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.andypgray/sliderule MCP server?

io.github.andypgray/sliderule runs locally as a NuGet package, launched with dnx SlideRule.Cli@0.3.0 --yes. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add andypgray-sliderule -- dnx SlideRule.Cli@0.3.0 --yes
```

### Cursor

```json
{
  "mcpServers": {
    "andypgray-sliderule": {
      "command": "dnx",
      "args": [
        "SlideRule.Cli@0.3.0",
        "--yes"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "andypgray-sliderule": {
      "command": "dnx",
      "args": [
        "SlideRule.Cli@0.3.0",
        "--yes"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add andypgray-sliderule -- dnx SlideRule.Cli@0.3.0 --yes
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "andypgray-sliderule": {
      "type": "local",
      "command": [
        "dnx",
        "SlideRule.Cli@0.3.0",
        "--yes"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  andypgray-sliderule:
    command: "dnx"
    args: ["SlideRule.Cli@0.3.0", "--yes"]
```

### Netclaw

```json
{
  "McpServers": {
    "andypgray-sliderule": {
      "Transport": "stdio",
      "Command": "dnx",
      "Arguments": [
        "SlideRule.Cli@0.3.0",
        "--yes"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "andypgray-sliderule": {
      "command": "dnx",
      "args": [
        "SlideRule.Cli@0.3.0",
        "--yes"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 90, +1)

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.63 → unverified
- [functional regression] Schema quality: 581 → 647
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional] MCP protocol: Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
- [functional] Package version: 0.2.1 → 0.3.0

### 2026-11-02 (score 89, +11)

- [security improvement] Provenance: unverified → pass
- [security] The attested source repository moved: andypgray/sliderule

### 2026-11-01 (score 78, −10)

- [security regression] Provenance: pass → unverified
- [security] The attested source repository moved: andypgray/sliderule

### 2026-10-30 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 86, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-26 (score 71, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Schema quality: excellent → good
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-25 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `arch_check` (~646 tokens)

Architecture Check

Run the architecture spec against the bound solution and return the JSON check report (schemaVersion 3): rules[] keyed by id, plus summary counts. Violations are data — a red rule is a finding, not an error. Narrow with grain (overview, skeleton or index) or rules (fewer rules); an over-budget report coarsens its own grain, as far as index, rather than being cut — and index lists every rule ID, which is what rules globs match. subjectTypes/subjectGeneratedTypes appear together on a rule whose subject contained generator output, pass or fail: how many types it swept and how many nobody wrote. Both absent means none were. Narrowing the rule with .Authored() removes them. If declared project files are missing, projects fail to load, or their NuGet packages did not resolve, the report still returns, stamped modelIncomplete: true and missingProjects/failedProjects/restoreFailedProjects — a verdict reached against a partial model; report that, never plain green. Under a .slnf solution filter, uncheckedProjects names the declared projects the run never checked — a clean report then covers a subset; say so. unsupportedProjects names the projects outside the model (not C#, Web Sites, unbuilt), each with its reason — no rule can be violated in one, so a clean report over a polyglot solution is not a clean solution either. multiTargetedProjects names the projects that compiled for several frameworks, each with the first framework its shared types' members and hierarchy follow (a type that framework does not declare follows the next that does); their references come from every framework, so a clean report over such a project covers one framework's members and hierarchy per type and every framework's references. staleSpec names a spec source that differs from the spec project's last build: the verdict is of the rules that build holds, so rebuild the spec project and check again.

Input parameters:

- `diffBase` (string): Git ref as one string, not an array; files changed since it that fall in a quarantined or cautioned scope raise a tripwire warning.
- `grain` (string): One grain as one string, not an array: full (the default), overview, skeleton or index, each coarser than the one before and never a narrower subject. overview elides each violation's sites (siteCoun…
- `rules` (string): Rule-ID globs as one string, not an array, semicolon-separated ('*' spans '/'). Only matching rules run, so rules[] and summary cover that subset alone. Matching no rule is an error listing the avail…

### `arch_status` (~216 tokens)

Architecture Status

Return the JSON migration burndown (schemaVersion 2): per-rule grandfathered/stale counts and promotion suggestions. If declared project files are missing, projects fail to load, or their NuGet packages did not resolve, the burndown still returns, stamped modelIncomplete: true and missingProjects/failedProjects/restoreFailedProjects — counts from a partial model; report that rather than quoting them as whole. Under a .slnf solution filter, uncheckedProjects names the declared projects the run never checked; they contribute no violations, so every count reads low. unsupportedProjects names the projects outside the model (not C#, Web Sites, unbuilt): no argument counts them, so their zero is not burndown. orphans lists baseline sections no rule in the spec names, such as a renamed rule's old section, and baseline files that could not be read. staleSpec names a spec source that differs from the spec project's last build, so the counts are of the rules that build holds; rebuild it and ask again.

### `arch_explain` (~304 tokens)

Architecture Explain

Return one rule's because, fix, citation, exemplar, posture payload, and linked prose as text. Given a type or a path instead of a rule ID, return which layers, rules and scopes claim each type, the rules that name it as an operand, the step that admitted it to each, and the rules whose selection reached it and then left it out: call it when a rule fires on a type you did not expect it to govern. Pass exactly one of ruleId, type and path. If projects fail to load or to restore, a type or path answer opens with a caveat naming them. A spec source that differs from the spec project's last build is named in a line above any answer: the answer is of the rules that build holds, so rebuild the spec project and ask again.

Input parameters:

- `path` (string): A file or directory to explain instead, absolute or solution-relative, as one string, not an array: every type declared there is explained. A path declaring no type answers successfully saying so.
- `ruleId` (string): A post-desugar rule ID as one string, not an array — e.g. layering/domain-independent or legacy/billing/containment.
- `type` (string): A type to explain instead, as one string, not an array: a full name as arch_check reports it, or a simple name, which explains every type wearing it. An unknown name is an error listing the closest f…

### `arch_context` (~260 tokens)

Architecture Context

Return the architecture scope card(s) covering a file or directory — a quarantined scope's dragons + sanctioned surface, a cautioned scope's dragons, or a layer's local rules — or a pointer line when none apply. If projects fail to load or to restore, the answer opens with a caveat naming them: cards from unloaded projects cannot be placed, and a rule about a package the restore never fetched was never measured, so treat a no-coverage answer as unproven there. A .slnf solution filter gets the same caveat for the declared projects it left unchecked: treat a no-coverage answer as unproven under them as well. A spec source that differs from the spec project's last build is named in a line above the answer: the cards are of the rules that build holds, so rebuild the spec project and ask again.

Input parameters:

- `path` (string, required): A file or directory path (absolute or solution-relative) as one string, not an array, to find architecture scope cards for. A path no card covers — including one the codebase does not contain yet — a…

### `arch_graph` (~1173 tokens)

Architecture Graph

Return the JSON codebase survey (schemaVersion 1): projects[] with namespace inventories, projectEdges[] (source/target, declared vs observed dependencies), and externalEdges[] grouped by namespace root. Every project the workspace loaded is here, which is wider than the solution: solutionMember false marks a passenger a ProjectReference dragged in, and an absent key means membership was unreadable. undeclaredProjectReferences (absent when empty) names the projects a project compiles against that no declared projectReferences entry reaches: its declared list is short, so trust its edges. projectEdges[] carry only references the code declares: where several projects declare one type, a project referencing its own copy is not an edge to the declarer the type was attributed to, nor is a reference one copy makes an edge from the others, and multiplyDeclaredTypes[] names those types with every declaring project and the one whose facts won — arch.Project() on any declarer selects them, with shape and member rules answering from the winner's facts (the key is absent when the solution has none). shadowedTypes[] is the other coverage key: a full name a project declares that a referenced assembly also supplies means two types, so a rule naming it reaches both while arch.Project() over the declaring project reaches only the declaration. generated qualifies the types count on a project and on each namespace (absent when zero): how many of them a generator emitted, which is what arch.Project() would sweep and .Authored() would drop. A namespace whose two counts are equal is wholly generator output — never make it a layer glob. targetFrameworks rides every project's row and names what it declares, normalized (a project predating the SDK reads net48); factsFollow rides only a multi-targeted one and names the first framework its shared types' members and hierarchy came from (a type it does not declare takes them from the next that does); their references come from every framework.…

Input parameters:

- `allowWorkspaceDiagnostics` (boolean): Survey the partial model even when some projects fail to load; otherwise the call returns an error naming what failed, because a survey missing whole projects is a wrong map, not a smaller one.
- `format` (string): One format as one string, not an array: json (the default), the survey document; or mermaid, the projects and their references as one Mermaid fence, as render --diagram draws them, with no grain. A f…
- `grain` (string): One grain as one string, not an array: full (the default), overview, skeleton or index, each coarser than the one before and never a narrower subject. overview elides every project's namespace invent…
- `projects` (string): Project-name globs as one string, not an array, semicolon-separated ('*' allowed). References in both directions are kept, so an edge can name a project outside the scope; under format mermaid only p…

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/andypgray-sliderule/sliderule-cli#diagnostics

## Score history

- 2026-11-04: 90
- 2026-11-03: 89
- 2026-11-02: 89
- 2026-11-01: 78
- 2026-10-31: 88
- 2026-10-30: 88
- 2026-10-29: 87
- 2026-10-28: 87
- 2026-10-27: 86
- 2026-10-26: 71
- 2026-10-25: 86
- 2026-10-24: 85
- 2026-10-23: 85
- 2026-10-22: 84
- 2026-10-21: 84
- 2026-10-20: 83
- 2026-10-19: 83
- 2026-10-18: 82
- 2026-10-17: 81
- 2026-10-16: 81
- 2026-10-15: 66
- 2026-10-14: 50
- 2026-10-13: 50
- 2026-10-12: 50

## Common questions

### What is the io.github.andypgray/sliderule MCP server?

io.github.andypgray/sliderule is an MCP server listed in the public MCP registry as io.github.andypgray/sliderule. A .NET architecture checker that enforces one C# spec and renders the same rules for coding agents. This page covers its NuGet package (SlideRule.Cli).

### Is the io.github.andypgray/sliderule MCP server safe to use?

io.github.andypgray/sliderule scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.andypgray/sliderule MCP server expose?

io.github.andypgray/sliderule exposes 5 tools: arch_check, arch_status, arch_explain, arch_context, arch_graph. Their descriptions and schemas cost roughly 2,599 tokens of context every time the server is loaded.

### Is the io.github.andypgray/sliderule MCP server still maintained?

io.github.andypgray/sliderule is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.andypgray/sliderule MCP server under?

io.github.andypgray/sliderule declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- NuGet package: https://www.nuget.org/packages/SlideRule.Cli
- Socket report: https://socket.dev/nuget/package/SlideRule.Cli
- Repository: https://github.com/andypgray/sliderule
- Changelog RSS feed: https://verifymcp.io/servers/andypgray-sliderule/sliderule-cli.xml
- Changelog JSON feed: https://verifymcp.io/servers/andypgray-sliderule/sliderule-cli.json
- HTML version of this page: https://verifymcp.io/servers/andypgray-sliderule/sliderule-cli