5 Pull requests merged by 3 people

• feat(database): support SeedFile import for memory database

  #128 merged Jun 6, 2025

• feat(config): specify to use in-memory database

  #74 merged Jun 4, 2025

• Rename mcp.json to server.json

  #106 merged Jun 3, 2025

• fix: make repository optional in openapi spec

  #119 merged Jun 3, 2025

• chore(docker-compose): enhance environment variable configuration using interpolation

  #78 merged Jun 2, 2025

1 Pull request opened by 1 person

• Corrected the Open API spec

  #120 opened Jun 3, 2025

8 Issues closed by 3 people

• Support SeedFile import for memory database

  #127 closed Jun 6, 2025

• Add a mode key in ServerDetail Object

  #117 closed Jun 5, 2025

• Python Implementation of the Registry?

  #121 closed Jun 5, 2025

• MySQL Support

  #122 closed Jun 5, 2025

• allow running registry with in-memory database

  #63 closed Jun 4, 2025

• Rename mcp.json to server.json

  #86 closed Jun 3, 2025

• Should `repository` be required on Servers?

  #111 closed Jun 3, 2025

• Unable to get `tools/publisher/main.go` to work

  #52 closed Jun 2, 2025

6 Issues opened by 4 people

• in-memory database functionality does not include seeding

  #129 opened Jun 5, 2025

• Add support for .NET / NuGet based MCP servers

  #126 opened Jun 5, 2025

• Allow engine or runtime version to be expressed for local MCP servers

  #125 opened Jun 5, 2025

• Support an array of commands (multiple commands) to start an MCP server instead of just one

  #124 opened Jun 4, 2025

• Server Detail should provide a well-defined method to automate server execution

  #123 opened Jun 4, 2025

• Add a Tags (or labels) key in ServerDetail object

  #116 opened Jun 2, 2025

22 Unresolved conversations

Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.

• Automated test suite that covers publication of a range of server formats

  #105 commented on Jun 5, 2025 • 0 new comments

• Allow a reverse-publication flow

  #104 commented on Jun 5, 2025 • 0 new comments

• Observability and alerting infrastructure

  #102 commented on Jun 5, 2025 • 0 new comments

• Daily re-verification of DNS records

  #100 commented on Jun 5, 2025 • 0 new comments

• Allow blacklisting GitHub users, organizations, or DNS namespaces

  #98 commented on Jun 5, 2025 • 0 new comments

• Sanitization, limits, enums on all free-form fields

  #97 commented on Jun 5, 2025 • 0 new comments

• Validate that submitted server.json's are referencing valid source code registries

  #96 commented on Jun 5, 2025 • 0 new comments

• Automatically remove server.json entries referencing invalid packages

  #93 commented on Jun 5, 2025 • 0 new comments

• Set up deployment infrastructure

  #91 commented on Jun 5, 2025 • 0 new comments

• Document server.json

  #90 commented on Jun 5, 2025 • 0 new comments

• Documentation for go-live

  #89 commented on Jun 5, 2025 • 0 new comments

• Bridge the "docs" OpenAPI spec with the actual OpenAPI implementation

  #87 commented on Jun 5, 2025 • 0 new comments

• Allow for vendor extensions to registry API

  #81 commented on Jun 5, 2025 • 0 new comments

• Provide clear guidance on avoiding security problems with `template` type package arguments

  #41 commented on Jun 5, 2025 • 0 new comments

• OAuth Config (Optional) for Remotes

  #25 commented on Jun 5, 2025 • 0 new comments

• Enforce some daily publish limits

  #21 commented on Jun 5, 2025 • 0 new comments

• Entry Criteria

  #31 commented on Jun 5, 2025 • 0 new comments

• Community-driven mechanism for takedown of spam/malicious servers

  #92 commented on Jun 6, 2025 • 0 new comments

• DNS-based server name verification

  #85 commented on Jun 6, 2025 • 0 new comments

• fix: fix missing seed.json on startup by renaming file

  #75 commented on Jun 4, 2025 • 0 new comments

• feat(health): enhance health check to report database connection status

  #109 commented on Jun 8, 2025 • 0 new comments

• fix: resolve registry image conflict in docker-compose

  #114 commented on Jun 8, 2025 • 0 new comments