Skip to main content
Glama
dindin-abdulloh

Secure Reports MCP

by dindin-abdulloh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Secure Reports MCP

No user-submitted related servers found.

    Related Servers

    • toolgate

      Rakshit-gen
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to call backend tools under per-agent policy, deciding which tools each agent can see, what arguments it may pass, how often it may call, and which writes wait for human approval. It also redacts secrets and PII from tool results, fences untrusted output against injection, and records every call in a hash-chained audit log.
      25 npm
      MIT

    • Aspire MCP

      Zero-State-LLC
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables a locally hosted AI, running entirely inside the client's building with no outside network access, to reach line-of-business systems, document stores and email through a small set of narrow, task-specific and schema-validated tools. It applies least-privilege per-tool credentials, personal-data masking, output leak checks and tamper-evident audit logging, keeping actions read-only by default and gating any write behind human approval so untrusted document content cannot trigger privileged operations.
      -

    • claims-mcp-server

      adwitiya-pandey
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to securely query a synthetic health-insurance claims database through read-only, parameterized tools for claims, member histories, coverage rules, and year-to-date summaries. Includes API-key authentication, per-tool authorization, rate limiting, untrusted-text sanitization, and fail-closed audit logging.
      MIT

    • enterprise-agent-lab

      isaac-dev-ai
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables controlled AI-agent access to enterprise-shaped tools with a deny-by-default gated write path, human approval, dry-run execution, and append-only audit logging.
      1
      -

    • Governed MCP Gateway

      icohangar-ops
      A
      license
      Not graded
      quality
      C
      maintenance
      Enforces authenticated identity on every tool call and SSE frame, rotates vaulted credentials in place, and restricts tools via allowlists.
      71 npm
      MIT

    • actionwall

      AfridaMehanaz
      A
      license
      Not graded
      quality
      B
      maintenance
      Gives AI agents policy-checked tools for shell commands, file reads and writes, HTTP fetches and tool calls, deciding each action against a policy before it runs while tracking secret taint and recording every decision in a tamper-evident audit log.
      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

    A3.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing available reports, initiating an export job, and polling job status. There is no overlap in resource or action, so an agent can easily choose the right tool.

    Naming Consistency5/5

    All three tools use consistent snake_case with verb-led names (list_..., download_..., get_...). The pattern is predictable and readable across the set.

    Tool Count5/5

    Three tools are well-scoped for a focused report-export server. Each earns its place in the core workflow without being excessive.

    Completeness4/5

    The set covers listing, starting an export, and checking job status, which forms a complete minimal lifecycle. Minor gaps exist (no cancel job or list jobs operation), but agents can work around them for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources