SDK: DePasqualeOrg/swift-mcp
Version: 1.0.0
Assessed: 2026-03-01
Requested tier: Tier 1
Tool: @modelcontextprotocol/conformance tier-check

Summary

Detail

1. Server Conformance – 30/30 (100%)

Tested against spec version 2025-11-25.

2. Client Conformance – 18/18 (100%)

18/18 scored scenarios pass for spec version 2025-11-25. Two 2025-03-26-only backward-compatibility auth scenarios (auth/2025-03-26-oauth-metadata-backcompat, auth/2025-03-26-oauth-endpoint-fallback) are excluded because the SDK targets 2025-11-25 and does not claim legacy support.

3. Issue Triage

All issues triaged within 2 business days. Open untriaged issues (should show 0).

4. P0 Resolution – 0 open

No P0 issues have been filed.

5. Stable Release – 1.0.0

SemVer with breaking change policy documented in Update Policy.

6. Spec Tracking

This SDK's first release (0.1.0, 2026-01-07) was 43 days after the spec 2025-11-25 tag (2025-11-25). This gap reflects the fact that this is a new SDK that was forked from the unmaintained Swift SDK in late December 2025. It fully implements the 2025-11-25 spec and will track future spec versions promptly. For these reasons, I request that this not disqualify this SDK from Tier 1 status.

7. Documentation

Comprehensive documentation with code examples covering all MCP features across server, client, and transport guides.

8. Dependency Policy

Published as Update Policy in the readme. SemVer with documented breaking change and support policy.

9. Roadmap

Published as Roadmap in the readme.

Notes on tier-check

While preparing this assessment, I found and fixed two issues in the conformance tool's tier-check:

• #175: tier-check uses a relative dist/index.js path when shelling out to run conformance tests, which fails when invoked via npx (producing 0% scores)
• #176: tier-check has no way to exclude legacy backward-compatibility scenarios, so SDKs targeting 2025-11-25 are scored against 2025-03-26-only tests they shouldn't need to pass

Reproduce

# Terminal 1: Clone, build, and start the conformance server
cd /tmp
git clone https://github.com/DePasqualeOrg/swift-mcp.git
cd swift-mcp/Examples/ConformanceTests
swift build --product ConformanceServer --product ConformanceClient
swift run ConformanceServer --port 8080

# Terminal 2: Run tier-check
cd /tmp
git clone https://github.com/modelcontextprotocol/conformance.git
cd conformance && npm install && npm run build

CLIENT_BIN="$(swift build --show-bin-path --package-path /tmp/swift-mcp/Examples/ConformanceTests)/ConformanceClient"

npm run --silent tier-check -- \
  --repo DePasqualeOrg/swift-mcp \
  --conformance-server-url http://localhost:8080/mcp \
  --client-cmd "$CLIENT_BIN"

Note: The automated tool reports Tier 2 due to two 2025-03-26-only backward-compatibility auth scenarios and the spec tracking gap. Both are addressed in the detail sections above. All requirements for Tier 1 are met when evaluated against the spec version this SDK targets (2025-11-25).