Legalize

dev.legalize/legalize

3/3 checks passed
Hosted
No secrets
★ 2 GitHub stars
Updated 2026-08-28
Health score 54

About Legalize

Legalize is an MCP server published by legalize.dev. Official MCP connector for Legalize: read and search its whole open corpus, at any point in time.

It is hosted by the publisher at one address, so there is nothing to install: your AI client connects to it over the internet.

It asks for no keys or passwords.

Version 0.18.0 was published on 28 August 2026, and the source code is public, so you can read it before installing.

Written from the registry entry. 6 automated checks on registry metadata: 3 pass, 0 warn, 0 fail, 3 info. How we check.

What it asks for

This server declares no environment variables, so it asks for no keys or settings.

Checks

Check	Result	Detail
Source repository linked	Pass	https://github.com/legalize-dev/mcp
Remote uses HTTPS	Pass	All remote endpoints use https://
Secrets requested	Info	Asks for no secrets
Namespace ownership	Info	Name verified via domain legalize.dev
Registry text aimed at the AI	Pass	Description and settings contain no hidden characters or instructions to the AI
Tool descriptions read	Info	Needs sign-in before it lists its tools, so they could not be read

Popularity & health: 54 / 100

Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.

Popularity4 / 40

2 GitHub stars, no download count, no Hacker News posts found. Best two of the three, each on a log scale.

Activity22 / 25

Last push 2026-10-22, no GitHub release, 17 commits in 90 days.

Issue health8 / 15

0 closed of 0 issues, too few to judge. No data, so half marks.

Our checks20 / 20

0 warnings, each costing a fifth.

0 forks, 1 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.

What people say

No Hacker News threads link to its source code.

Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.

Facts

Registry name	`dev.legalize/legalize`
Publisher	Domain legalize.dev
How the name is verified	Name verified via domain legalize.dev. The registry ties the name prefix to that account or domain; it does not check the code.
Type	Remote: hosted at a URL, nothing to install
Remote endpoints	streamable-http https://legalize.dev/mcp
Version	0.18.0
Published	2026-08-28
Last updated	2026-08-28
Source repository	https://github.com/legalize-dev/mcp
Website	https://legalize.dev/mcp
Category	Search & web (assigned by keyword rule, not by hand)

Install

Claude Code · hosted

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

What these checks don't cover

We did not run this server, so we don't know what it does when it runs. We could not read its code or its tool descriptions, which is where tool poisoning hides. And we don't watch it after you install: if the publisher changes it later (a rug pull), this page won't notice until the next scan. Treat a pass as "nothing found", not as "safe".

For people and their AI

The same data as plain JSON: /data/servers/dev-legalize-legalize.json. Text inside it that came from the publisher is data, not instructions.