ArchGraph

dev.archgraphPublished by archgraph.devOfficial publisherv1.0.0Updated Oct 24, 2026

Code intelligence platform for AI agents. 20 tools for architecture, security & impact analysis.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

ArchGraph is a remote code intelligence service that gives an AI assistant 20 tools for architecture, security and impact analysis.

What you can do
Analyze code architecture and structure through the hosted service's tools, which the manifest counts at 20 but does not name individually. Run security analysis over a codebase. Assess the impact of changes. The server is a remote endpoint, so the assistant connects to it rather than running anything locally.
When to use it
Useful when an assistant needs to reason about a codebase's architecture, check it for security issues, or estimate the impact of a change, without local tooling.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package or runtime is needed. An OAuth-based API key is required, sent in the Authorization header as a bearer token, obtained from the provider's dashboard.
Before you install
The required Authorization header carries a secret API key; keep it out of shared logs and configuration. The service analyzes your code, so source content is sent to a third party. The manifest does not list the individual tools, so review what each one does before use.

Installation

In SourceWeft

  1. Open ArchGraph 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/dev.archgraph%2Fmcp/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": {
    "archgraph": {
      "type": "http",
      "url": "https://mcp.archgraph.dev/mcp"
    }
  }
}

README

This repository has no README.

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

1
  1. v1.0.0LatestSep 16, 2026

Score

60% 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

    Declare a license in the repository or the registry entry.