GitHub
by github
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Computer or cloud★ 34,245MITUpdated 3 days ago
Install
Span
Overview
Description from the maker (original English)
Codebase understanding with exact evidence, qualified on every read and re-aligned on change.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Developer tools
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- PyPIPython’s uv installed (for the uvx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"span": {
"command": "uvx",
"args": [
"span-mcp"
]
}
}
}Run this in your terminal
claude mcp add span -- uvx span-mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"span": {
"command": "uvx",
"args": [
"span-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"span": {
"type": "stdio",
"command": "uvx",
"args": [
"span-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account pontivus-com, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Developer toolsi
- More stars than 0% of the other 1389 servers in this category
- Published to the registry more recently than 94% of the other 1389 servers in this category
- Basic checks equal to or better than 100% of the other 1389 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Span safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.9.4) reached the registry 2 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
What can I use instead?
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Desktop Commander
by wonderwhy-er
MCP server for terminal commands, file operations, and process management
Runs on your computer★ 10,225MITUpdated 15 days ago
Install
Cloudflare MCP
by cloudflare
Cloudflare MCP servers
Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Carry useful investigations into the next coding session.
Span keeps the explanations your coding agent worked out, the evidence behind them, and what needs another look when that evidence changes.
Quick start · How it works · Docs
Keep the understanding your agent worked for
A coding agent traces a request across services, checks the tests, finds the contract, and explains why the boundary exists. The next session should be able to find that explanation and see whether its support still holds.
Span makes that investigation reusable. It is a local MCP server where agents record coherent explanations with exact source support, explicit gaps, and version history. Later agents can discover the explanation through an ordinary engineering question, then inspect what is current, disputed, or changed.
The coding agent does the thinking. Span keeps the record and checks its support.
Three tools — ask, record, reconsider — carry one lifecycle: find current understanding, retain a supported conclusion, and re-align after change.
How it works
- Investigate a real question. Ask about the surface you are looking at. Span returns current answers with surface status, or a gap with inspectable source evidence.
- Record the useful result. Save one conclusion at a time with the file it rests on, or declare a service/domain surface for a cross-file explanation. Work that started outside Span can be recorded directly; the flat create derives support from the locator you already read.
- Reuse in a fresh session. Ask the same question about the same surface, and retrieve the result with live support and challenges.
- Reassess after change. Check affected dependencies, investigate what changed, then confirm, correct, replace, or withdraw the explanation. Earlier versions remain inspectable.
One explanation can span code, tests, CSS, configuration, and contracts. The agent decides what is worth recording; a file inventory does not become a mandatory documentation campaign.
See the lifecycle
Illustrative tool sequence, not literal request JSON. The installed schemas and MCP reference own the wire grammar.
ask: "How does checkout decide whether to charge?"→ Gap: exact evidence, a context, and an explicit question
agent investigates; record admits the source it just read
record(kind="understanding", conclusion, locator) → committed receipt, understanding version 1, support qualification
fresh session asks the same question about the same surface → Answer with current conclusions, evidence, and surface status ask(selector=UnderstandingSnapshotSelector) → recorded explanation, live support, gaps, and challenges
supporting source changes reconsider(changed_paths) → every affected surface, with containment, direct, and indirect reasons, and per-conclusion support state
agent investigates and records a correction against the expected version → version 2; version 1 remains history
A query names the surface; saved understanding is matched by that surface and the recorded question. Wording is not treated as semantic equivalence, and a returned conclusion is a starting point for judgment.
Know what can be reused
| Qualification | What the agent can conclude |
|---|---|
CURRENT | The declared support still passes its checks. Applicability and semantic correctness still need judgment. |
REASSESSMENT_REQUIRED | Source, authority, premise, or recorded membership support changed. Revisit the affected explanation. |
UNVERIFIABLE | Required support cannot be established. The limitation stays explicit. |
Gaps and challenges remain visible independently of support currency. Matching bytes do not settle a dispute, and test existence does not establish a pass. Independent verification records the observations or evidence actually tested and preserves failures as failures.
Recording is atomic and returns a receipt. The caller preserves identity before sending; retrying the same identity and content recovers the retained receipt after a lost response or process restart. A committed receipt and a present support qualification answer different questions.
Quick start
The verified installation path is Linux with Python 3.12+, Node.js, and npm. From a checkout containing the current candidate:
python3 scripts/install-span.py --repo /path/to/your/repoFor a published package release, install span-mcp with your Python package manager and run span-install --repo /path/to/your/repo. See install and connect for registration, verification, and the offline store transition.
The installer provisions the managed structural indexer, runtime, skills, and host integration. With the default global OpenCode scope, it registers the Span lifecycle plugin and MCP server in the same global OpenCode configuration. Repeat installs use the receipt's absolute MCP path unless --opencode-config explicitly relocates it. Reconnect your coding agent after upgrade so it receives the new tools and instructions. Verify operational setup with:
span-install --verify-onlySetup creates no understanding. Begin with a question from your actual task; see using Span.
Beta host status
| Host | Current scope |
|---|---|
| Codex | Supported; three-tool delivery captured with hooks disabled. The flat-create re-capture is pending (account quota). |
| OpenCode | Supported; three-tool and flat-create delivery captured. The installer plugin puts the first ask before the first source read in 5/5 measured runs. |
| Claude Code | Supported managed host; registration/health and installer behavior are covered. Authenticated model-delivery grammar and caller identity remain UNVERIFIED. |
| Other MCP hosts | Manual stdio connection is available; model-delivery behavior needs host-specific verification. |
Registration, hook configuration, and model-delivered behavior are distinct. Optional hooks provide notices; retrieval and recording still check support when hooks are absent. See host integration.
Fits around your agent
Span runs locally over stdio and keeps state outside target repositories. Your agent uses its own model, tools, edits, and test runner. Span does not invoke a model or store provider credentials. Structural search helps investigation; recorded conclusions retain the agent's interpretation and declared support.
The intended benefit is continuity between sessions and a focused review of changed support. Recording and host delivery have costs. Measured cost is class-specific: repeated reuse of a covered surface breaks even at two uses on the tested tasks, while single-use implementation is currently more expensive than reading. This beta makes no universal time/token-saving claim or completed comparative product-fitness ACCEPT claim. See acceptance.
Status and documentation
This checkout describes 0.9.4: three lifecycle tools (ask, record, reconsider), schema-11 storage, surface-scoped answers, explicit store transition, and live support qualification. 0.9.4 is a bug-fix release over 0.9.2: it shares the selected OpenCode configuration between MCP registration and global plugin wiring, makes verification and uninstall receipt-backed, including receipt-bound repositories during bare verification, restores Claude Code as a supported managed host, and removes superseded MCP, receipt, target-plugin, host-contract, and structural-indexer compatibility paths. --no-hooks disables lifecycle hook and plugin wiring without disabling MCP registration; current receipts fail closed and foreign host state remains untouched. The 0.9.2 release history is recorded in the changelog; its migration behavior is not a current 0.9.4 implementation promise. The current installer preserves the selected OpenCode configuration and does not perform obsolete target-plugin compatibility migration. Host delivery is captured for the three-tool surface on Codex and OpenCode; Claude registration/health and installer behavior are covered, while its authenticated model-delivery grammar and caller identity remain UNVERIFIED. The flat-create re-capture passes on OpenCode and is pending on Codex (account quota). Comparative fitness remains class-scoped (FD-53, FG-7). macOS and Windows installation paths remain unverified. Publication and product acceptance are separate from the implementation version.
- Install and connect
- Using Span and first investigation
- Agent lifecycle and MCP reference
- Support and reassessment
- Evidence and authority
- Scope and boundaries and FAQ
- Architecture, repository overview, and all docs
- Changelog
Older acceptance evidence retains its historical protocol and does not certify the rebuilt API or comparative value.
Contributing
See contributing. Preserve the central contract: useful understanding stays attached to its support, noncurrent or uncertain state stays explicit, and corrections preserve history. Security reports go through SECURITY.md; support expectations are in SUPPORT.md.
Registry
Official MCP Registry entry: io.github.pontivus-com/span
mcp-name: io.github.pontivus-com/span
License
Span is licensed under Apache License 2.0 (Apache-2.0). See LICENSE.