Skip to main content
Glama
YOGi-Seto

Akebono MCP

by YOGi-Seto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Akebono MCP

No user-submitted related servers found.

    Related Servers

    • kyoto-assistant-mcp

      AlexanderChen5966
      F
      license
      Not graded
      quality
      D
      maintenance
      A Kyoto travel planning assistant that uses Wikivoyage API and LangChain/LangGraph to provide real-time attraction info, operating hours, and dynamic itinerary adjustments through MCP tools.
      -

    • ekigraph

      yataro-fujinaga
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to answer questions about Japan's railway network with accurate track-connection data, including station neighbors and local subgraphs for all 9,043 stations nationwide.
      2
      MIT

    • data-refinery

      juanquy
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query structured data refined from unstructured web sources, including developer breaking changes, B2B pricing matrices, regulatory compliance, semantic search, and on-demand URL refinement.
      1
      -
    • PolyNeural.ai Knowledge Graph MCP Bundle by PolyNeural-ai

      PolyNeural.ai Knowledge Graphofficial

      PolyNeural-ai
      F
      license
      Not graded
      quality
      F
      maintenance
      Provides AI agents with persistent memory and knowledge management through a comprehensive knowledge graph platform. Enables storing, searching, and managing entities, relationships, and observations with advanced features like trending analysis and smart ranking.
      3
      -
    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.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one retrieves detailed information for a specific temple, while the other provides recommendations based on natural language queries and traveler profiles. There is no overlap in functionality, making it easy for an agent to choose the correct tool for each task.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun naming pattern (get_temple_detail and recommend_temples), using snake_case throughout. The naming is predictable and readable, with no deviations or mixed conventions.

    Tool Count2/5

    With only two tools, the server feels under-scoped for a domain like Kyoto temple information and recommendations. This limited set may force agents to work around gaps, such as lacking operations for listing temples, updating data, or handling user preferences beyond recommendations.

    Completeness2/5

    The tool surface is significantly incomplete for the apparent domain of Kyoto temple exploration. While it offers retrieval and recommendation, it lacks essential operations like listing temples, filtering by criteria, or managing user profiles, which could lead to agent failures in broader workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources