switch-trust-mcp 0.1.0__tar.gz

switch_trust_mcp-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or Derivative
+          Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright (c) 2026 SB Technology, Inc. dba SandboxAQ
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

switch_trust_mcp-0.1.0/PKG-INFO

@@ -0,0 +1,197 @@
+Metadata-Version: 2.4
+Name: switch-trust-mcp
+Version: 0.1.0
+Summary: Switch Trust platform MCP server: read-only AI-SPM issues, inventory, and remediation guidance for coding agents
+Author: SandboxAQ
+License: Apache-2.0
+Project-URL: Repository, https://github.com/sandbox-quantum/switch-trust-mcp
+Keywords: ai,mcp,security,ai-spm,switch-trust
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: httpx<1,>=0.28
+Requires-Dist: mcp<2,>=1.27
+Requires-Dist: attrs<27,>=25
+Requires-Dist: python-dateutil<3,>=2.9
+Provides-Extra: dev
+Requires-Dist: pytest<9,>=8; extra == "dev"
+Provides-Extra: audit
+Requires-Dist: pip-licenses>=5.0; extra == "audit"
+Requires-Dist: cyclonedx-bom>=6.0; extra == "audit"
+Requires-Dist: pip-audit>=2.7; extra == "audit"
+Requires-Dist: pip-tools==7.6.2; extra == "audit"
+Dynamic: license-file
+
+# switch-trust-mcp
+
+A local [MCP](https://modelcontextprotocol.io) server (stdio) that gives a coding
+agent read-only access to a Switch Trust backend's **AI-SPM issues, inventory, and
+remediation guidance** so it can fix the flagged code.
+
+It is a thin, authenticated REST client over the Switch Trust API — no scanner runs
+locally and no backend changes are required. Everything valuable (AI-reasoned
+findings, rule-based issues, public-asset vuln enrichment, remediation guidance)
+is already computed server-side and served over the existing API / static assets.
+
+## Install & run
+
+The idiomatic way is via the published wheel with `uvx` (no clone, no build step):
+
+```bash
+uvx switch-trust-mcp
+```
+
+## Configuration
+
+Set two environment variables:
+
+| Variable                 | Meaning                                                        |
+| ------------------------ | --------------------------------------------------------------- |
+| `SWITCH_TRUST_API_KEY`   | Switch Trust API key (`sk_...`).                                |
+| `SWITCH_TRUST_INSTANCE`  | Switch Trust instance base URL, e.g. `https://app.flintai.dev`. |
+
+The instance URL is validated against a fail-closed host allowlist before any
+credential is attached.
+
+The **tenant and workspace are auto-discovered** from the API key at startup —
+you do not configure any IDs. A key is pinned to exactly one tenant + active
+workspace by the backend.
+
+The API key is only ever sent in the `Authorization: ApiKey ...` header and is
+never logged.
+
+## Wiring into a coding agent
+
+Add to your MCP client config (Claude Code `.mcp.json`, Cursor, etc.):
+
+```jsonc
+{
+  "mcpServers": {
+    "switch-trust-mcp": {
+      "command": "uvx",
+      "args": ["switch-trust-mcp"],
+      "env": {
+        "SWITCH_TRUST_API_KEY": "sk_...",
+        "SWITCH_TRUST_INSTANCE": "https://app.flintai.dev"
+      }
+    }
+  }
+}
+```
+
+## Tools
+
+**Fix-focused**
+
+- `get_context` — show the resolved instance / tenant / workspace.
+- `list_issues(severity?, rule_id?, category?, search?, page_size?, cursor?)` —
+  list issues; paginated, `page_size` capped at 100.
+- `get_issue(issue_id, page_size?, cursor?)` — issue detail + assembled
+  rule-level remediation guidance + a page of affected objects; `objects` is
+  paginated the same way as `list_issues`.
+- `get_finding_detail(issue_id, object_id, detail_id?)` — per-finding file path,
+  code snippet, evidence, and inline remediation.
+- `find_issues_for_file(path, max_issues?)` — issues whose findings reference a
+  given working-tree file (client-side scan; matches by shared path suffix).
+  The scan follows pagination but is bounded — `max_issues` is capped at 500 and
+  the call at 300 backend requests — and returns a `scan` block reporting
+  `complete`, `issues_scanned`, `requests` and `errors`. **`complete: false`
+  means the caps were hit and the file may have findings this result omits**;
+  treat it as "unknown", not as "clean", and narrow the search with
+  `list_issues` filters instead.
+- `get_remediation_guidance(rule_name)` — rule-level remediation markdown.
+
+**Inventory browse**
+
+- `list_models | list_agents | list_tools | list_mcp_servers(name?, severity?, supplier?, library?, page_size?, cursor?)`
+- `get_model | get_agent | get_tool | get_mcp_server(asset_id)` — detail plus
+  attached issues, related assets, and code locations.
+
+**Guardrails & LLM-interaction analytics**
+
+- `list_guardrail_policies(search?, page?, page_size?)` — page-numbered (not
+  cursor-based); `page_size` capped at 100.
+- `get_guardrail_policy(policy_id)` — policy detail: name, description,
+  user/assistant detector configuration.
+- `get_guardrail_interaction_counts | get_guardrail_outcomes | get_guardrail_categories(agent_id?)`
+  — guardrail-decision dashboards across LLM interactions, optionally scoped
+  to one agent.
+- `list_llm_interactions(search?, agent_id?, page_size?, cursor?)` — prompt/
+  response pairs with guardrail outcomes; rows are trimmed (long text
+  truncated, per-turn events omitted) for context budget. `page_size` capped
+  at 100.
+- `get_interaction(interaction_id)` — one interaction's full detail.
+- `list_llm_sessions(agent_id, sort?, sort_dir?, page_size?, cursor?)` —
+  grouped conversation turns for one agent (required). `page_size` capped at 100.
+- `get_llm_session(session_id)` — one session's aggregate cost/tokens/turns
+  plus the full per-turn list.
+
+**Red-teaming / eval**
+
+- `list_evaluations(search?, approach?, page?, page_size?, order?)` —
+  evaluation definitions (probes/metrics), including red-teaming adversarial
+  probes; `approach` is `probe` or `metric`. Page-numbered; `page_size`
+  capped at 100.
+- `get_evaluation(evaluation_id)` — full definition detail, including
+  `attack_techniques` / `adversarial_goals` / `num_prompts` / `max_turns` for
+  adversarial-probe evaluations.
+- `list_agent_evaluations(agent_id?, evaluation_id?, search?, page?, page_size?, order?)`
+  — agent↔evaluation assignments, each with `latest_run_status`/`progress`/
+  `summary` and a `score_trend` (last 5 scores). Page-numbered; `page_size`
+  capped at 100.
+- `get_agent_evaluation(agent_evaluation_id)` — one assignment's full detail.
+- `get_agent_evaluation_summary(agent_id)` — one agent's evaluation health
+  rollup: health score, per-category OWASP coverage, and score trend.
+- `list_evaluation_runs(evaluation_id?, agent_evaluation_id?, page?, page_size?, order?)`
+  — runs; `status` is `queued`/`running`/`finished`/`error`. Page-numbered;
+  `page_size` capped at 100.
+- `get_evaluation_run(evaluation_run_id)` — one run's detail.
+- `list_evaluation_run_results(evaluation_run_id, page?, page_size?, order?)`
+  — one run's per-prompt results; `status` is `passed`/`failed`/`error`/
+  `scored`. There is no single-result detail endpoint, so `conversation`
+  transcripts are trimmed rather than dropped: every turn is kept but each
+  turn's text is truncated to 300 characters. Page-numbered; `page_size`
+  capped at 100.
+- `get_agent_endpoint(agent_id)` — an agent's red-teaming target-endpoint
+  config (`endpoint_url`, `endpoint_auth_type`, `model_type`, `config`);
+  secrets are redacted server-side and always come back empty.
+
+## Remediation guidance
+
+Rule-level remediation markdown has **no dedicated API** — it is served by the
+instance's web server as static assets at `{instance}/assets/docs-remediations/…`
+(the same origin and files the web UI reads). This server fetches them at runtime
+over HTTP through the shared client and caches them per session; nothing is
+bundled into the package. When a rule has no docs (or the assets origin is
+unreachable), fall back to the per-finding `remediation` text from
+`get_finding_detail`.
+
+For offline development or tests, set `SWITCH_TRUST_REMEDIATION_DIR` to a local directory
+laid out like the assets (`rule-name-to-remediation-folder-map.json` + per-rule
+folders); the loader then reads from disk and never touches the network.
+
+## Development
+
+- Layout: `src/switch_trust_mcp/` (`src/` layout), tests under `test/`.
+- Editable install: `pip install -e '.[dev]'`, then run `switch-trust-mcp`.
+- Docs are fetched from your instance at runtime; for offline work point
+  `SWITCH_TRUST_REMEDIATION_DIR` at a local copy of the docs directory.
+
+## Tests
+
+```bash
+pytest
+```
+
+Tests are hermetic (httpx `MockTransport` for the client and the remediation-docs
+fetch, a fake client + `SWITCH_TRUST_REMEDIATION_DIR` for the tools), so they need no
+network or live backend.

switch_trust_mcp-0.1.0/README.md

@@ -0,0 +1,164 @@
+# switch-trust-mcp
+
+A local [MCP](https://modelcontextprotocol.io) server (stdio) that gives a coding
+agent read-only access to a Switch Trust backend's **AI-SPM issues, inventory, and
+remediation guidance** so it can fix the flagged code.
+
+It is a thin, authenticated REST client over the Switch Trust API — no scanner runs
+locally and no backend changes are required. Everything valuable (AI-reasoned
+findings, rule-based issues, public-asset vuln enrichment, remediation guidance)
+is already computed server-side and served over the existing API / static assets.
+
+## Install & run
+
+The idiomatic way is via the published wheel with `uvx` (no clone, no build step):
+
+```bash
+uvx switch-trust-mcp
+```
+
+## Configuration
+
+Set two environment variables:
+
+| Variable                 | Meaning                                                        |
+| ------------------------ | --------------------------------------------------------------- |
+| `SWITCH_TRUST_API_KEY`   | Switch Trust API key (`sk_...`).                                |
+| `SWITCH_TRUST_INSTANCE`  | Switch Trust instance base URL, e.g. `https://app.flintai.dev`. |
+
+The instance URL is validated against a fail-closed host allowlist before any
+credential is attached.
+
+The **tenant and workspace are auto-discovered** from the API key at startup —
+you do not configure any IDs. A key is pinned to exactly one tenant + active
+workspace by the backend.
+
+The API key is only ever sent in the `Authorization: ApiKey ...` header and is
+never logged.
+
+## Wiring into a coding agent
+
+Add to your MCP client config (Claude Code `.mcp.json`, Cursor, etc.):
+
+```jsonc
+{
+  "mcpServers": {
+    "switch-trust-mcp": {
+      "command": "uvx",
+      "args": ["switch-trust-mcp"],
+      "env": {
+        "SWITCH_TRUST_API_KEY": "sk_...",
+        "SWITCH_TRUST_INSTANCE": "https://app.flintai.dev"
+      }
+    }
+  }
+}
+```
+
+## Tools
+
+**Fix-focused**
+
+- `get_context` — show the resolved instance / tenant / workspace.
+- `list_issues(severity?, rule_id?, category?, search?, page_size?, cursor?)` —
+  list issues; paginated, `page_size` capped at 100.
+- `get_issue(issue_id, page_size?, cursor?)` — issue detail + assembled
+  rule-level remediation guidance + a page of affected objects; `objects` is
+  paginated the same way as `list_issues`.
+- `get_finding_detail(issue_id, object_id, detail_id?)` — per-finding file path,
+  code snippet, evidence, and inline remediation.
+- `find_issues_for_file(path, max_issues?)` — issues whose findings reference a
+  given working-tree file (client-side scan; matches by shared path suffix).
+  The scan follows pagination but is bounded — `max_issues` is capped at 500 and
+  the call at 300 backend requests — and returns a `scan` block reporting
+  `complete`, `issues_scanned`, `requests` and `errors`. **`complete: false`
+  means the caps were hit and the file may have findings this result omits**;
+  treat it as "unknown", not as "clean", and narrow the search with
+  `list_issues` filters instead.
+- `get_remediation_guidance(rule_name)` — rule-level remediation markdown.
+
+**Inventory browse**
+
+- `list_models | list_agents | list_tools | list_mcp_servers(name?, severity?, supplier?, library?, page_size?, cursor?)`
+- `get_model | get_agent | get_tool | get_mcp_server(asset_id)` — detail plus
+  attached issues, related assets, and code locations.
+
+**Guardrails & LLM-interaction analytics**
+
+- `list_guardrail_policies(search?, page?, page_size?)` — page-numbered (not
+  cursor-based); `page_size` capped at 100.
+- `get_guardrail_policy(policy_id)` — policy detail: name, description,
+  user/assistant detector configuration.
+- `get_guardrail_interaction_counts | get_guardrail_outcomes | get_guardrail_categories(agent_id?)`
+  — guardrail-decision dashboards across LLM interactions, optionally scoped
+  to one agent.
+- `list_llm_interactions(search?, agent_id?, page_size?, cursor?)` — prompt/
+  response pairs with guardrail outcomes; rows are trimmed (long text
+  truncated, per-turn events omitted) for context budget. `page_size` capped
+  at 100.
+- `get_interaction(interaction_id)` — one interaction's full detail.
+- `list_llm_sessions(agent_id, sort?, sort_dir?, page_size?, cursor?)` —
+  grouped conversation turns for one agent (required). `page_size` capped at 100.
+- `get_llm_session(session_id)` — one session's aggregate cost/tokens/turns
+  plus the full per-turn list.
+
+**Red-teaming / eval**
+
+- `list_evaluations(search?, approach?, page?, page_size?, order?)` —
+  evaluation definitions (probes/metrics), including red-teaming adversarial
+  probes; `approach` is `probe` or `metric`. Page-numbered; `page_size`
+  capped at 100.
+- `get_evaluation(evaluation_id)` — full definition detail, including
+  `attack_techniques` / `adversarial_goals` / `num_prompts` / `max_turns` for
+  adversarial-probe evaluations.
+- `list_agent_evaluations(agent_id?, evaluation_id?, search?, page?, page_size?, order?)`
+  — agent↔evaluation assignments, each with `latest_run_status`/`progress`/
+  `summary` and a `score_trend` (last 5 scores). Page-numbered; `page_size`
+  capped at 100.
+- `get_agent_evaluation(agent_evaluation_id)` — one assignment's full detail.
+- `get_agent_evaluation_summary(agent_id)` — one agent's evaluation health
+  rollup: health score, per-category OWASP coverage, and score trend.
+- `list_evaluation_runs(evaluation_id?, agent_evaluation_id?, page?, page_size?, order?)`
+  — runs; `status` is `queued`/`running`/`finished`/`error`. Page-numbered;
+  `page_size` capped at 100.
+- `get_evaluation_run(evaluation_run_id)` — one run's detail.
+- `list_evaluation_run_results(evaluation_run_id, page?, page_size?, order?)`
+  — one run's per-prompt results; `status` is `passed`/`failed`/`error`/
+  `scored`. There is no single-result detail endpoint, so `conversation`
+  transcripts are trimmed rather than dropped: every turn is kept but each
+  turn's text is truncated to 300 characters. Page-numbered; `page_size`
+  capped at 100.
+- `get_agent_endpoint(agent_id)` — an agent's red-teaming target-endpoint
+  config (`endpoint_url`, `endpoint_auth_type`, `model_type`, `config`);
+  secrets are redacted server-side and always come back empty.
+
+## Remediation guidance
+
+Rule-level remediation markdown has **no dedicated API** — it is served by the
+instance's web server as static assets at `{instance}/assets/docs-remediations/…`
+(the same origin and files the web UI reads). This server fetches them at runtime
+over HTTP through the shared client and caches them per session; nothing is
+bundled into the package. When a rule has no docs (or the assets origin is
+unreachable), fall back to the per-finding `remediation` text from
+`get_finding_detail`.
+
+For offline development or tests, set `SWITCH_TRUST_REMEDIATION_DIR` to a local directory
+laid out like the assets (`rule-name-to-remediation-folder-map.json` + per-rule
+folders); the loader then reads from disk and never touches the network.
+
+## Development
+
+- Layout: `src/switch_trust_mcp/` (`src/` layout), tests under `test/`.
+- Editable install: `pip install -e '.[dev]'`, then run `switch-trust-mcp`.
+- Docs are fetched from your instance at runtime; for offline work point
+  `SWITCH_TRUST_REMEDIATION_DIR` at a local copy of the docs directory.
+
+## Tests
+
+```bash
+pytest
+```
+
+Tests are hermetic (httpx `MockTransport` for the client and the remediation-docs
+fetch, a fake client + `SWITCH_TRUST_REMEDIATION_DIR` for the tools), so they need no
+network or live backend.

switch_trust_mcp-0.1.0/pyproject.toml

@@ -0,0 +1,84 @@
+[build-system]
+requires = ["setuptools>=68.0", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "switch-trust-mcp"
+version = "0.1.0"
+description = "Switch Trust platform MCP server: read-only AI-SPM issues, inventory, and remediation guidance for coding agents"
+readme = "README.md"
+# 3.11+: the generated OpenAPI clients import ``typing.Self`` (new in 3.11) at
+# module top with no ``typing_extensions`` fallback, so 3.10 would ImportError
+# on first import.
+requires-python = ">=3.11"
+license = { text = "Apache-2.0" }
+authors = [
+  { name = "SandboxAQ" },
+]
+keywords = ["ai", "mcp", "security", "ai-spm", "switch-trust"]
+classifiers = [
+  "Development Status :: 3 - Alpha",
+  "Intended Audience :: Developers",
+  "License :: OSI Approved :: Apache Software License",
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3.11",
+  "Programming Language :: Python :: 3.12",
+  "Programming Language :: Python :: 3.13",
+  "Topic :: Software Development :: Libraries :: Python Modules",
+  "Typing :: Typed",
+]
+dependencies = [
+  "httpx>=0.28,<1",
+  "mcp>=1.27,<2",
+  # Runtime for the generated OpenAPI clients (switch_trust_mcp._platform_api /
+  # _auth_api): attrs models and date parsing.
+  "attrs>=25,<27",
+  "python-dateutil>=2.9,<3",
+]
+
+[project.optional-dependencies]
+dev = ["pytest>=8,<9"]
+# Release-audit tooling: `make release-audit` in the public repo. gitleaks is a
+# Go binary and is installed separately.
+audit = [
+  "pip-licenses>=5.0",
+  "cyclonedx-bom>=6.0",
+  "pip-audit>=2.7",
+  # Exact pin, not >= or ~=: different pip-compile patch versions have been
+  # observed changing requirements.lock's header comment / `# via` ordering
+  # with zero actual dependency change, which the sync's byte-exact diff
+  # treats as staleness (see sync/README.md, "Dependency lockfile"). Loosening
+  # this to ~=7.6 broke the next release's sync when 7.6.2 shipped.
+  "pip-tools==7.6.2",
+]
+
+[project.scripts]
+switch-trust-mcp = "switch_trust_mcp.server:main"
+
+[project.urls]
+Repository = "https://github.com/sandbox-quantum/switch-trust-mcp"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+switch_trust_mcp = ["py.typed", "remediation_procedure.md"]
+"switch_trust_mcp._platform_api" = ["py.typed"]
+"switch_trust_mcp._auth_api" = ["py.typed"]
+
+[tool.pytest.ini_options]
+testpaths = ["test"]
+
+[tool.mypy]
+strict = true
+warn_return_any = true
+warn_unused_configs = true
+
+# Ruff is configured repo-wide in //ruff.toml. Do not add a [tool.ruff] section
+# here: ruff resolves config per-file by walking up from the file, so a section
+# in this pyproject would shadow the root config for this whole subtree. A
+# line-length = 120 section here did exactly that, leaving `ruff format` and
+# `ruff check` disagreeing about this package.
+#
+# Ruff's own default line-length is 88, the same as //ruff.toml, so the synced
+# public repo keeps formatting these files identically with no config at all.

switch_trust_mcp-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

switch_trust_mcp-0.1.0/src/switch_trust_mcp/__init__.py

@@ -0,0 +1,18 @@
+"""switch-trust-mcp: the Switch Trust platform MCP server for coding agents.
+
+v1 exposes read-only AI-SPM issues, inventory, and remediation guidance from a
+Switch Trust instance. The package is named for the platform (not AI-SPM
+specifically) so it can grow to cover additional Switch Trust product domains
+over time.
+"""
+
+from __future__ import annotations
+
+from importlib.metadata import PackageNotFoundError, version
+
+try:
+    __version__ = version("switch-trust-mcp")
+except PackageNotFoundError:  # not installed (e.g. running from a source checkout)
+    __version__ = "0.0.0-dev"
+
+__all__ = ["__version__"]