Skip to main content

Scion SDK

Scion SDK logo

Build secure connectors once. Serve, synchronize, and write back through one governed contract.
The typed source-integration boundary for MCP services and Medulla.

PyPI - Version Build Documentation GitHub Repo stars GitHub forks GitHub contributors GitHub license GitHub last commit (by committer) GitHub pull requests GitHub closed pull requests GitHub issues GitHub top language GitHub language count GitHub repo size GitHub repo file count (file type) PyPI - Downloads PyPI - License PyPI - Wheel PyPI - Implementation

Documentation · Capabilities · Interfaces · Status


Quick Start

Install Scion SDK as scion-sdk and import it as scion_sdk. The repository is scion-sdk; package, CLI and API identifiers remain unchanged.

Create a project and install the SDK:

uv init --bare demo-connector
cd demo-connector
uv add scion-sdk
uv sync
uv run connector-sync --help

The command prints the supervised synchronization options without opening a source session. Continue with the connector tutorial to build and run a one-file MCP connector, observe its health response, add declarative content, certify the live schema, and join source synchronization.

Overview

Scion SDK is the ecosystem's source-integration boundary. It turns vendor APIs and domain tools into secure MCP connectors, transports bounded source evidence into Medulla, indexes immutable repository snapshots, and applies authorized changes back to source systems.

Connector packages retain vendor behavior. The SDK owns transport, lifecycle, certification, and effect execution. Generated Medulla contracts own durable graph records, checkpoints, content identity, and receipts.

Key Capabilities

  • Build FastMCP servers with authentication, safe exposure, health, visibility, rate limits, change subscriptions, and consistent tool surfaces.
  • Publish skills, prompts, ontologies, SHACL shapes, and connector manifests as typed MCP content.
  • Extract bounded source pages and advance checkpoints only from matching durable Medulla receipts.
  • Import deterministic ConnectorPack archives without copying graph DTOs or digest algorithms into connector packages.
  • Stream authenticated immutable repository snapshots into the generated IndexRepository boundary without becoming a semantic writer.
  • Govern write-back through dry-run, authorization, source-version checks, idempotency, and uncertain-effect reconciliation.
  • Certify extension identity, live MCP schemas, pagination, and safety behavior before activation.

Documentation

Start with Build the operator's first connector, then choose the reference that matches the work:

Sibling authorities: Medulla owns durable graph state and generated contracts; Arbora owns authenticated runtime composition.

Architecture

Runtime architecture: people and clients enter through Arbora. Source systems flow through Scion SDK into Medulla.

Explore the live architecture

Boundary Owned here Owned elsewhere
Connector service MCP lifecycle, exposure policy, content capture, certification Vendor models and business semantics stay in the connector package.
Source ingest Discovery, bounded extraction, transport, receipt verification Medulla owns mapping, checkpoints, provenance, and commit receipts.
Repository ingest Authenticated snapshots, stable manifests, bounded object transport Medulla owns indexing, graph projection, and semantic interpretation.
Write-back Preview, source-version checks, apply, and reconciliation Medulla owns change sets, authorization decisions, and durable outcomes.
Runtime composition Typed ports and checked dependency requirements Arbora supplies authenticated identity, clients, and live authority.

The SDK depends directly on epistemic-graph>=2.27.6. Generated SourceIngest, ConnectorPack, IndexRepository, and WriteBack clients and models are the graph boundary; the SDK adds no parallel graph contract.

Contributing

Issues and pull requests are welcome. Follow AGENTS.md for ownership, isolation, and validation rules, and run the affected tests and public-surface gates before submitting a change.

License

Scion SDK is released under the MIT License.

Metadata

Release files for scion-sdk 0.6.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for scion-sdk 0.6.3
File Size Uploaded Provenance Actions
scion_sdk-0.6.3.tar.gz 1.1 MB Without provenance Details for scion_sdk-0.6.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for scion-sdk 0.6.3
File Interpreter ABI Platform Actions
scion_sdk-0.6.3-py3-none-any.whl Python 3 none any Details for scion_sdk-0.6.3-py3-none-any.whl

Total release size: 2.2 MB

Release files / scion_sdk-0.6.3.tar.gz

Download URL scion_sdk-0.6.3.tar.gz
Size 1.1 MB
Tags Source
SHA-256 checksum
How to use checksums
690550dedd489c9ad81b0c680c3e47319c393f6a7c20d6c59cc992035ebf010d
BLAKE2b-256 checksum
How to use checksums
21ed5b1e8eac5711b77a9c1cefd19433e111374acd8c98bb63663ce8f4f96e98
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.11.7 {"installer":{"name":"uv","version":"0.11.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / scion_sdk-0.6.3-py3-none-any.whl

Download URL scion_sdk-0.6.3-py3-none-any.whl
Size 1.1 MB
Tags Python 3
SHA-256 checksum
How to use checksums
94d7fec774a77cf4cd77fd8baee1e684c2923e5c8f444cc7bb78eb17b8da9677
BLAKE2b-256 checksum
How to use checksums
cb9417694d7a77632e7f9bef29c1f7df413c1b9f5a4541a82da68beb0345d09f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.11.7 {"installer":{"name":"uv","version":"0.11.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for scion-sdk 0.6.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page