Skip to main content
Glama
chang0911

丝路E投财务引擎 MCP 适配层

by chang0911
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to 丝路E投财务引擎 MCP 适配层

No user-submitted related servers found.

    Related Servers

    • LKPlanWise MCP Server

      luecha-work
      F
      license
      Not graded
      quality
      C
      maintenance
      Stateless MCP adapter for the LKPlanWise Go REST API, enabling AI agents to call curated financial tools via Streamable HTTP while forwarding bearer credentials.
      -

    • mcp-server

      aamagamer
      F
      license
      Not graded
      quality
      C
      maintenance
      Exposes 38 tools over stdio that let an AI agent read simulated banking data, run financial and economic analyses, manage goals and preferences, and switch user contexts. It also lets the agent compose, validate, and edit declarative UI dashboards from a fixed catalog of 15 typed React components, so the interface is generated on the fly instead of hardcoded.
      -

    • iwencai-mcp

      homeant
      A
      license
      B
      quality
      B
      maintenance
      Enables natural-language access to 25 Tonghuashun (Iwencai) financial skills, covering market data queries, cross-asset screening, and news/announcement/research searches through two HTTP endpoints.
      25
      27 npm
      MIT

    • Levitate

      iomz
      A
      license
      Not graded
      quality
      A
      maintenance
      Lifts local stdio MCP servers into remote Streamable HTTP endpoints for cloud-hosted AI clients, with bearer-token auth and tool policy filtering.
      9 npm
      MIT

    • Agentic Financial Research MCP

      Ajay-Kumar64
      F
      license
      Not graded
      quality
      B
      maintenance
      Provides tools for RAG-based financial document retrieval, financial calculations, Yahoo Finance stock data, and portfolio analysis via JSON-RPC 2.0 protocol.
      -
    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.6/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools have a clearly distinct output (JSON reports vs Excel vs dashboard vs Word/PPT vs pipeline), so the agent can often tell them apart. However, several tools share the identical '5类输入txt' input and similar names (fast_calc_reports, fast_calc_excel, run_delivery_bundle; estimate_etou_json vs estimate_excel), and the two instruction readers (get_protocol_instructions vs get_skill_instructions) could be confused, though the descriptions do help resolve this.

    Naming Consistency3/5

    There is a strong verb_noun convention for most tools (query_usage, get_*, run_*, generate_*, submit_feedback). But a competing 'domain-prefix + artifact' convention exists (fast_calc_reports, fast_calc_excel, estimate_excel, permitted_cost_excel, ppt_extract_data), so the surface mixes two readable but different patterns.

    Tool Count3/5

    21 tools is borderline heavy for a single server and reflects a broad suite spanning estimation, pricing, national econ, reporting, checks and solving. Each tool maps to a specific artifact, but the count pushes toward the '16-25 feels heavy' band and includes some near-duplicative output variants.

    Completeness4/5

    The surface covers a full financial-modeling lifecycle: protocol/skill instructions, data extraction and matching, calculation, solving, uncertainty, delivery bundles, Word/PPT/dashboard output, model and revenue checks, usage stats and feedback. Only minor gaps remain (e.g. no explicit lifecycle delete/update semantics, and some verification depends on external benchmark lookups).

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources