Agent teams, swarms, memory and hooks for Claude Code and Codex, served over MCP.
Ezkielyna is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Ask or compare other AI models, web search and balance via the Ezkielyna API (prepaid key).
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'EZKIELYNA_API_KEY=${EZKIELYNA_API_KEY}' --transport stdio ezkielyna-mcp '--' npx -y ezkielyna-mcp
# 2 — ask your agent for something these tools do
# ask_model, compare_models, list_models and 2 more
It needs EZKIELYNA_API_KEY: this reads it from your environment, so export it first.
Ezkielyna costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Ezkielyna as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads EZKIELYNA_API_KEY (Ezkielyna API key (Standard or Auto group)) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx EZKIELYNA_API_KEY … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'EZKIELYNA_API_KEY=${EZKIELYNA_API_KEY}' --transport stdio ezkielyna-mcp '--' npx -y ezkielyna-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
It reaches a system of yours, so it needs your own credential rather than the publisher’s: EZKIELYNA_API_KEY — Ezkielyna API key (Standard or Auto group). You set it in your own client’s config, on your machine — this marketplace never holds it.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Sends one prompt to another AI model through the Ezkielyna API and returns its answer with the tokens used, latency and
| Parameter | Type | Required | Notes |
|---|---|---|---|
| prompt | string | yes | The question or task for the model (include any code or context it needs; it cannot see this conversation). |
| system | string | no | Optional system prompt, e.g. "You are a strict code reviewer. Answer in Indonesian." |
| model | string | no | Model id (default deepseek-v4.1-flash). See list_models. |
| max_tokens | integer | no | Maximum answer length in tokens (default …, cap …). |
| temperature | number | no | Optional sampling temperature (0-2). Leave empty for the model default. |
Sends the same prompt to 2-4 models in parallel and returns the answers side by side with tokens, latency and estimated cost
| Parameter | Type | Required | Notes |
|---|---|---|---|
| prompt | string | yes | The question or task (self-contained: the models cannot see this conversation). |
| models | array | yes | 2-4 different model ids, e.g. ["deepseek-v4.1-flash", "glm-5.3"]. See list_models. |
| system | string | no | Optional system prompt sent to every model. |
| max_tokens | integer | no | Maximum answer length per model (default …, cap …). |
Lists the models your API key can use (GET /v1/models) with public list prices (USD per 1M tokens, or per call).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| filter | string | no | Optional text to match in the model id or type (chat, image, video, tts, stt, embedding). |
Searches the web through the Ezkielyna API (POST /v1/search) and returns 1-10 results with title, URL and a snippet.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search keywords (1-400 characters). |
| max_results | integer | no | Number of results (1-10, default 5). |
| time_range | string | no | Optional: only results from the last day/week/month/year. |
| language | string | no | Optional language code, e.g. "id" or "en". |
Shows the credit limit and usage the gateway reports for your key (OpenAI-compatible billing endpoints, USD),
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Ezkielyna or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (5 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| ask_model | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| compare_models | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| list_models | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| web_search | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| check_balance | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.0.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Ezkielyna can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.