Skip to main content
Glama
ShieldLabs-ai

@shieldlabs-ai/mcp

Official

Related Servers

Alternatives to @shieldlabs-ai/mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Exposes three read-only tools over stdio — guarded SQL querying, SKU status lookup, and document retrieval — plus a schema resource. This lets MCP clients such as Claude Code answer stock and policy questions without any write access.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients such as Cursor and Claude Desktop to query a GRC platform over stdio or HTTP, with read-only access by default and opt-in create, update, and delete tools subject to platform authorization.
      3
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI clients to search and read a local folder of notes, fetch public web pages as markdown with SSRF and robots.txt safeguards, and convert times between IANA timezones. It exposes these read-only capabilities as MCP tools over stdio or streamable HTTP.
      5
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Serves sigit.si account, repository, issue, pull request, code-search, session, hook, and billing operations to AI agents over stdio, reusing the token stored by the CLI login and defaulting repository tools to the checkout the agent is pointed at. Tool lists can be trimmed with read-only mode or toolset selection, and a hosted HTTP endpoint offers the same tools.
      2
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables read-only document retrieval and SQLite exploration through tools over stdio, enforcing a safety gate before SQL execution.
      3
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Exposes fourteen read-only tools over the HEY Research public API, letting assistants look up Robinhood Chain projects, builders, shipped work, relationships and market context, with each answer tagged FACT, DERIVED or UNKNOWN and unmeasured fields omitted rather than zeroed. Runs over stdio or hosted Streamable HTTP, and gives no trade instructions.
      MIT

    TDQS

    A4.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct action: get one identification by request ID, list identifications for an identifier, aggregate history for an entity, explain a risk score, verify a webhook signature, and get server time. The descriptions explicitly cross-reference each other (e.g. search_history vs summarize_entity, and pointing to explain_risk_score for score explanations), leaving no real overlap.

    Naming Consistency4/5

    All tools use snake_case with a consistent shieldlabs_ prefix and mostly follow a verb_noun pattern (get_identification, search_history, summarize_entity, explain_risk_score, verify_webhook_signature). The only minor deviation is current_time, which lacks a verb, but it still reads clearly as a command.

    Tool Count5/5

    Six tools is well-scoped for a read-oriented risk/verdict API: single read, search, aggregate, score explanation, webhook verification, and a time helper. Each tool earns its place without redundancy or obvious padding.

    Completeness4/5

    The surface covers the read lifecycle well (single, list, aggregate, explain) plus webhook verification and time, and the risk-signal catalog is exposed as a resource. A minor gap is the absence of a tool to list recent identifications for a domain/tenant without first knowing an identifier, which some triage workflows would want.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues