Markdown sanitizer — Atom

● Active

org.aimlds/atom-markdown-sanitizer

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

Connect this server

One click to install, or copy the config below. Suits: Cursor · HTTP clients.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "atom-markdown-sanitizer": {
      "url": "https://atoms.pipavia.com/mcp/markdown-sanitizer"
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --transport http atom-markdown-sanitizer https://atoms.pipavia.com/mcp/markdown-sanitizer
VS Code
code --add-mcp '{"name":"atom-markdown-sanitizer","type":"http","url":"https://atoms.pipavia.com/mcp/markdown-sanitizer"}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Documents & Knowledge
Version
0.1.0
Registry
active
Published
11/17/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Looks healthy: Markdown sanitizer — Atom is maintained, open source, hosted endpoint behind a sign-in.

Maintained
Active
Last commit 3 days ago (Nov 18, 2026), 1 open issues.
Official registry
Active
Published as org.aimlds/atom-markdown-sanitizer in the official MCP registry, version 0.1.0.
Source
Open source, Apache-2.0
Public repository under the Apache-2.0 licence, 1 stars, 0 forks.
Runs
Hosted by the publisher
Your client talks to atoms.pipavia.com: prompts and tool arguments leave your machine for that host.
Credentials
Sign-in required
The hosted endpoint answered 401/403 to a credential-free call (checked Nov 22, 2026): it wants an API key or an OAuth login first.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.

Live check

checked Nov 22, 2026, 00:07 UTCStatus history & uptime →
● Needs sign-in

The endpoint is up but wants a key or an OAuth sign-in before the handshake, so its tools can only be read with an account.

Checked by Serverdex with a plain initialize + tools/list call to atoms.pipavia.com/mcp/markdown-sanitizer, no credentials, about once a day. A failed check is never a removal.

On GitHub

read Nov 18, 2026
Stars
1
Forks
0
Last push
Nov 18, 2026
License
Apache-2.0

TypeScript

From the README

atom-services Conceived by Nrupal Akolkar · Built by Muse (Arjun/Wright). One collective repo for all product atoms. An atom is a small, independent service that delivers one bounded judgment artifact — a VERDICT, a CHECK, a MAP, a STAMP, a REPORT — over API / MCP / agent / human endpoints, paid per unit delivered. Atoms never sell the underlying knowledge; they sell the artifact the knowledge produces. The model in plain words • Independent atoms, one home. Every atom is its own named service unit in services/ /, with its own endpoints, its own payment plan, and its own growth / retention / maintenance docs. Atoms are never merged into existing product repos — this repo is their only home. Shared rails live once at the repo root (rails/), not inside any product. • The rail is Conduit. Atoms are listed and discovered through Conduit (the owner's connector marketplace, live since 2026-11-12) and served as key-gated MCP/API endpoints in Conduit's shape. Where Conduit lacks a piece atoms need, the gap is named in rails/ and in BUILD-LOG.md — never papered over. • One by one. Atoms release one by one (or bundle by bundle), in the approved queue order — never the whole register at once. Release #1 is release-readiness-verdict. • Volume pricing doctrine. Cheap per unit, millions of units. The earning lever is refinement — narrower, sharper services get called more — not price height.…

Read the full README on GitHub →

Remotes

  • streamable-httphttps://atoms.pipavia.com/mcp/markdown-sanitizer

The most-starred Documents & Knowledge servers in the index, with their live-check result.

ServerStarsLast pushLive check
Context765,010Nov 2026Working
Codebase Memory48,994Nov 2026Local / not checked
Reactive Resume45,960Nov 2026Needs sign-in
Sui Knowledge Base (kapa.ai)7,785Nov 2026Needs sign-in
Agent-Native Slides7,735Nov 2026Needs sign-in

Markdown sanitizer — Atom: questions people ask

Is Markdown sanitizer — Atom a remote or a local MCP server?
According to its entry in the official MCP registry, Markdown sanitizer — Atom ships as a hosted endpoint (streamable-http) that your client connects to by URL.
Does Markdown sanitizer — Atom need an API key or a sign-in?
Yes. Its hosted endpoint answered the credential-free Serverdex live check with HTTP 401/403 on Nov 22, 2026: it expects an API key in a header or an OAuth login before it lists its tools.
Is Markdown sanitizer — Atom safe to use?
Looks healthy: Markdown sanitizer — Atom is maintained, open source, hosted endpoint behind a sign-in. In detail — maintained: Active; official registry: Active; source: Open source, Apache-2.0; runs: Hosted by the publisher; credentials: Sign-in required. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is Markdown sanitizer — Atom still maintained?
Active: the repository's last commit 3 days ago. Last push Nov 18, 2026, 1 GitHub stars, Apache-2.0 licence. Read from GitHub on Nov 18, 2026.
How do I add Markdown sanitizer — Atom to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
  1. codetopo — code graph for AI agentsDomain-blind code graphs for AI agents: symbols, calls, blast radius, proof-checked snapshots.★ 2
  2. Conduit Router — Governed MCP RoutingGoverned MCP routing: every agent call spend-capped, metered, sealed with a verifiable receipt.
  3. Verdict — Send anything. Get the truth.Send anything. Get the truth — REAL, SUSPICIOUS or LIKELY SCAM verdicts on messages and links.
  4. LetsAskItCreation-first AI content engine: one brief in, finished content everywhere, in your brand voice.
Browse all Documents & Knowledge →

Add the badge to your site

Show visitors that Markdown sanitizer — Atom is listed here — it’s also the link we check for a free listing.

Markdown sanitizer — Atom — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/org-aimlds-atom-markdown-sanitizer?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Markdown sanitizer — Atom — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Markdown sanitizer — Atom — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/org-aimlds-atom-markdown-sanitizer?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/org-aimlds-atom-markdown-sanitizer) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/org-aimlds-atom-markdown-sanitizer) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/org-aimlds-atom-markdown-sanitizer)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/org-aimlds-atom-markdown-sanitizer"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/org-aimlds-atom-markdown-sanitizer"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/org-aimlds-atom-markdown-sanitizer"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).