# Published Server Not Appearing on github.com/mcp - Need Clarity

[Wolfe-Jam]

Pre-submission Checklist

• I have checked that this question would not be more appropriate as an issue in a specific repository
• I have searched existing discussions and documentation for answers

Question Category

• Protocol Specification
• SDK Usage
• Server Implementation
• General Implementation
• Documentation
• Other

Your Question

Published Server Not Appearing on github.com/mcp - Need Clarity

The Issue

I successfully published claude-faf-mcp to the MCP registry (v2.6.1 days ago, v2.6.2 today), but it hasn't appeared on github.com/mcp despite documentation claiming servers "automatically appear."

Server: io.github.Wolfe-Jam/claude-faf-mcp
Status: ✓ Successfully published (confirmed by CLI)
Result: Not visible on github.com/mcp

Quality Metrics

• ☑️ Anthropic-Approved (PR #2759, merged Oct 17)
• ☑️ 3,600+ npm downloads (800+ weekly)
• ☑️ 100% TypeScript strict mode - Zero errors
• ☑️ 730 C.O.R.E tests passing
• ☑️ Google-approved Chrome Extension

The Disconnect

GitHub's claim:

"Once published, those servers will automatically appear in the GitHub MCP Registry."
— GitHub Blog

Reality:

• 1,000+ servers in OSS registry (InfoQ)
• Only 26 showing on github.com/mcp (recently dropped from 44)
• No status check, no timeline, no contact method

Questions

1. Is github.com/mcp manually curated? Please clarify vs "automatic" claim
2. What are the selection criteria? Anthropic-approved (merged)? npm published? Downloads? Testing? Quality metrics?
3. How do we check status? Is our server under review?
4. Can we get feedback? What criteria are we missing?

Request

For claude-faf-mcp:

• Confirm registry publication status
• Clarify github.com/mcp inclusion status

For the ecosystem:

• Update docs to distinguish "published to registry" vs "shown on github.com/mcp"
• Publish transparent selection criteria
• Add status check mechanism

About claude-faf-mcp

MCP server for .faf format - first persistent "Project DNA" layer in MCP ecosystem. 33 tools for context scoring, bi-sync, and context-on-demand.

Links:

• GitHub: https://github.com/Wolfe-Jam/claude-faf-mcp
• npm: https://www.npmjs.com/package/claude-faf-mcp
• Anthropic PR: Add claude-faf-mcp to MCP servers registry servers#2759

---

Wolfe James | Creator, .faf Format
GitHub: @Wolfe-Jam | ORCID: 0009-0007-0801-3841

[rdimitrov]

Hey @Wolfe-Jam, thanks for reaching out! This issue seems better suited for GitHub’s MCP registry support team whereas this repo is for the upstream registry (which, as you mentioned, is working fine). Closing as out of scope.

[Wolfe-Jam]

Ok, thanks, I don't suppose you have a URL...