"Systems or platforms that support dynamic registration" matching MCP servers:

Enables creating release manifests and verifying that local release folders or public HTTPS bytes match the manifest, using read-only MCP tools.

Provides a read-only tool to check Wrangler configuration files for common mistakes before deployment, supporting environment selection and strict mode.

Generates a daily standup note from GitLab merge request or GitHub pull request state: what is ready to merge, what is blocked, what is stale, and what is waiting on your review. When CI is red it opens the failed job's log and reports the error lines, so the note says why the pipeline failed rather than just that it did.

Enables AI agents to deploy static files and get live HTTPS URLs instantly, with support for custom domains and data residency.

Security auditor for CI ecosystems that detects supply-chain and injection flaws in CI/CD configuration files across seven CI platforms, providing taint analysis, remediation, and compliance scoring.

Model Context Protocol (MCP) server for GitLab — exposes 1006 GitLab REST & GraphQL API operations as MCP tools (42 meta-tools / 57 enterprise), 24 resources, 38 prompts, and 17 completion types for AI assistants. Written in Go, single static binary, stdio and HTTP transport.

An MCP server that enables AI assistants to discover and execute Nox sessions for project automation tasks like testing, linting, and building. It provides tools to list available sessions and run them using specific Python versions, tags, or keyword expressions.

Enables AI coding tools to validate local projects and publish or update applications to Bedengan App Hub via API, with automated checks and live deployment without manual approval.

Enables code-review gating by converting a git diff into a typed verdict with safety probabilities, severity, and recommended actions for auto-merge or human review.

Deploys and manages projects on Swigs Cloud from any MCP client, turning folders or git repositories into live HTTPS sites in about two minutes.

A Model Context Protocol server that enables AI assistants to interact with Azure DevOps services, allowing users to query work items with plans to support creating/updating items, managing pipelines, handling pull requests, and administering sprints and branch policies.

Enables AI agents to query summit registration and forum analytics, review code changes for risks, run fixed quality gates, and perform audited, permission-controlled commits and deployments with minimal access and human approval.

Enables coding agents to upload local .apk or .ipa builds and receive tester install links without leaving the editor.

Publishes what an AI made — a page, a markdown or PDF doc, or a whole site — to a live HTTPS link. Runs locally over stdio from the @drop2run/mcp npm package, or hosted at https://mcp.dropto.run/mcp for chats that connect by URL.

An MCP server that enforces disciplined Git workflows by planning coding tasks into small, test-gated commits, ensuring tests pass before staging and preventing out-of-scope or oversized changes.

Checks whether software dependencies (npm packages, GitHub Actions, MCP servers, Docker images) are alive, dormant, abandoned, archived, or deleted using dated observations from lastseen.dev.

MCP server that lets coding agents test AI agents. Create YAML test cases, snapshot golden baselines, check for regressions, and generate visual reports all from inside Claude Code or any MCP-compatible tool. Works with LangGraph, CrewAI, OpenAI, Claude, Mistral, and any HTTP API.

MCP server that automates the publishing and validation of Tableau workbooks and data sources on Tableau Server or Tableau Cloud, enabling an AI agent to discover, build, validate, and publish content without human intervention.

Browser acceptance testing for AI agent deliverables: verify agent output in real Chromium from JSON specs, with MCP server, visual regression, multi-browser support and GitHub Actions.

Enables agents and CI pipelines to audit MCP servers and agent tool-chains by statically scanning repositories, local checkouts, tools/list exports, or live endpoints for risks such as destructive actions without confirmation, mismatched safety annotations, injection surfaces, credential or PII exposure, and unguarded command, path, or URL sinks. All checks are read-only and never execute the scanned code or call tools/call.