Server data from the Official MCP Registry
First production Authority-MCP. W3C VC attested by Jassverband Schweiz.
First production Authority-MCP. W3C VC attested by Jassverband Schweiz.
Remote endpoints: sse: https://us-central1-jassguru.cloudfunctions.net/mcp/sse
Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.
Endpoint verified · Open access · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"ch-jassverband-jasswiki": {
"url": "https://us-central1-jassguru.cloudfunctions.net/mcp/sse"
}
}
}From the project's GitHub README.
Erste vom Schweizer Jassverband (JVS) attestierte MCP-Quelle. Kryptographisch verifizierbar via
did:web:jassverband.ch.
JassWiki MCP gibt KI-Assistenten (Claude, ChatGPT-Connectors, Perplexity, Gemini Agentspace) direkten Zugriff auf die offizielle Schweizer Jass-Wissensbasis: 520+ 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:
Add to claude_desktop_config.json (~/Library/Application Support/Claude/ on macOS):
{
"mcpServers": {
"jasswiki": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://us-central1-jassguru.cloudfunctions.net/mcp/sse"
]
}
}
}
Restart Claude Desktop. The jasswiki server will appear with two tools.
SSE Endpoint: https://us-central1-jassguru.cloudfunctions.net/mcp/sse
Messages POST: https://us-central1-jassguru.cloudfunctions.net/mcp/messages
Health: https://us-central1-jassguru.cloudfunctions.net/mcp/health
Manifest: https://jasswiki.ch/.well-known/mcp.json
Authority: https://jassverband.ch/.well-known/mcp-authority.json
DID Document: https://jassverband.ch/.well-known/did.json
search_jass_knowledge(query, limit?)Fuzzy-search across the official JassWiki encyclopedia (520+ articles). Returns matching titles, IDs, URLs, and content excerpts.
Example:
search_jass_knowledge(query="Schieber-Regeln", 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")
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_knowledgefor 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.
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.
The attestation document is a self-contained Verifiable Credential — fetch and verify in one step:
curl -s https://jassverband.ch/.well-known/mcp-authority.json
The proof.proofValue field contains the signature in multibase base58btc format. Use any of:
@digitalbazaar/vc + @digitalbazaar/eddsa-jcs-2022-cryptosuite@veramo/credential-w3c with eddsa-jcs-2022 pluginpyld + PyNaCl (manual JCS implementation, see below)ssi cratepip install pynacl base58
import json, hashlib, urllib.request
import nacl.signing, base58
# 1. Fetch the VC + DID document
vc = 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-2022
def 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 base58btc
proof_value = vc['proof']['proofValue']
assert proof_value.startswith('z') # 'z' = base58btc multibase prefix
signature = base58.b58decode(proof_value[1:])
# 4. Decode public key from DID document
import base64
pub_jwk_x = did['verificationMethod'][0]['publicKeyJwk']['x']
public_key = base64.urlsafe_b64decode(pub_jwk_x + '==')
# 5. Verify
nacl.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-05-04 (JVS-VS-2026-05-04-AMCP-01).
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:
| Layer | Existing Standard |
|---|---|
| Identity of the authority | W3C DID Core (did:web method) |
| Cryptographic envelope | W3C Verifiable Credentials Data Model 2.0 |
| Signature suite | eddsa-jcs-2022 (Ed25519 + JCS canonicalization) |
| Entity descriptions | Schema.org + JSON-LD |
| Canonical entity IDs | Wikidata QIDs |
| Server protocol | Anthropic MCP |
| Discovery | HTTP 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 architect@agenticrelations.ch.
did:web:jassverband.chAttribution must include the JassWiki.ch link and indicate any modifications.
us-central1 (low-latency global)For service incidents or schema changes, watch the GitHub releases.
JassWiki content is curated. To suggest factual corrections, terminology updates, or new variants:
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.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.