net.imzala/ictihat
imzala.net — Türk içtihat arşivi
Is the imzala.net MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-10-26.
Turkish case law, updated daily: 11.5M decisions, citation check, statute map, deep research.
needs auth probed 2026-11-15 · unchanged since 2026-10-26 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"unauthorized","error_description":"kimlik gerekli"}- Endpoint
- https://mcp.imzala.net/mcp (streamable-http)
- Host
- mcp.imzala.net
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mcp.imzala.net/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server mcp.imzala.net, PKCE S256, grants authorization_code, refresh_token.
Scopes ictihat.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/asimokat/imzala-claude-eklenti
- Website
- https://imzala.net/yapay-zeka
- Registry
- active, updated 2026-10-23 · registry entry
Compare this server with others.
More servers
Servers that mention ictihat.
- Türk Hukuku İçtihat io.github.aydincan/turk-hukuku-ictihat-mcp · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.