atlasent-stdio

atlasent-stdio is an MCP server for Claude Code, Codex, Cursor, Gemini CLI, OpenCode from AtlaSent-Systems-Inc/atlasent-mcp-server. Its token cost is not measured, scanned A, original, Apache-2.0.

An AtlaSent MCP server that checks authorization before an AI agent executes an action. This recommended local connection uses the standard input/output channel between programs and connects to a hosted AtlaSent service.

In plain words
What is it for?
Use it to provide AtlaSent authorization tools to MCP-compatible agents such as Claude Desktop, Cursor, or Windsurf.
Why use it?
It adds a permission check before external tool actions and avoids exposing an HTTP server to the network. The server denies actions when authorization or verification fails.

MCP server for Claude CodeCodexCursorGemini CLIOpenCode

Written for no agent in particular: it speaks MCP, so any client can run it. Also seen: listed in a Claude config.

One of 3 entries in claude_desktop_config.json upstream. Installing this one merges just its entry into your config; the other 2 are separate, each on its own page.

Good fit Use it to provide AtlaSent authorization tools to MCP-compatible agents such as Claude Desktop, Cursor, or Windsurf.

Compare 6 mcp servers from other repositories ↓
Install with agentmods
npx agentmods add mcp/atlasent-systems-inc/atlasent-mcp-server/atlasent-stdio
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/AtlaSent-Systems-Inc/atlasent-mcp-server

Made for: Claude Code, Codex, Cursor, Gemini CLI, OpenCode.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for atlasent-stdio

README.md
[![agentmods](https://agentmods.dev/badge/mcp/atlasent-systems-inc/atlasent-mcp-server/atlasent-stdio/github.svg)](https://agentmods.dev/mcp/atlasent-systems-inc/atlasent-mcp-server/atlasent-stdio)
Your own site
<a href="https://agentmods.dev/mcp/atlasent-systems-inc/atlasent-mcp-server/atlasent-stdio"><img src="https://agentmods.dev/badge/mcp/atlasent-systems-inc/atlasent-mcp-server/atlasent-stdio/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for atlasent-stdio

Your own site · 80×15
<a href="https://agentmods.dev/mcp/atlasent-systems-inc/atlasent-mcp-server/atlasent-stdio"><img src="https://agentmods.dev/badge/mcp/atlasent-systems-inc/atlasent-mcp-server/atlasent-stdio.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

atlasent-stdio scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

examples/claude_desktop_config.json · 16 lines

What it actually says

{
  "atlasent-stdio": {
    "_comment": "Recommended: stdio transport (no network exposure, works out of the box).",
    "command": "npx",
    "args": [
      "-y",
      "@atlasent/mcp-server"
    ],
    "env": {
      "ATLASENT_API_KEY": "<your-atlasent-api-key>",
      "_base_url_note": "Use your runtime base ending in /functions/v1, e.g. https://<project-ref>.supabase.co/functions/v1. The api.atlasent.io apex 404s unless a custom domain is verified for your tenant.",
      "ATLASENT_BASE_URL": "https://<project-ref>.supabase.co/functions/v1",
      "ATLASENT_MODE": "remote"
    }
  }
}
Same file

What else claude_desktop_config.json configures

This page is one entry in a file that holds 3. Installing the file brings all of them; each is measured and scanned on its own page.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 16 lines scan A c6efbc848b24

Subscribe to this mod's changes

atlasent-stdio is an MCP server published in the GitHub repository AtlaSent-Systems-Inc/atlasent-mcp-server (0 stars, last pushed 4d ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.