Repository references point at the org repo
Metadata only. No tool, schema or behaviour changes — 1.11.1 is functionally
identical to 1.11.0.
VirtualFlyBrain/VFB3-MCP is the standalone home of this project.
Robbie1977/VFB3-MCP is archived at v1.3.0 and should not be cloned or linked.
Every in-tree reference now points at the org repo:
README.md,TECHNICAL.md— clone instructionssrc/index.ts— the "Full Documentation on GitHub" link on the landing pagepackage.json—repository.url,bugs.url,homepageserver.json—repository.url, andrepository.idcorrected from
1150713920to1151949164
Why this needs a tag
publish-mcp.yml runs on v* tags only. Until something is tagged, the MCP
registry listing keeps serving the old repository block, which points users
and security reviewers at an archived repo.
The repository.id matters more than it looks: the registry treats a changed
id as evidence of repository resurrection — a repo deleted and recreated under
the same name. Publishing under the archived repo's id misrepresents where this
server's source actually lives.
Registry authentication is unaffected. publish-mcp.yml logs in by DNS domain
(virtualflybrain.org), not by GitHub repo ownership.
Full changelog: v1.11.0...v1.11.1