Skip to main content
Glama
Grativy6

SeedPEA MCP Adapter

by Grativy6
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to SeedPEA MCP Adapter

No user-submitted related servers found.

    Related Servers

    • mcp-jsonschema

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Validates JSON values against JSON Schema (draft-07). Enables schema validation for structured data.
      4 npm
      MIT

    • repo-verifier

      stsepelin
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides MCP tools for local code validation with execution evidence, enabling users to run planned checks on projects and receive JSON results that distinguish passing, failing, and incomplete outcomes.
      467 npm
      MIT

    • dsh-duty-separation-proof

      dongsheng123132
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables offline verification that a supplied DSH workflow adhered to declared duty-separation constraints, producing a redacted, content-addressed JSON verdict.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of the PEA/SEED declaration inspection process: authority separation, evaluator grants, release envelopes, and institutional branch registration. The descriptions clearly differentiate the purpose of each tool, so an agent would not confuse them.

    Naming Consistency5/5

    All tool names follow a consistent pattern of verb_object_json, using either 'inspect' or 'review' as the verb followed by the specific domain object. This is a uniform and predictable naming convention.

    Tool Count4/5

    With 4 tools, the set is compact and focused on a specialized inspection domain. The count is appropriate for the narrow scope, though slightly minimal but not insufficient.

    Completeness4/5

    The tools cover four key inspection areas within the PEA/SEED domain, providing a coherent surface for non-authorizing inspections. There might be additional inspection scenarios not covered, but the set appears reasonably complete for its stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources