FIDE Laws of Chess

Name: FIDE Laws of Chess
Author: io.arxo

MCP serverMCP

FIDE Laws of Chess (2023) as an executable model: arbiter cases, answers with rules and judgments

by io.arxorepository ↗homepage ↗v0.1.1

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"fide-laws-of-chess","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability26/27 checks ok

when	check	result	http	latency	detail
2 h ago	mcp initialize	ok	200	70 ms	server arxo-fide-chess-mcp 0.1.0 · protocol 2025-06-18 · 16 tools
8 h ago	mcp initialize	ok	200	43 ms	server arxo-fide-chess-mcp 0.1.0 · protocol 2025-06-18 · 16 tools
22 h ago	mcp initialize	failed	—	—	timeout
29 h ago	mcp initialize	ok	200	78 ms	server arxo-fide-chess-mcp 0.1.0 · protocol 2025-06-18 · 16 tools
2 d ago	mcp initialize	ok	200	76 ms	server arxo-fide-chess-mcp 0.1.0 · protocol 2025-06-18 · 16 tools
2 d ago	mcp initialize	ok	200	14 ms	server arxo-fide-chess-mcp 0.1.0 · protocol 2025-06-18 · 16 tools
2 d ago	mcp initialize	ok	200	79 ms	server arxo-fide-chess-mcp 0.1.0 · protocol 2025-06-18 · 16 tools
3 d ago	mcp initialize	ok	200	57 ms	server arxo-fide-chess-mcp 0.1.0 · protocol 2025-06-18 · 16 tools
3 d ago	mcp initialize	ok	200	127 ms	server arxo-fide-chess-mcp 0.1.0 · protocol 2025-06-18 · 16 tools
3 d ago	mcp initialize	ok	200	70 ms	server arxo-fide-chess-mcp 0.1.0 · protocol 2025-06-18 · 16 tools

Tools observed via MCP handshake

law_search — A semantic SEARCH over formalised law: a question or a notion in your own words → candidates with addresses — predicates with signatures, rules, article fragmen
law_passport — Passport of an exact release: purpose, interface, boundaries, checks and performance. The reports section holds the history of measurements, failures included.
law_answer_capabilities — A machine-readable matrix of the Lens producers that are actually installed, of replay/projection checks, profiles, limits and the contract tests that confirm t
law_capture_answer — Run a registered producer and obtain producerControl/0.2 for a later verifiable preparation of a Lens. The producer is chosen only from the shipped registry.
law_prepare_answer — At the explicit request of the user, repeat between 1 and 12 earlier law_ask or law_process_run calls, compare their replayControl strictly, and prepare a non-p
law_publish_answer — Publish a prepared document. Repeating it with the same preparationId idempotently returns the same URL and the same separate revocation secret.
law_revoke_answer — Revoke a published document using its separate secret. The public id alone grants no control; revocation closes the HTML page, the API and the download.
law_packages — The catalogue of formalised law: instruments, predicates with signatures, the boundaries of coverage. This is where the NAMES of predicates come from — they mus
law_ask — Put a question to formalised law. When the answer is "not established" it carries whyNot — the engine's why_not report: the candidate rules and the state of eve
law_screen — Build a necessary condition — a superset — for the preliminary selection of rows from an external source. This is NOT a legal answer and NOT SQL: the result is
law_rules — The rules of formalised law put into words: exactly how a predicate is derived (premises, source articles). Call this BEFORE supplying facts to law_ask — the ru
law_explain — Unfold the proof of a law_ask answer into a chain "rule ← premises → conclusion". The compact input: question (the original law_ask arguments, truth/collect), r
law_inspect — Evaluation inspector over a SAVED evaluation document: summary — the origin card, resultHash and snapshot verification, listings of results, positions and issue
law_case_ask — The ask operation: run a registered case of a case package over its pinned dependencies and return the answer: by default a projection of the evaluation documen
law_sources — Sources: by default short excerpts (view=summary), 5 texts per page, with the address of the full text in fragments[].full. Either package or fragment is requir
law_query — A deterministic LawQL query over the CLIR of a formalization: a question about the model of the act itself, not about a case. Relations (14): anchors, edges, fi

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.arxo/fide-chess

first seen 8 d ago · fetched 22 h agoopen ↗

Field history (7 recent events)

8 d ago · declared · summary → "FIDE Laws of Chess (2023) as an executable model: arbiter cases, answers with rules and judgments"
8 d ago · declared · description → "FIDE Laws of Chess (2023) as an executable model: arbiter cases, answers with rules and judgments"
8 d ago · declared · publisherName → "io.arxo"
8 d ago · declared · homepageUrl → "https://github.com/arxohq/arxo-fide-chess"
8 d ago · declared · repoUrl → "https://github.com/arxohq/arxo-fide-chess"
8 d ago · declared · version → "0.1.1"
8 d ago · declared · protocols → ["mcp"]

FIDE Laws of Chess

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from