
JSON schema enforcer — Atom
org.aimldsPublished by aimlds.orgv0.1.0Updated Nov 17, 2026
JSON schema enforcer, delivered per API call as an atom service on Conduit Atoms.
The publisher's own server: Atom.com — Premium Domains
Overview
A remote atom service that enforces JSON schemas per API call, letting an assistant validate JSON against a schema.
- What you can do
- Validate JSON data against a schema through a remote atom service.
- Enforce schema conformance on a per-call basis.
- No tool list, instructions or README are published, so the exact operations and their inputs are not documented; the only stated capability is schema enforcement delivered per API call.
- When to use it
- When an assistant needs to check that JSON payloads conform to a schema and you prefer a hosted service over a local validator.
- Requirements
- A remote streamable HTTP endpoint at the provider's atom host; no local runtime or package. A bearer API key is required in the Authorization header, issued per user per atom after signing up on the atom's page.
Installation
In SourceWeft
- Open JSON schema enforcer — Atom in the dashboard and add it to a workspace.
- Connect Authorization token credentials. They are stored privately and never shown on public pages.
- 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/org.aimlds%2Fatom-json-schema-enforcer/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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"json-schema-enforcer-atom": {
"type": "http",
"url": "https://atoms.pipavia.com/mcp/json-schema-enforcer",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}README
This repository has no README.
Tools
0Version history
1- v0.1.0LatestNov 17, 2026
Score
70% 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.
- License10 pts
Other Atom integrations
Atom.com — Premium Domains
com.atomOfficial publisher
Atom.com's remote MCP server for searching, appraising, trademark-screening and buying premium brandable domain names.

Token estimator — Atom
org.aimlds
A remote atom service that estimates token counts, called per API request and authenticated with a per-user API key.

Markdown sanitizer — Atom
org.aimlds
Remote atom service that sanitizes Markdown per API call, exposed to assistants as an MCP endpoint at atoms.pipavia.com.

Zero trust architecture design pack — Atom
org.aimlds
Zero trust architecture design pack — Atom's hosted MCP server, published by aimlds.org; credential required; Streamable HTTP.

Zero knowledge system design pack — Atom
org.aimlds
Zero knowledge system design pack — Atom's hosted MCP server, published by aimlds.org; credential required; Streamable HTTP.