n3tz Atlas

ai.n3tzPublished by n3tz.aiOfficial publisherv0.1.2Updated Oct 31, 2026

Governed company knowledge over MCP. Synthetic read-only demo; customer Atlas by contract.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Remote MCP endpoint that gives an assistant governed, read-only access to company knowledge, offered as a synthetic demo.

What you can do
  • The manifest lists no tools, so capabilities come from the description only.
  • It is described as governed company knowledge served over MCP, meaning an assistant can query organizational knowledge under defined access rules.
  • The public endpoint is a synthetic, read-only demo; a customer-specific Atlas instance is provided by contract.
When to use it
Worth trying when you want to evaluate how an assistant answers questions over governed company knowledge before committing to a contracted deployment.
Requirements
A remote streamable HTTP endpoint at the provider's demo host; no local package or runtime is needed. OAuth authentication is required. No environment variables or headers are declared.
Before you install
The public endpoint is a synthetic demo, so its content is not real company data and results should not be treated as production answers. Real deployments are arranged by contract with the provider. OAuth grants the server access tied to your account, so review the scopes requested at sign-in.

Installation

In SourceWeft

  1. Open n3tz Atlas in the dashboard and add it to a workspace.
  2. Connect the required 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/ai.n3tz%2Fatlas/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "n3tz-atlas": {
      "type": "http",
      "url": "https://demo.atlas.n3tz.ai/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.1.2LatestOct 31, 2026
  2. v0.1.1Sep 16, 2026

Score

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

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.