Legalize

Your assistant no longer has to guess what the law said in 2023

Asked about a norm, a model answers from memory: no source, and a version it cannot name. This connector hands it the corpus instead — consolidated legislation from 32 countries, every reform it holds a dated commit. Here is a real answer, with the commit that makes it checkable.

“¿Qué decía el artículo 348 bis de la Ley de Sociedades de Capital en marzo de 2023?”

What did article 348 bis of the Spanish Companies Act say in March 2023?

law_at_date es · BOE-A-2010-10544 · Artículo 348 bis · 2023-03-31

Artículo 348 bis. Derecho de separación en caso de falta de distribución de dividendos.

1. Sin perjuicio de lo dispuesto en la disposición adicional undécima, salvo disposición contraria de los estatutos, transcurrido el quinto ejercicio contado desde la inscripción en el Registro Mercantil de la sociedad, el socio o socia que hubiera hecho constar en el acta su protesta por la insuficiencia de los dividendos reconocidos tendrá derecho de separación en el caso de que la junta general no acordara la distribución como dividendo de, al menos, el veinticinco por ciento de los beneficios obtenidos durante el ejercicio anterior que sean legalmente distribuibles siempre que se hayan obtenido beneficios durante los tres ejercicios anteriores.

… sections 2 to 5 and the amendment notes are trimmed here, for the page. The tool itself returns the article whole — it never hands back half of one.

citation
Real Decreto Legislativo 1/2010, de 2 de julio, por el que se aprueba el texto refundido de la Ley de Sociedades de Capital — texto de la última versión publicada hasta el 31/03/2023 (versión de 18/03/2023)
sha
3b9aea8d5f3495092a2ea3934360a94efcaa3fe7
url
legalize.dev/es/law/BOE-A-2010-10544/date/2023-03-31
The SHA is a commit in legalize-dev/legalize-es, not an identifier we minted for the answer. Run git show 3b9aea8d5:es/BOE-A-2010-10544.md and you get that exact file — the text below, under the YAML frontmatter the corpus stores its metadata in, which the connector reads and does not hand back. That is what makes the quote checkable by whoever reads your brief.
Add to Claude Add to Cursor Add to VS Code Add to ChatGPT

The first three fill in the address for you, then ask you to confirm it and sign in: there is no anonymous mode, every call is tied to an account. ChatGPT opens its create-connector form instead, where the endpoint below gets pasted — it needs developer mode on, under Settings → Connectors → Advanced.

Any other MCP client

Anything else — add a connector and paste this endpoint. Same address for all of them:

https://legalize.dev/mcp

In Claude Code it is one command:

claude mcp add --transport http legalize https://legalize.dev/mcp

What it costs

A monthly allowance of requests, free. Every request to the connector counts against it — including connection setup, not just the tools below. Past that the connector answers quota_exceeded, which names your limit, and stops until the month rolls over — nothing is charged and nothing is cut off silently. Your own limit is on your dashboard; the paid tiers raise it, and every country is included in all of them.

The tools

Almost all of them read. The one above is law_at_date; the ones marked writes are the only ones that change anything, they change your own subscriptions and nothing else, and they need the Pro plan.

  • list_countries Which countries are in the corpus, and how many laws each one holds.
  • search_laws Find a norm by words in its title or by its official number.
  • get_law Read what a norm says today — the whole text, or one article of it.
  • law_at_date What the norm said on a given day, with the git SHA behind that version.
  • diff_law What changed between two dates, as a diff of the two texts.
  • reform_history Which norms amended this one, when, and what each says it touched.
  • law_stats How large a corpus is and how much it moves, before drilling into it.
  • create_webhook writes Subscribe an endpoint of yours to law changes — one law, one topic, one country.
  • preview_webhook Try a subscription rule against the last 30 days without creating anything.
  • list_webhooks The endpoints this account already has, and the ids to delete them by.
  • set_webhook_enabled writes Pause one, or start it again. The endpoint, its rule and its history stay.
  • delete_webhook writes Remove one of them. Deliveries stop, and its history goes with it.
  • create_email_digest writes The same rule, delivered as one email a day to your own address instead of to a server you run.
  • list_email_digests The digests this account already gets, and the ids to delete them by.
  • set_email_digest_enabled writes Pause the mail, or start it again. Paused, it keeps its place and catches up on resume.
  • delete_email_digest writes Stop one. The daily mail ends immediately.

Before you quote it

Most of the corpus is consolidated: amendments are folded into the text, so what you read is the law as it stands. Some of it is not.

These corpora hold texts published as enacted, with amendments recorded separately rather than merged in: pt Portugal, 97% of 171,755 norms; gr Greece, 4 of 6,810 norms; ad Andorra, 1 of 3,595 norms.

Every answer says which kind it is. An as_enacted text comes back flagged, with the norms that amend it named, and never as the law in force — but the flag is only useful if you read it before pasting the quote into a brief.

Two more limits worth knowing: a date resolves to what was published on or before it, not to what was in force, and article boundaries are derived from the headings in the text rather than published as structure by the source.

On writing: most of the tools cannot change anything at all, and the ones that can only touch your own subscriptions — an endpoint of yours, or a digest sent to your own address. Turning one off never needs a plan, whatever plan you are on. Nothing any tool does can alter a law, a version or a corpus — those come from the git repositories, and the connector has no way in.

Being told when a law changes is what create_webhook is for: point it at an HTTPS endpoint of yours and we POST there, signed, when a norm is published, amended or repealed. Narrow it to the laws you actually follow — specific norms, a topic, a country — and use preview_webhook first to see what a rule would have caught last month, because a filter that catches nothing looks exactly like a quiet month. It is on the paid plans; the change feed answers the same question by polling and is on every plan. Neither is a substitute for reading the text before you rely on it.

The pipeline, the corpus and the git history are all open source. Prefer HTTP? The same data is at the REST API.