Skip to main content
Glama
134,894 tools. Last updated 2026-05-25 20:39

"A server for test coverage and MCP integration" matching MCP tools:

  • Test connectivity to an MCP server by sending a live check. Returns success, response time, HTTP status, and errors for diagnostics.
    MIT
  • Retrieve the capabilities exposed by an MCP server instance, including total counts and current tool, resource, and prompt surfaces. Use for server-specific exposure instead of integration-level lists.
    MIT
  • Retrieve an MCP server by ID or slug to get details including parent integration, status, and creation time. Use this to access the server record instead of the integration config.
    MIT
  • Create an MCP integration by registering an external server URL with Portkey. Returns the integration ID and slug; supports authentication via headers, OAuth, or none.
    MIT

Matching MCP Servers

Matching MCP Connectors

  • Alpic Test MCP Server - great server!

  • The PropelAuth Integration MCP Server helps you and your favorite AI agent integrate PropelAuth as quickly and easily as possible into your project. Whether you're integrating PropelAuth into your Next.js project or your FastAPI backend, the Integration MCP Server will ensure your AI agent has the best context possible for a successful integration.

  • Verify MCP server functionality by sending a message and receiving an immediate echo response. A simple test tool to ensure server communication is working correctly.
    MIT
  • Analyze test coverage to identify untested lines, functions, branches, and statements. Get actionable insights and recommendations for improving coverage, with automatic exclusion of non-production files.
    MIT
  • Discover test files matching .test.* and .spec.* patterns recursively. Get structured file info with absolute and relative paths to understand test organization and coverage. Optionally limit search to a specific directory.
    MIT
  • Test a specific MCP server before installing or after updating by launching it with a command, checking all capabilities, and saving a run artifact. Optionally invoke tools to verify execution and analyze schemas for vulnerabilities.
    MIT
  • Run a compiler smoke test to verify Axint installation and connection. Proves the agent performed real work beyond just starting the MCP server.
    Apache 2.0