JassWiki — Swiss Jass Authority (AMCP v0.1)

ch.jassverbandv1.0.3Updated Sep 29, 2026

First production Authority-MCP. W3C VC attested by Jassverband Schweiz.

VerifiedStreamable HTTPWeb executableOther

Installation

In SourceWeft

  1. Open JassWiki — Swiss Jass Authority (AMCP v0.1) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "jasswiki": {
      "type": "http",
      "url": "https://jasswiki.ch/mcp/http"
    }
  }
}

README

JassWiki MCP — Authority-Attested Knowledge Server for Swiss Jass

Erste vom Schweizer Jassverband (JVS) attestierte MCP-Quelle. Kryptographisch verifizierbar via did:web:jassverband.ch.

[smithery badge] [Official MCP Registry] [License: CC BY-SA 4.0] [MCP] [Authority]

JassWiki MCP gibt KI-Assistenten (Claude, ChatGPT-Connectors, Perplexity, Gemini Agentspace) direkten Zugriff auf die offizielle Schweizer Jass-Wissensbasis: 230+ kuratierte Artikel zu Regeln, Spielvarianten, Terminologie, Geschichte und Taktik. Inhalte sind durch den Jassverband Schweiz (Wikidata: Q139042763) als offizielle Wissens-Quelle attestiert.

This is the first production deployment of the AMCP v0.1 specification, developed by Agentic Relations (Architect: Remo Prinz). It demonstrates how organisations and federations can become cryptographically verifiable knowledge sources for AI agents — beyond traditional SEO and brand visibility.

Trust-Chain:

Installation

Endpoint (Streamable HTTP): https://jasswiki.ch/mcp/http — no auth, no API key.

Claude (claude.ai / Desktop)

Settings → Connectors → Add custom connector → URL https://jasswiki.ch/mcp/http.

ChatGPT (Apps & Connectors)

Settings → Connectors → Add custom app/connector → URL https://jasswiki.ch/mcp/http (requires a paid plan; enable Developer Mode if needed).

Claude Code (CLI)

bash
claude mcp add --transport http jasswiki https://jasswiki.ch/mcp/http

After connecting, the jasswiki server exposes three tools.

Reference URLs (any MCP-compatible client)

MCP Endpoint:    https://jasswiki.ch/mcp/http   (Streamable HTTP)Health:          https://jasswiki.ch/mcp/healthManifest:        https://jasswiki.ch/.well-known/mcp.jsonAuthority:       https://jassverband.ch/.well-known/mcp-authority.jsonDID Document:    https://jassverband.ch/.well-known/did.json

Tools

show_jass_card(query)

Render an official branded JassWiki knowledge card (jasswiki.ch UI, via the MCP Apps extension / SEP-1865) for a Swiss Jass term, rule, variant or question — with definition, category, related terms and source link. This is the default answer path in hosts that support MCP Apps.

Example:

show_jass_card(query="Karte fällt runter")

search_jass_knowledge(query, limit?)

Semantic search across the official JassWiki encyclopedia (230+ articles, Pinecone-backed with keyword fallback). Understands natural-language questions. Returns matching titles, IDs, URLs, and content excerpts.

Example:

search_jass_knowledge(query="Was gilt, wenn eine Karte runterfällt?", limit=3)

get_term_details(id)

Retrieve the full official rule or definition for a specific term ID. Use after search_jass_knowledge for verification of exact wording.

Example:

get_term_details(id="schieber")

Example Conversations

Rule clarification:

User: "What are the official rules for Schieber-Jass?" AI: [calls search_jass_knowledge] → Returns the canonical Schieber-rules sourced from JassWiki.ch with authority footer.

Variant lookup:

User: "Difference between Coiffeur-Schieber and Differenzler?" AI: [calls search_jass_knowledge for both] → Returns comparison sourced from official terminology.

Tactical reference:

User: "Welche Verwerfen-Konventionen gibt es im Schieber?" AI: [calls search_jass_knowledge] → Returns tactical signaling conventions with citation.

Verifying the Authority Attestation (W3C Verifiable Credential)

The JassWiki MCP server is the first MCP service in Switzerland with cryptographically verifiable authority attestation, expressed as a W3C Verifiable Credential (Data Model 2.0) signed with the eddsa-jcs-2022 cryptosuite. Any standard W3C VC verification library can confirm it.

Quick verify with any W3C VC library

The attestation document is a self-contained Verifiable Credential — fetch and verify in one step:

bash
curl -s https://jassverband.ch/.well-known/mcp-authority.json

The proof.proofValue field contains the signature in multibase base58btc format. Use any of:

Manual verification (Python, no W3C VC library required)

bash
pip install pynacl base58
python
import json, hashlib, urllib.requestimport nacl.signing, base58
# 1. Fetch the VC + DID documentvc = json.load(urllib.request.urlopen('https://jassverband.ch/.well-known/mcp-authority.json'))did = json.load(urllib.request.urlopen('https://jassverband.ch/.well-known/did.json'))
# 2. Reconstruct the signed hash data per eddsa-jcs-2022def jcs(obj):    return json.dumps(obj, sort_keys=True, separators=(',', ':'), ensure_ascii=False).encode('utf-8')
unsigned_doc = {k: v for k, v in vc.items() if k != 'proof'}proof_config = {k: v for k, v in vc['proof'].items() if k != 'proofValue'}
doc_hash = hashlib.sha256(jcs(unsigned_doc)).digest()proof_hash = hashlib.sha256(jcs(proof_config)).digest()hash_data = proof_hash + doc_hash  # W3C VC Data Integrity ordering
# 3. Decode signature from multibase base58btcproof_value = vc['proof']['proofValue']assert proof_value.startswith('z')  # 'z' = base58btc multibase prefixsignature = base58.b58decode(proof_value[1:])
# 4. Decode public key from DID documentimport base64pub_jwk_x = did['verificationMethod'][0]['publicKeyJwk']['x']public_key = base64.urlsafe_b64decode(pub_jwk_x + '==')
# 5. Verifynacl.signing.VerifyKey(public_key).verify(hash_data, signature)print('✓ W3C VC verified — JassWiki MCP is officially attested by Jassverband Schweiz')

The attestation is governed by JVS Vorstandsbeschluss 2026-06-10 (JVS-VS-2026-06-10-AMCP-01) — the signed board resolution PDF, whose SHA-256 digest is anchored in the credential's termsOfUse.digestSRI.

Specification: AMCP v0.1 (Authority-MCP)

JassWiki MCP is the first production implementation of AMCP v0.1 — An Applied Profile of W3C Verifiable Credentials and DID:web for MCP Server Authority Attestation.

AMCP is not a new standard — it is a thin profile that combines:

LayerExisting Standard
Identity of the authorityW3C DID Core (did:web method)
Cryptographic envelopeW3C Verifiable Credentials Data Model 2.0
Signature suiteeddsa-jcs-2022 (Ed25519 + JCS canonicalization)
Entity descriptionsSchema.org + JSON-LD
Canonical entity IDsWikidata QIDs
Server protocolAnthropic MCP
DiscoveryHTTP Link header (RFC 8288) + .well-known/

The contribution of AMCP is the combination — specifying how an organisation declares its official MCP server with cryptographic proof, Wikidata-anchored entity references, and a verifiable trust chain.

Spec owner & architect: Agentic Relations — founder: Remo Prinz.

📄 Read the full specification: AMCP v0.1 Working Draft (3,600 words; canonical URL https://agenticrelations.ch/specs/amcp/v0.1)

The methodology applies to any organisation, federation, public-sector body, or association that wants to become a cryptographically verifiable knowledge source in the agentic web.

Feedback and adoption inquiries: open an issue or contact [email protected].

Operator & Authority

Data & Licensing

Attribution must include the JassWiki.ch link and indicate any modifications.

Status & Reliability

  • Production since: January 2026
  • Hosting: Firebase Cloud Functions, region us-central1 (low-latency global)
  • Languages supported: German (primary), French, Italian, English (ongoing expansion)
  • Uptime SLA: Best-effort (99.5%+ historical)

For service incidents or schema changes, watch the GitHub releases.

Contributing

JassWiki content is curated. To suggest factual corrections, terminology updates, or new variants:

  1. Open an issue on JassWiki GitHub (the public site repo)
  2. Or contact directly: [email protected]
  3. New entries are reviewed by JVS (4-eyes principle) before publishing

The MCP server itself (this repository) accepts PRs for documentation improvements, examples, and submission metadata.

Erste öffentlich-rechtliche Authority-MCP der Schweiz. The first publicly attested MCP knowledge server in Switzerland.

Source: README.md at commit 786efb7

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.3LatestSep 16, 2026