Empty the footer of outbound links, and fix the registry listing - #44
Merged
Merged
Conversation
The footer now links nowhere off-site -- not to third parties, and not to our own properties either. The gateway link stays in the header, which is where it was asked for. - Drop the gateway and analytics links from the footer columns - Keep the analytics credit as plain text, because attribution is still owed and wanted; it does not need to be a sitewide link to be paid - Put "Publish a server" in the Project column so it is not left with one item - Point server.json at lbesecker195/MCP_Registry instead of the HoneyTrap clone, and bump to 1.0.1 so the corrected metadata republishes The listing is the first thing anyone evaluating this server reads, and it was sending them to an abandoned repository. The server is already active in the official MCP Community Registry, which is the documented route into GitHub's registry, so this corrects an existing listing rather than creating one. --- Pages affected: - [MCP Registry](https://ai.mcpharbor.dev/) — home page carrying the revised footer. - [Browse MCP servers](https://ai.mcpharbor.dev/servers) — catalogue of Model Context Protocol servers. - [MCP endpoint](https://ai.mcpharbor.dev/mcp) — the endpoint the registry listing points at. - [Agent instructions](https://ai.mcpharbor.dev/llms.txt) — plain-text guide for agents. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #43.
Footer
No outbound links remain — not to third parties, not to our own properties. A test asserts the allowed-host list is empty, so any future one fails the build.
gateway.mcpharbor.dev(For agents column)seriouslysimpleanalytics.com(Project column)seriouslysimpleanalytics.com(bottom bar link)The analytics credit stays as text deliberately: attribution is still owed and still wanted, it just does not need to be a sitewide link to be paid. Say the word if you want the sentence gone too.
Publish a serverfills the Project column so it is not left with a single entry.One conditional exception remains: the DB-IP credit, which is a CC BY 4.0 licence condition and renders only while that geo database is loaded. Geo blocking is off, so it renders nowhere today.
Registry listing
server.jsonwas publishingrepository.urlashttps://github.com/lbesecker195/HoneyTrap, subfoldermcp_registery— the stale clone. The canonical repo islbesecker195/MCP_Registryat its root. That URL is what the official registry and GitHub's registry both surface to anyone evaluating the server, so it was sending them to an abandoned repository.Corrected, and bumped to
1.0.1so the publish job republishes it.On github.com/mcp
No submission is needed — it is already registered. The server is published and
activein the official MCP Community Registry (since 2026-09-18), and GitHub's own announcement states that servers self-published there "will automatically appear in the GitHub MCP Registry". GitHub's surface has no separate submission form; it ingests from the community registry.Two things worth your call, neither changed here:
io.github.lbesecker195/mcp-registry-search-find-mcp-servers-discover-install-mcp-tools-directory-catalog-marketplace. Your own book argues against exactly this — long names that feel clever until lookups fail. Renaming means retiring the current identity and republishing under a new one, which is disruptive, so I have not done it unilaterally.96 tests pass.
Pages affected:
🤖 Generated with Claude Code