Skip to content

Would you be open to a read-only MCP compatibility check? #294

Description

@KryptosAI

Hi, I’m reaching out because neo4j-contrib/mcp-neo4j looks like an active MCP server where a lightweight compatibility/security check could be useful to maintainers and users.

I maintain MCP Observatory: https://github.com/KryptosAI/mcp-observatory. It is local-first and can run as a read-only GitHub Action to check MCP protocol compatibility, schema drift, and common schema/security footguns. No account or hosted service is required.

This project is a good candidate because database MCP servers benefit from explicit compatibility and schema-drift checks. If there is a safe fixture, local Docker, or no-secret startup path, Observatory can keep the workflow read-only.

I do not want to add noise here. If this is useful, I can open a very small PR that:

  • adds a read-only MCP Observatory workflow
  • uses the startup command you prefer
  • avoids secrets or destructive actions
  • keeps the check advisory if blocking CI would be too aggressive

I also opened a central maintainer thread here if you would rather coordinate there instead of this issue: KryptosAI/mcp-observatory#124

Totally fine to close this if it is not a fit. I’m asking first rather than sending a drive-by PR.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions