eulaw-legal-research
Registry code: efa94a3e0af13869
eulaw.ai serves European legislation and case law with the identifiers and source URLs needed to cite it. Search it whenever an answer depends on what a European law says or how a court applied it, rather than answering from recollection. Scope every search to jurisdiction codes returned by list_jurisdictions. Quote and cite the retrieved text, keep each document's identifiers and URL with the claim they support, and say so plainly when a search returns nothing rather than filling the gap.
- endpoint
- https://eulaw.ai/api/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- bearer
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is eulaw-legal-research live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is eulaw-legal-research free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does eulaw-legal-research have?
- 3 tools: list_jurisdictions, get_document, search_legal_sources.
- Is eulaw-legal-research safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 3 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_jurisdictions auth-required 2h ago
List the jurisdiction codes this server can search, with their names. Call it before the first search of a conversation, or whenever a question names a country whose coverage you have not confirmed, so the search is scoped to codes that exist rather than guessed ones. Coverage changes as jurisdictions are added, so treat the returned list as current and do not assume a code is covered because it was covered before.
{ "type": "object", "properties": {} }arguments 4 linesget_document auth-required 2h ago
Fetch the text of a single document from the eulaw.ai corpus by the document_id and jurisdiction that search_legal_sources returned for it. Use it when a passage from search is not enough to answer accurately - to read the provision around a quoted fragment, to check a definition, or to confirm wording before relying on it. Documents can be long, so it returns a slice: the response states the total length and whether more remains, and offset pages through the rest. It takes only identifiers this server issued; it cannot fetch a document from a URL or a citation.
{ "type": "object", "required": [ "document_id", "jurisdiction" ], "properties": { "offset": { "type": "integer", "minimum": 0, "description": "Character offset to start reading from (default 0). Use it to continue past a truncated slice." }, "max_chars": { "type": "integer", "maximum": 50000, "minimum": 1, "description": "How many characters to return (default 20000, maximum 50000)." }, "document_id": { "type": "string", "maxLength": 500, "description": "The document_id from a search_legal_sources result. Opaque - do not construct one." }, "jurisdiction": { "type": "string", "maxLength": 10, "description": "The jurisdiction code the document was returned under." } } }arguments 30 linessearch_legal_sources auth-required 2h ago
Semantic search over eulaw.ai's corpus of European legislation and case law. Use it whenever a question turns on what a European or national European law actually says, or on how a court has applied it, and you need the authoritative text rather than recollection. Returns one entry per matching document: title, jurisdiction, document type, publication date, the identifiers that document carries (CELEX, ELI, ECLI where they apply), a source URL, an opaque document_id, and a passage from the document. It returns passages, not whole documents - call get_document with the document_id when the surrounding text matters. It cannot answer about jurisdictions outside the covered set: call list_jurisdictions first if you do not already know which codes are covered. It is not a general web search and holds no material outside the legal corpus.
{ "type": "object", "required": [ "query", "jurisdictions" ], "properties": { "limit": { "type": "integer", "maximum": 50, "minimum": 1, "description": "How many documents to return (default 8)." }, "query": { "type": "string", "maxLength": 2000, "minLength": 2, "description": "What to search for, as a natural-language description of the legal question or subject matter. Matching is semantic, so a full question works better than isolated keywords. Query in the language of the jurisdiction being searched where possible: the corpus is stored in each source's own language, and a query in another language matches it only through translation." }, "jurisdictions": { "type": "array", "items": { "type": "string" }, "maxItems": 15, "minItems": 1, "description": "Which jurisdictions to search, as the codes returned by list_jurisdictions. Required - there is no all-jurisdictions search. At most 15 per call." }, "only_in_force": { "type": "boolean", "description": "When true, drop documents whose expiry date has passed, so only currently applicable law is returned. Leave false (the default) when legislative history, superseded versions or the state of the law at some earlier time is part of the question. Setting it costs additional lookup time." } } }arguments 34 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idefa94a3e0af13869.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/efa94a3e0af13869/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/efa94a3e0af13869?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.