Skip to main content
Glama
PAARA Connector Audit

PAARA Connector Audit

Related Servers

Alternatives to PAARA Connector Audit

  • A
    license
    A
    quality
    B
    maintenance
    A stdio MCP server that audits other MCP servers over the live protocol. It connects to any MCP target (stdio or HTTP), lints every tool's schema for agent-usability, then actually calls the tools with deliberately broken inputs to see how the server handles them, and returns a 0–100 conformance score with a per-dimension breakdown rendered as Markdown.
    6
    6
    MIT

Related Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Read-only MCP tools over an AgentFox control plane: agents found in a codebase, the tools and MCP servers each can reach, security findings, policy linting and simulation, and audit verification. 25 tools, none changing enforcement; implemented in src/agentfox/apps/mcp_server.py as JSON-RPC 2.0 over stdio on the standard library, with no MCP SDK dependency.
    227 PyPI
    4
    Apache 2.0
  • A
    license
    Not graded
    quality
    B
    maintenance
    Runs the MCP initialize handshake and validates tools/list JSON schemas on any public MCP server, and inspects x402 payment endpoints. Ships as a stdio MCP server the agent calls directly, plus a CLI and a GitHub Action. Read-only, no API key needed.
    141 npm
    MIT
  • F
    license
    A
    quality
    C
    maintenance
    An MCP server that exposes governance, trust-scoring, compliance, guardrail, cost, drift, and supply-chain scanning tools and resources to any MCP client over stdio, Streamable HTTP, or legacy HTTP+SSE. It lets agents route every tool call through a deterministic five-way decision (allow, redact, require approval, deny, or quarantine) with hash-chained evidence, human approval workflows, and in-agent trust gates for LangChain, LangGraph, and Google ADK.
    30
    -
  • A
    license
    Not graded
    quality
    D
    maintenance
    MCP server that produces scored, evidence-cited audits of public GitHub repos via tools for fetching metadata, reading files, scanning git history, and checking hygiene.
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    MCP server for a compliance knowledge graph covering 686 frameworks, 21,696+ controls and 310K+ cross-framework mappings, with tools to map controls between two standards and run coverage analysis. Node and Python implementations over stdio, plus a hosted streamable HTTP endpoint.
    MIT

TDQS

A3.8/5.0

Scored across 3 tools

Disambiguation4/5

The three tools map to distinct operations: score_connector computes a new score from supplied codes, lookup_connector retrieves a single named connector, and list_connectors returns the full set. lookup vs list overlap in that both return stored audit data, but the singular/plural split and explicit 'one of the 13' vs 'list the 13' wording makes selection clear.

Naming Consistency5/5

All three names follow a strict verb_noun snake_case pattern (score_connector, lookup_connector, list_connectors). The verbs are conventional CRUD-style/read-style verbs applied uniformly to the same noun, so the pattern is fully predictable.

Tool Count4/5

Three tools is on the thin side, but the domain is deliberately narrow: a fixed rubric applied to a 13-connector published audit. Each tool earns its place (compute, retrieve one, enumerate all), so the surface is well-scoped rather than padded.

Completeness4/5

The core lifecycle is covered: enumerate the corpus, look up an entry, and score a connector with the seven-factor rubric including restricted-band handling. Minor gaps exist — no tool to explain or validate the F1-F7 code semantics independently, and no comparison of multiple connectors — but agents can work around these by using score_connector directly.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues