Add gyazo-mcp-server

[ishii-masaki-646]

MCP Server Information

Server Name: gyazo-mcp-server
Repository URL: https://github.com/ishii-masaki-646/gyazo-mcp-server
Brief Description: Unofficial but feature-rich Gyazo MCP server with MCP OAuth broker, streamable HTTP and stdio transports, image resources, and eight Gyazo tools.

Basic Requirements

• Open Source: Uses acceptable license (Apache-2.0, MIT, BSD-2-Clause, BSD-3-Clause or other permissive license)
• MCP Compliant: Implements MCP API specification
• Active Development: Recent commits and maintained
• Docker Artifact: Dockerfile
• Documentation: Basic README and setup instructions
• Security Contact: Method for reporting security issues

Submitter Checklist

• This server meets the basic requirements listed above
• I understand this will undergo automated and manual review.
• I have tested the MCP Server using go run ./cmd/validate --name gyazo-mcp-server
• I have built the MCP Server using go run ./cmd/build --pull-community --tools gyazo-mcp-server
• If the server requires credentials to test it, I have shared test credentials using this form

Notes

• This entry targets the Docker image ishiimasaki646/gyazo-mcp-server.
• It is positioned as an unofficial Gyazo server with broader feature coverage than the existing Gyazo entry, including MCP OAuth broker support, image resource access, and both HTTP and stdio transports.
• Registry validation and build checks pass without credentials:
  • go run ./cmd/validate --name gyazo-mcp-server
  • go run ./cmd/build --pull-community --tools gyazo-mcp-server
• Authenticated Gyazo operations require a Personal Access Token or OAuth credentials.
• A Gyazo Personal Access Token can be created from a Gyazo.com account, including a free account.
• I have not shared test credentials via the submission form at this time. If reviewer-side credentials are required, please let me know the preferred process.