GitDiagram
REMOTE · GITDIAGRAM.COM · SCANNED OCT 4
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 740 tokens (~185/item across 4 items; 3 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
How do I install the GitDiagram MCP server?
GitDiagram is a hosted endpoint at https://gitdiagram.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · gitdiagram.com
claude mcp add --transport http com-gitdiagram-gitdiagram 'https://gitdiagram.com/mcp'
{
"mcpServers": {
"com-gitdiagram-gitdiagram": {
"url": "https://gitdiagram.com/mcp"
}
}
} {
"servers": {
"com-gitdiagram-gitdiagram": {
"type": "http",
"url": "https://gitdiagram.com/mcp"
}
}
} [mcp_servers.com-gitdiagram-gitdiagram] url = "https://gitdiagram.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-gitdiagram-gitdiagram": {
"type": "remote",
"url": "https://gitdiagram.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-gitdiagram-gitdiagram --url 'https://gitdiagram.com/mcp' --transport streamable-http
mcp_servers:
com-gitdiagram-gitdiagram:
url: "https://gitdiagram.com/mcp" {
"McpServers": {
"com-gitdiagram-gitdiagram": {
"Transport": "http",
"Url": "https://gitdiagram.com/mcp"
}
}
} assistant mcp add com-gitdiagram-gitdiagram -t streamable-http -u 'https://gitdiagram.com/mcp'
{
"mcpServers": {
"com-gitdiagram-gitdiagram": {
"type": "http",
"url": "https://gitdiagram.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- Tool “find_repository_diagrams” rewrote its description, which is the text the model reads security
- Tool “get_repository_diagram” rewrote its description, which is the text the model reads security
- Schema quality: 238 → 185 ▲ functional
- Stability: unverified → 0.03 ▲ functional
- The server now declares the “resources” capability functional
- First check of Capabilities: pass functional
- First check of Schema quality: 100 functional
- New resource “GitDiagram diagram view” functional
- 29 Sept 26 73
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Oct 2026 · Probed https://gitdiagram.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=gitdiagram.com | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 43e535c214a146dd13d7965bc4b4e216 |
| SANs: gitdiagram.com, preview.gitdiagram.com, *.preview.gitdiagram.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of gitdiagram.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| gitdiagram.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob:; font-src 'self' data:; connect-src 'self' wss://gitdiagram-presence.gitdiagram-presence.workers.dev; worker-src 'self' blob:; frame-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gitdiagram.com/mcp | Verified | 200 | |
| http (plaintext) | http://gitdiagram.com/mcp | HTTPS enforced | 301 | https://gitdiagram.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_repository_diagrams Search GitDiagram's architecture diagrams ~170
Search GitDiagram's library of ready-made architecture diagrams of public GitHub repositories by owner or repository name. Matches any part of "owner/repo" (e.g. "langchain", "vercel/", "react-native") and returns up to 10 repositories, most-starred first, each with its interactive diagram link. Use it to find a project's exact owner/repo from its name, or to list which repositories of an owner or topic already have diagrams. It searches repository names only, not code or file contents.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many repositories to return (1–10, default 10). |
| query | string | yes | Part of a repository's "owner/repo" name, e.g. "fastapi", "microsoft/", or "next.js". |
No output schema declared.
No examples provided.
get_explainer_video Get a GitHub repository's explainer video ~185
Get GitDiagram's narrated explainer video of a public GitHub repository, if one has been made: the link to watch and share it, its title and length, and the full narration transcript, a plain-language walkthrough of what the project is for, what people do with it and how its main parts fit together. Use it when the user wants a video about a repository, something to watch or share instead of read, or a short spoken-style summary of a project. Read-only: it never makes a video; when none exists it says so and links the page where one can be made.
| Name | Type | Req | Description |
|---|---|---|---|
| repository | string | yes | The GitHub repository as "owner/repo" (e.g. "fastapi/fastapi") or any github.com URL inside it (e.g. "https://github.com/vercel/next.js/tree/canary/packages"). |
No output schema declared.
No examples provided.
get_repository_diagram Get a GitHub repository's architecture diagram ~252
Get the architecture of a public GitHub repository from GitDiagram (gitdiagram.com): a written explanation of how the codebase is organized, its main components with the source paths they live in, how those components connect, and a Mermaid flowchart of the whole system, plus a link to the interactive diagram, where every component opens its code on GitHub. Use it whenever the user wants to understand, visualize, map or explain a GitHub repository's or open-source project's architecture, structure, main modules or data flow, wants an overview before reading unfamiliar code, or asks for an architecture or system diagram of a repo. Read-only and fast: it returns the diagram GitDiagram has already made. If none exists yet, it returns a link that makes one when opened in a browser. Public repositories only. In chat apps that show interactive views, the result also appears as a zoomable diagram whose components open their code on GitHub.
| Name | Type | Req | Description |
|---|---|---|---|
| repository | string | yes | The GitHub repository as "owner/repo" (e.g. "fastapi/fastapi") or any github.com URL inside it (e.g. "https://github.com/vercel/next.js/tree/canary/packages"). |
No output schema declared.
No examples provided.
What is the GitDiagram MCP server?
GitDiagram is an MCP server listed in the public MCP registry as com.gitdiagram/gitdiagram. Architecture diagrams, explanations and Mermaid source for public GitHub repositories. This page covers its hosted endpoint (https://gitdiagram.com/mcp).
Is the GitDiagram MCP server safe to use?
GitDiagram scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the GitDiagram MCP server expose?
GitDiagram exposes 3 tools: get_repository_diagram, find_repository_diagrams, get_explainer_video. Their descriptions and schemas cost roughly 607 tokens of context every time the server is loaded.
Does the GitDiagram MCP server require authentication?
No. We connected to GitDiagram without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the GitDiagram MCP server still maintained?
GitDiagram is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.