Markdown sanitizer — Atom

org.aimldsPublished by aimlds.orgv0.1.0Updated Nov 17, 2026

Markdown sanitizer, delivered per API call as an atom service on Conduit Atoms.

The publisher's own server: Atom.com — Premium Domains

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

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

What you can do
  • Sanitize Markdown content through a per-call atom service on Conduit Atoms.
  • No tool list, README or server instructions are published, so the exact operations and output format are not documented here.
  • Access is scoped to a single atom namespace (markdown_sanitizer) with its own key.
When to use it
Consider it when you need Markdown cleaned or sanitized as a service step and are willing to use a hosted third-party endpoint with a per-user API key. Without a published tool list, verify its behavior before relying on it.
Requirements
Remote streamable HTTP endpoint at atoms.pipavia.com; no local package or runtime. A bearer token is required in the Authorization header, described as the atom's own API key. Keys are per user and per atom and are issued from the atom's page after sign-up.
Before you install
You must sign up and obtain a per-user, per-atom API key, sent as a bearer token in the Authorization header. Content submitted for sanitizing is sent to a third party service. No tool list or documentation is published, so what it does with input and what it returns is unverified.

Installation

In SourceWeft

  1. Open Markdown sanitizer — Atom 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/org.aimlds%2Fatom-markdown-sanitizer/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": {
    "markdown-sanitizer-atom": {
      "type": "http",
      "url": "https://atoms.pipavia.com/mcp/markdown-sanitizer",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

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. 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