Skip to content

Add Agents Shipgate to MCP resources - #4106

Closed
pengfei-threemoonslab wants to merge 1 commit into
modelcontextprotocol:mainfrom
pengfei-threemoonslab:codex/add-agents-shipgate-resource
Closed

Add Agents Shipgate to MCP resources#4106
pengfei-threemoonslab wants to merge 1 commit into
modelcontextprotocol:mainfrom
pengfei-threemoonslab:codex/add-agents-shipgate-resource

Conversation

@pengfei-threemoonslab

Copy link
Copy Markdown

This adds Agents Shipgate to the additional MCP resources list.

Why:

  • Agents Shipgate is a static release-readiness scanner for AI agent tool surfaces.
  • MCP exports are one of its supported inputs, alongside OpenAPI specs and agent framework artifacts.
  • This is a docs-only resource entry; it does not add CI or change any reference server implementation.

Trust model:

  • No agent execution.
  • No LLM calls.
  • No tool calls.
  • No MCP server connections.
  • No scanner network calls.
  • No telemetry.

I kept this intentionally small and placed it near related MCP discovery/security/scanning resources.

@localden

Copy link
Copy Markdown
Contributor

Thanks for the submission. We no longer accept server, resource, or tooling submissions to this repository; it is dedicated to the small set of reference servers maintained by the MCP steering group. To make your project discoverable, please publish it to the MCP Registry: https://registry.modelcontextprotocol.io/

@localden localden closed this Jul 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants