Reach: ecosystem listings and launch channels (awesome lists, MCP directories, Show HN, releases)

[hexsecs]

Tracking issue for distribution work that isn't code. For a developer security tool, these channels likely matter more than classic search ranking.

Search engine submission (owner action — required for the sitemaps to be used at all)

GitHub project pages can't serve an authoritative robots.txt (crawlers only honor it at the host root, and hexsecs.github.io/robots.txt belongs to the user site, not this repo — see discussion on #485). So the sitemaps must be submitted directly:

• Verify the site in Google Search Console and submit https://hexsecs.github.io/canarchy/sitemap.xml and https://hexsecs.github.io/canarchy/docs/sitemap.xml
• Same in [Bing Webmaster Tools](https://www

[hexsecs]

Adding to the "Ongoing" list — surfaced during review of #485:

• Submit both sitemaps directly to search engines. On a GitHub project page the site is served from /canarchy/, so /canarchy/robots.txt is not at the host root and crawlers won't auto-discover its Sitemap: directives (Google treats subdirectory robots files as invalid). Submit https://hexsecs.github.io/canarchy/sitemap.xml and https://hexsecs.github.io/canarchy/docs/sitemap.xml to Google Search Console and Bing Webmaster Tools instead. (A custom domain served from the root would make robots.txt authoritative and remove this step.)

---

Generated by Claude Code

[hexsecs]

Starting work on #484; branch will be issue-484-launch-packet. The current issue body appears truncated mid-Bing link. I will prepare a source-checked distribution packet (listing targets/copy, runnable demo, search-engine and MCP submission prerequisites) and open a review PR. External submissions and account verification will remain explicitly pending.

[hexsecs]

Prepared launch packet in PR #511: #511

Verified: CANarchy already appears in Awesome Vehicle Security; no entry found in the Awesome MCP Servers README; PyPI 0.9.2 lacks the official registry ownership marker; both live sitemaps return valid XML. The pinned 0.9.2 hardware-free demo ran successfully.

Validation: 1,638 tests passed, 1 skipped, 293 subtests passed. Strict docs content build passed with social-card generation disabled only locally; the full build stalled during font processing and remains a CI gate.

Proposed remaining scope, reconstructed from the issue title because the original body is truncated:

• Review and merge docs: prepare ecosystem listings and launch packet #511.
• Verify Google Search Console and Bing ownership; submit both sitemaps and record fetch outcomes.
• Check Awesome MCP Servers prior PRs, then submit the prepared entry if appropriate.
• Add the MCP ownership marker in a release-scoped change, publish the package, then publish and verify the official registry entry.
• Review and post Show HN when available for discussion; record the thread URL.
• Use the announcement template for a selected published release and record its link, or explicitly defer that channel.

Awesome Vehicle Security is already covered; a description refresh is optional. No external submissions were sent. Keep #484 open until selected channels have submission evidence or an explicit decision to defer.

[hexsecs]

PR #511 merged as 3b9a135 following user approval. All nine executable PR checks passed, including the full docs build; PR deployment was correctly skipped. The launch packet is now on main. #484 remains open for the distribution submissions and account verification listed above.

[hexsecs]

Starting the authorized awesome-list submissions: refresh the existing Awesome Vehicle Security entry on branch canarchy-description-refresh, and submit CANarchy to Awesome MCP Servers after duplicate checks. The existing vehicle-security fork is accessible; no hexsecs/awesome-mcp-servers fork is currently accessible.

[hexsecs]

Awesome-list progress:

• Vehicle Security: prepared and pushed the single-line description refresh to hexsecs/awesome-vehicle-security:canarchy-description-refresh (573f61d3b71fb836e45d9d9a47201c6ae84f288f), based on current upstream master. Duplicate search found only original PR Update CAN-related resources in README.md jaredthecoder/awesome-vehicle-security#105.
• Opening the upstream PR was attempted, but GitHub returned HTTP 403: Resource not accessible by integration. No upstream PR was created. The ready branch can be submitted here: https://github.com/jaredthecoder/awesome-vehicle-security/compare/master...hexsecs:awesome-vehicle-security:canarchy-description-refresh?expand=1
• Awesome MCP Servers: current README contains no CANarchy entry, and the PR search found no prior CANarchy submission. Proposed destination: Security. No accessible hexsecs/awesome-mcp-servers fork exists, and this connection exposes no fork-creation action. Its upstream PR submission may also require manual action due to the integration restriction above.

Ready MCP entry:

- [hexsecs/canarchy](https://github.com/hexsecs/canarchy) 🐍 🏠 - Local MCP server for CAN capture analysis, J1939 workflows, and structured security research tools, backed by the CANarchy CLI.

Suggested PR title: Add CANarchy CAN bus research MCP server
Suggested body: Adds CANarchy to Security: a local Python MCP server backed by a CLI-first CAN security research toolkit, with J1939 workflows and structured JSON events. Checked the current README and prior pull requests for duplicates. Source and installation: https://github.com/hexsecs/canarchy

Both external submissions remain pending; the account integration limitation prevents completing them directly here.

[hexsecs]

The user created hexsecs/awesome-mcp-servers. Starting the listing change on add-canarchy; rechecked the upstream README and prior PRs with no CANarchy duplicates found.

[hexsecs]

The Awesome MCP Servers entry is now committed and pushed to hexsecs/awesome-mcp-servers:add-canarchy at 93bfd2466604101199666e19eb02516c445739d4. Validation confirmed exactly one new line, placed between the haruodev and hieutran entries in Security, with the rest of the README unchanged.

Attempting to open the upstream PR returned GitHub HTTP 403: Resource not accessible by integration. No upstream PR was created. Ready-to-submit comparison:
https://github.com/punkpeye/awesome-mcp-servers/compare/main...hexsecs:awesome-mcp-servers:add-canarchy?expand=1

Title: Add CANarchy CAN bus research MCP server

Body: Adds CANarchy to Security: a local Python MCP server for CAN capture analysis, J1939 workflows, and structured security research tools. Checked the current README and prior PRs for duplicates. Source and installation: https://github.com/hexsecs/canarchy . One entry added; existing entries unchanged. Prepared with coding-agent assistance and authorized by the CANarchy maintainer.

[hexsecs]

Confirmed the user submitted the Awesome MCP Servers listing: punkpeye/awesome-mcp-servers#13736 . The submission step is complete; upstream review/acceptance remains separate. Keep #484 open for the remaining distribution work. The optional Awesome Vehicle Security description refresh is still prepared in the fork; the search currently finds only the original #105 upstream.