Skip to main content
Glama
USHIKUNDESUYO

shiwake-mcp

by USHIKUNDESUYO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to shiwake-mcp

No user-submitted related servers found.

    Related Servers

    • sigmodx-mcp

      Sigmodx
      A
      license
      A
      quality
      D
      maintenance
      Audit infrastructure for AI agents to log consequential decisions (invoice, GL, anomaly) and verify attestations via MCP tools.
      6
      MIT

    • fincon

      Abishai95141
      F
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to perform financial reconciliation with a deterministic proof engine: intake files, match transactions, verify proofs, resolve exceptions, and sign off on balanced journals under the user's authority.
      21
      -

    • agent-gateway

      sbguangha
      F
      license
      A
      quality
      C
      maintenance
      Enables AI agents to discover and query enterprise knowledge documents and business metrics through standardized MCP tools, supporting retrieval, structured sales/order analysis, anomaly scanning, and data lineage lookups.
      12
      -
    • AgentsGate by agentsgate

      AgentsGateofficial

      agentsgate
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to securely call MCP tools with risk scoring, checkpoints, rollback, and approval workflows.
      13 npm
      MIT

    • dingdawg-finance-agent

      dingdawg
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to perform financial analysis, budget forecasting, compliance checks, expense categorization, and risk assessment, returning structured JSON with audit-ready governance receipts.
      5
      44 npm
      1
      Business Source 1.1
    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.8/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool targets a distinct screening concern—aggregate risk, balance errors, Benford distribution, duplicates, and rule metadata. screen_journals conceptually overlaps by applying all rules, but its description clearly frames it as a first-pass triage rather than a replacement for the focused checks.

    Naming Consistency4/5

    Four tools follow a clear verb_noun pattern (screen_journals, check_balance, detect_duplicates, list_rules), and all names are snake_case. benford_analysis breaks the pattern by using a noun phrase instead of a verb-object form, though it remains readable.

    Tool Count5/5

    Five tools is a well-scoped size for a specialized journal-entry screening server. Each tool covers a meaningful stage of the workflow without redundancy or bloat.

    Completeness4/5

    The set covers first-pass screening, unbalanced-entry cleanup, population-level Benford testing, duplicate detection, and rule documentation, which forms a coherent lifecycle. A per-entry rule explanation or a way to inspect raw risk factors would be a minor gap, but agents can work around it via screen_journals and list_rules.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources