Validate Formhaus form definitions and simulate multi-step paths against the real engine.
Nothing to run from here
ELYREON JSON Schema Payload Validator 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.
6
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
JSON Schema validator for API payloads via MCP: bounded checks and structured pass/fail errors.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http elyreon-json-schema-payload-validator-mcp https://elyreon-payload-validator.colt2822.workers.dev/mcp --header 'Authorization: Bearer ${AUTHORIZATION}'
# 2 — ask your agent for something these tools do
# drex_choose, drex_yes_no, drex_rate and 3 more
It needs AUTHORIZATION (Free token: POST https://elyreon-payload-validator.colt2822.workers.dev/trial with JSON {"source":"mcp_registry"}. Enter Bearer TOKEN): this sends it in the Authorization header from your environment, so export it first — its endpoint answers 401 without it.
ELYREON JSON Schema Payload Validator costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ELAll 2 servers
elyraon2 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it. Claude Code reads AUTHORIZATION (Free token: POST https://elyreon-payload-validator.colt2822.workers.dev/trial with JSON {"source":"mcp_registry"}. Enter Bearer TOKEN) from your environment each time it connects and sends it in the Authorization header — its endpoint answers 401 without it — so the key stays out of its config: export it in your shell profile (macOS, Linux), or run setx AUTHORIZATION … and open a new terminal (Windows).
claude mcp add --scope user --transport http elyreon-json-schema-payload-validator-mcp https://elyreon-payload-validator.colt2822.workers.dev/mcp --header 'Authorization: Bearer ${AUTHORIZATION}'Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add — but its publisher asks for a key of their own on every call.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: Authorization header — Free token: POST https://elyreon-payload-validator.colt2822.workers.dev/trial with JSON {"source":"mcp_registry"}. Enter Bearer TOKEN.. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
6 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.
Make a fast, calibrated structured choice between 2 to 64 discrete options using Drex.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | The decision question |
| choices | array | yes | List of discrete choice options |
| context | string | yes | Context, diff, or error output |
| decision_type | string | no | Optional decision type identifier |
Make a binary YES/NO decision with calibrated probability using Drex.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | The question to answer YES or NO |
| context | string | yes | Context or code snippet |
| decision_type | string | no | Optional decision type identifier |
Rate or score risk, complexity, or quality across ordered levels using Drex.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | Rating question |
| criteria | array | yes | Ordered levels (e.g. ['low', 'medium', 'high']) |
| context | string | yes | Context or code snippet |
Preflight an engineering issue before expensive LLM planning: determines complexity, subsystem, target verifier, and architecture risk.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_description | string | yes | The problem description or issue |
| repo_summary | string | no | Repository overview or file tree |
Triage a candidate patch after generation: evaluates scope, completeness, risk, missing tests, and review readiness.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_objective | string | yes | Original goal |
| patch_diff | string | yes | Generated diff |
| verifier_evidence | string | yes | Test or build output |
Diagnose test or toolchain failure to identify root cause and prevent wasting coding agent tokens on environment errors.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| objective | string | yes | Task objective |
| changed_files | array | yes | — |
| verifier_command | string | yes | Test command that failed |
| exit_code | integer | yes | — |
| stdout_stderr | string | yes | Compiler or test error traceback |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 ELYREON JSON Schema Payload Validator or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
1.0.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish ELYREON JSON Schema Payload Validator can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.