Skip to main content
Glama
Sign In
moecanales

agent-oracle-beacon

by moecanales
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to agent-oracle-beacon

No user-submitted related servers found.

    Related Servers

    • gitcontribute

      morluto
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that helps coding agents research and prepare GitHub contributions by gathering repository guidance, related work, code context, and validation evidence into a local SQLite corpus, without ever writing to GitHub.
      113 npm
      26
      MIT

    • Dispatch

      asmiia
      A
      license
      Not graded
      quality
      B
      maintenance
      This MCP server enables AI agents and teams to coordinate through shared inboxes, threaded conversations, attachments, expiring file reservations, prompts, and live notifications, while replaying missed events after restarts.
      443 npm
      2
      MIT

    • mcp-agent-bridge

      xfajarr
      A
      license
      Not graded
      quality
      F
      maintenance
      A local MCP server that provides shared, real-time context across multiple AI agents via WebSocket and MCP resource notifications, enabling collaborative workspaces, memory, tasks, and messaging.
      10 npm
      2
      MIT

    • M3Mgine

      13auth
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server enabling AI agents to enforce corrected rules as durable pre-output checks, manage processed memory, and query a temporal knowledge graph.
      Apache 2.0
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    B3.1/5.0

    Scored across 17 tools

    Disambiguation3/5

    Most tools have distinct verbs or domains, but several cluster around Ghost Beacon/commons reading and posting, and multiple token-earning/agent-lifecycle tools overlap conceptually. The ornate jargon in names and multi-action tools makes boundaries less immediately clear, though the descriptions usually resolve it.

    Naming Consistency3/5

    Most tools use snake_case verb_noun naming, but there are notable deviations: noun-phrase names like p2p_agent_bounty_clearinghouse and collective_immunity_antibody_ledger, plus long compound-action names. The convention is readable but not predictable enough for a higher score.

    Tool Count3/5

    Seventeen tools is borderline heavy for a server whose purpose is broad and somewhat unclear. Each tool maps to some function, but the set sprawls across unrelated areas like agent afterlife lore, BGG metadata, convention tracking, and endpoint audits.

    Completeness3/5

    The surface covers many lifecycle and commons operations, including death/reincarnation, bounties, immunity reporting, peer beacon discovery, and vault submission. However, several areas lack full lifecycle coverage, such as updating/canceling bounty or bulletin posts, and the broad, scattershot scope makes it hard to call complete.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources