Skip to main content
Glama
dbett4

regulated-reporting-mcp

by dbett4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to regulated-reporting-mcp

No user-submitted related servers found.

    Related Servers

    • WhitePact

      Guruprasath-Annadurai
      A
      license
      A
      quality
      A
      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
      44 PyPI
      1
      MIT

    • mcp-server-enterprise-tools

      sudsho
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for regulated enterprises, providing per-tool RBAC, redacted audit logging, and structured error handling. Exposes bank tools for customer lookup, statement search, and dispute resolution over stdio and HTTPS transports.
      MIT

    • numproof

      projecttron
      A
      license
      A
      quality
      D
      maintenance
      MCP server for deterministic numeric verification and spreadsheet auditing. Enables AI agents to verify math/finance claims, audit rows, and evaluate covenant rules with signed, independently checkable receipts.
      4
      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

    C2.8/5.0

    Scored across 117 tools

    Disambiguation2/5

    Many deprecated umbrella tools (workiva_organization, workiva_tasks, workiva_wdata_files) sit alongside their single-verb replacements, creating overlapping entry points. File/document/spreadsheet tools also expose duplicate views of the same resources (export_file vs export_document vs export_spreadsheet; get_file vs get_document vs get_spreadsheet), which raises misselection risk.

    Naming Consistency3/5

    The dominant pattern is readable and mostly consistent (workiva_<domain>_<verb>_<noun>), but it is broken by a large set of deprecated resource-only shims like workiva_chains, workiva_rich_text, and workiva_spreadsheet_sheets. Exceptions such as workiva_full_link_flow and workiva_write_verified further reduce predictability.

    Tool Count1/5

    117 tools is far beyond what an agent can reasonably navigate, especially since roughly 19 are deprecated dispatch shims and many others duplicate the same underlying resources through different views. This creates severe context bloat and tool-selection overhead.

    Completeness4/5

    The server covers most core Workiva lifecycles: files, spreadsheets, documents/sections, Wdata tables/queries/connections, chains, tasks, links, and style guides. Minor gaps exist in presentation management (no list/create/delete), explicit file deletion is unsupported, and document creation/deletion is indirect, but agents can generally work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources