Dike

io.github.fr3onPublished by GitHub account fr3onv1.0.0Updated Oct 24, 2026

Grounded MENA legal search, reasoning, citation resolution, and citation-graph traversal.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

Dike is a remote MCP server for grounded legal search, reasoning, citation resolution and citation-graph traversal over Saudi, Egyptian and Emirati primary law.

What you can do
Search the legal corpus with hybrid semantic and lexical search, and browse or compare sources on a topic without answering a question. Ask grounded legal questions where every citation is verified against retrieved documents and unresolved references are dropped. Parse and resolve an Arabic citation string to a specific document. Traverse the citation graph to find documents that cite, amend, repeal, implement or interpret a given document. Run the full research workflow in order: search, reason, graph audit for amendments and repeals, then citation verification.
When to use it
Useful when you need answers or source material on Saudi, Egyptian or Emirati primary legal sources, especially when citations must be verified rather than guessed, or when you need to check whether a document has been amended or repealed.
Requirements
A remote endpoint at api.dike.it.com; nothing runs locally. A Dike API key is required, sent as an Authorization bearer token, or OAuth against an existing Dike account when connecting from Claude.ai or Claude Desktop. Self-serve signup is currently closed, so a key must be requested manually. Rate limits apply: 60 requests per minute by default, 10 per minute for reasoning.
Before you install
The Authorization header carries a live API key; keep it secret. Requests and legal queries go to a third-party service. Answers are limited to the covered corpus and should be checked against official sources before relying on them.

Installation

In SourceWeft

  1. Open Dike in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.fr3on%2Fdike/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "dike": {
      "type": "http",
      "url": "https://api.dike.it.com/mcp"
    }
  }
}

README

dike-legal-search

Claude Code plugin bundling Dike's remote MCP server: grounded search, reasoning, citation resolution, and citation-graph traversal over Saudi, Egyptian, and Emirati primary legal sources.

Requires

A Dike API key. Get one at https://dike.it.com/developers/ (self-serve signup is currently closed while in testing; request a key manually until it reopens, see https://dike.it.com/auth.md).

Setup

bash
export DIKE_API_KEY=your-key-here

Then, inside Claude Code:

/plugin marketplace add dikeai/plugins/plugin install dike-legal-search@dike-plugins

If you're connecting from Claude.ai or Claude Desktop's Connectors panel instead of Claude Code, click "Connect" on the dike connector, it uses OAuth against your existing Dike account rather than a pasted API key.

Commands

  • /dike-research — the full grounded workflow: search, reason, graph audit for amendments/repeals, and citation verification, in that order. Use this for an actual legal question.
  • /dike-search — browse and compare sources for a topic without answering a question.
  • /dike-cite — parse and verify a specific citation string against the corpus.

Tools

  • dike_search — hybrid semantic + lexical search over the corpus
  • dike_reason — grounded Q&A; every citation is verified against retrieved documents before being returned, unresolved references are dropped, never guessed
  • dike_cite — parse and resolve an Arabic citation string to a document
  • dike_graph_traverse — find documents that cite, amend, repeal, implement, or interpret a given document

Same rate limits as the REST API: 60 requests/minute default, 10/minute for dike_reason.

What this is not

This bundles Dike's existing production MCP server (api.dike.it.com/mcp), it does not run anything locally. There's no separate binary or package to install beyond this plugin's .mcp.json pointer.

Source: dike-legal-search/README.md at commit c9e0075

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.