Add dike-dify-tools plugin

[fr3on]

Plugin Submission

Plugin information

• Author: fr3on
• Plugin name: dike-dify-tools
• Version: 0.0.1
• Source repository: https://github.com/dikeai/plugins/tree/main/dike-dify-tools
• Contact: https://github.com/fr3on

Submission type

• New plugin
• Version update

What changed

Adds Dike Legal Search, a Dify tool plugin wrapping four grounded MENA legal research capabilities as native Dify tools: dike_search (hybrid semantic + lexical search over verified Saudi, Egyptian, and Emirati legislation, court rulings, and fatawa), dike_reason (grounded Q&A where every citation in the answer is verified against the retrieved source set before being returned, unverifiable claims dropped rather than fabricated), dike_cite (parses and resolves an Arabic legal citation string to its canonical source document), and dike_graph_traverse (finds documents that cite, amend, repeal, implement, or interpret a given document). These mirror the same four capabilities already exposed by Dike's own MCP server, packaged here as native Dify tools for chatflow/agent/workflow use without an MCP hop.

Risk level

• Low risk
• Medium risk
• High risk

The plugin only calls fixed, documented Dike API HTTPS endpoints (api.dike.it.com by default, or a self-hosted instance if the user configures a different base URL) with a user-supplied API key. It does not execute code/SQL, does not use SSH/filesystem/browser automation, does not process uploaded files, and does not fetch arbitrary user-controlled URLs.

Required checks

• I have read and followed the Marketplace submission requirements.
• I have read and comply with the Plugin Developer Agreement.
• I tested this plugin on Dify Community Edition, or documented any limitation below.
• The package contains only files needed at runtime.
• The package does not contain secrets, local credentials, .env files, .git directories, virtual environments, caches, logs, or IDE files.
• The package does not contain executables or bundled binaries, or I explained why they are required below.
• The plugin README includes setup steps, usage instructions, required APIs or credentials, connection requirements, and the source repository link.
• The plugin includes PRIVACY.md, and manifest.yaml references it.
• All user-facing text is primarily in English.

Security and privacy notes

The plugin sends whatever query/question/citation/canonical-ID the calling Dify app supplies to the configured Dike API and returns Dike's response. It does not persist the API key or any query/answer content beyond the single request being handled, and does not log API key values. No other sensitive capabilities. Documented in PRIVACY.md.

Local validation

Packaged with the official Dify plugin CLI (dify-plugin):
dify-plugin plugin package ./dike-dify-tools -o ./dike-dify-tools-0.0.1.difypkg
Verified the resulting archive contains only the 20 runtime files (no .git, caches, or secrets), and that manifest.yaml/provider/dike.yaml/each tools/*.yaml schema validates against the CLI's own packaging checks.

Reviewer notes

Not yet tested end-to-end against a live Dify instance Cloud -- only exercised locally against the Dike API directly and the plugin's own request/response mapping. Flagging this per the "Required checks" box above.

[crazywoola]

CI is green: Pre Check Plugin and PR Risk Label passed.