ELYREON Payload Validator

io.github.colt2822Published by GitHub account colt2822v1.0.1Updated Nov 7, 2026

Deterministic, read-only JSON payload validation (bounded JSON Schema 2020-12 subset).

The publisher's own server: Video Transcript

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant validate JSON payloads against a bounded JSON Schema 2020-12 subset, read-only and deterministic.

What you can do
  • Validate JSON payloads against a bounded JSON Schema 2020-12 subset
  • Return deterministic, read-only validation results for submitted payloads
When to use it
Useful when an assistant needs to check that JSON documents conform to a schema, for example while building or debugging API requests and responses, without any write access to your data.
Requirements
A remote streamable HTTP endpoint; no local install. A bearer token is required in the Authorization header. A free trial token (20 calls per day) can be requested from the service's trial endpoint.
Before you install
The Authorization bearer token is a credential and must be kept private. Payloads are sent to a third-party hosted service, so avoid submitting sensitive data. Only a bounded subset of JSON Schema 2020-12 is supported, so results may differ from full validators.

Installation

In SourceWeft

  1. Open ELYREON Payload Validator in the dashboard and add it to a workspace.
  2. Connect Authorization token 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.colt2822%2Fpayload-validator/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.

{
  "mcpServers": {
    "elyreon-payload-validator": {
      "type": "http",
      "url": "https://elyreon-payload-validator.colt2822.workers.dev/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.1LatestNov 7, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Payload integrations