Developer · Remote MCP server
Atomicreps
Retrieval practice in your coding agent: one short question about what you just built.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.atomicreps/atomicreps- Version
- 0.1.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-30
- Updated
- 2026-09-30
- Publisher
- atomicreps (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/atomicreps) · how
- Repository
- github.com/atomicreps/cli
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://atomicreps.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | atomicreps | 0.1.0 | stdio |
How to connect Atomicreps
Atomicreps is a remote MCP server: there is nothing to install. Its endpoint is https://atomicreps.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: atomicreps version 0.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y atomicreps@0.1.0.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"atomicreps": {
"command": "npx",
"args": [
"-y",
"atomicreps@0.1.0"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Atlas ScoutLocal, read-only structural code navigation and bounded dependency analysis for source repositories. | Local · stdio |
| Atlassian Dc MCP BitbucketMCP server for Atlassian Bitbucket Data Center - interact with repositories and code. | Local · stdio |
| Atlassian Dc MCP BitbucketMCP server for Atlassian Bitbucket Data Center - interact with repositories and code. | Local · stdio |
| Atomadic ForgeArchitecture compiler for AI code. 11 tools, 92 actions, 872 Lean4 proofs, 100/100 self-cert. | Remote & Local · HTTP, stdioLive check: ✗ no handshake |
| AtonoGive your AI coding tools your team's product context: stories, bugs, epics, and glossary. | Local · stdio |
| Attack Surface MCP ServerPassive external attack-surface mapping: CT subdomains, DNS, TLS, HTTP posture, RDAP/WHOIS, Shodan. | Local · stdio, HTTP |
| Attest proxyZero-code proxy: policy, human gate, read-back and a hash-chained ledger for any MCP server. | Local · stdio |
| Attestd MCPCVE checks, supply chain signals, live catalog, and CVE detail for MCP clients (infra, PyPI, npm). | Local · stdio |