"A server for finding information about search engines" matching MCP servers:

Enables interaction with Azure DevOps through natural language in Cursor IDE. Supports work item management, pull requests, builds, releases, test management, and guided workflows for development teams, QA testers, and release management.

A Model Context Protocol server implementation that allows AI models to interact with and manage Spinnaker deployments, pipelines, and applications through a standardized interface.

Checks the outcome after an agent handoff, when a request, 200 or ack only shows the handoff. Reads one field of one exact public HTTPS JSON record, with a same-site known-good control, for 20-120 s. Returns PROVED, DISPROVED or INCONCLUSIVE with a signed receipt you can verify. 5 free checks, then USD 1 per completed check, by card (Stripe Checkout) or existing Link wallet. INCONCLUSIVE is free.

Integrates Cline with Azure DevOps services, enabling access to work items, repositories, and pull requests through configurable MCP tools.

Provides AI assistants with comprehensive access to Azure DevOps services including work items, repositories, pull requests, wikis, builds, pipelines, and test plans through 25+ MCP tools with multi-project support.

Provides a standardized way for MCP clients to interact with Apache Airflow's REST API, supporting operations like DAG management and monitoring Airflow system health.

Provides ChatGPT read-only access to inspect repositories, code, merge requests, pipelines, and CI logs on self-managed GitLab instances, including those reachable only from a private network or VPN.

. A good description should be concise and describe what the server enables users to do, e.g. * Enables to interact with WordPress sites...' Then a huge block? Actually the user message includes the README content inside tags, then after the readme, there is a large block of text starting with '{

Enables comprehensive GitHub workflow automation including Actions monitoring, PR management, code search, file operations, and repository management through a code-first architecture that reduces token usage by 98%.

Enables AI assistants to interact with Argo CD applications, managing clusters, applications, and resources through natural language.

Provides integration with Apache Airflow's REST API, allowing AI assistants to programmatically interact with Airflow workflows, monitor DAG runs, and manage tasks.

MCP server that enables AI assistants to manage Azure DevOps resources including Work Items, Git repositories, pipelines, and user identities.

A remote MCP server that provides AI agents access to the Rootly API for incident management, allowing users to query and manage incidents, alerts, teams, services, and other incident management resources through natural language.

A Model Context Protocol server for checking package versions and metadata across multiple package managers including npm, PyPI, Maven, NuGet, RubyGems, Crates.io, and Go modules.

SSWP MCP — Deterministic software attestation for AI-augmented development. Witness any repo through a 5-gate pipeline, adversarially probe dependencies, and produce self-verifying .sswp.json attestations. Fleet registry across 131 nodes with tamper-proof audit ledger and FTS5 search. Agent-native — one tool call from Hermes, Claude, or Cline.

Detects breaking changes in a TypeScript library's public API and recommends the semver bump, comparing two npm releases, git refs or a working tree. Each finding is graded proven or review-only.

Record an agent's MCP tool-call workflow once, replay it deterministically for zero tokens, and get a receipt — a snapshot-testing and deterministic-execution layer for Agent Skills.

Provides disposable email inboxes for AI agents to automatically receive and extract OTPs and magic links, enabling seamless email verification during autonomous workflows.

A Model Context Protocol server for Bitbucket Cloud that lets agents read pull request diffs, comments, and pipeline logs, as well as write PR comments and edit PR details.

A Model Context Protocol server that monitors shadow-cljs builds and provides real-time build status updates for ClojureScript projects, allowing LLMs to verify build status after making code changes.

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.

Publishes normalized release notices to a configured webhook via MCP, with built-in validation, deterministic dry-run mode, and a clear boundary for authority gates.

A reference MCP server for observing Vercel projects and deployments over stdio. It provides read-only tools to list and fetch details of Vercel projects and deployments.

A CircleCI MCP server specialized in config review, providing tools for fetching actual configs, validating changes, and analyzing workflow bottlenecks, health, and DAG dependencies.

Aegis keeps Claude Code, Codex CLI and Antigravity on your project's rules via a zero-dependency Model Context Protocol (MCP) server (aegis-mcp), AGENTS.md / CLAUDE.md bootstrap, git pre-commit hooks, and CI governance (aegis check). It serves each agent just-in-time rules for the files it is about to edit, then enforces AST and repository invariants before commit and in pull requests.

Enables MCP clients to read a Forgejo, Codeberg, or Gitea instance—including users, repositories, issues, pull requests, search, notifications, comments, reviews, and Actions runs—with opt-in, time-boxed guarded writes for repository, branch, issue, pull request, comment, migration, push-mirror, and workflow operations.

Enables reviewing GitHub Actions workflows for outdated actions, deprecated Node runtimes, retired runners, deprecated commands, and security risks, with file, line, and fix for each finding.

MCP server that analyzes GitHub Actions workflow performance, audits configuration for optimization, and provides billing and cache usage insights.

Turns JUnit XML test reports from CI into queryable QA metrics, letting AI assistants answer plain-English questions about failures, flaky tests, regressions pinned to a commit, root-cause clusters, and performance drift. Also generates ready-to-share QA health reports and self-contained HTML dashboards without logging into separate tools.