Skip to main content
Glama
lonniev

DPYC Oracle

by lonniev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to DPYC Oracle

No user-submitted related servers found.

    Related Servers

    • Gitopia MCP Server by gitopia

      Gitopia MCP Serverofficial

      gitopia
      A
      license
      A
      quality
      C
      maintenance
      Decentralized Git with on-chain governance, bounties, and DAOs. Tools for repos, issues, PRs, labels, releases, bounties, and DAO proposals. Auto-wallet on first use, trust tiers, and approval mode for human-in-the-loop.
      57
      3
      MIT
    • reedright by reedright

      reedrightofficial

      reedright
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to read, search, and propose durable knowledge stored as flat files in a GitHub repository, with every write opened as a pull request and domain owners approving changes in a web UI without touching git.
      Apache 2.0
    • @agentcivics/mcp-server by agentcivics

      @agentcivics/mcp-serverofficial

      agentcivics
      A
      license
      A
      quality
      A
      maintenance
      Read-only on-chain query surface for the AgentCivics civil registry on Sui — soulbound AI-agent identities, on-chain memories, reputation, refusal records. Hosted, no install, no keypair. For write tools (register, write_memory, record_refusal), install the npm package @agentcivics/mcp-server locally and supply your own keypair.
      26
      1
      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

    A3.7/5.0

    Scored across 30 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action—member lookups, role-specific registrations, relay management, campaigns, and informational queries are all clearly separated. Even the 'not yet implemented' ban and membership tools are unambiguous in their purpose.

    Naming Consistency3/5

    The majority of tools follow a verb_noun pattern (get_rulebook, register_operator, list_campaigns), but a substantial minority use bare nouns or phrases (about, economic_model, network_versions, how_to_join, who_is_first_curator, service_status). This mix is readable but inconsistent.

    Tool Count2/5

    With 30 tools, this exceeds the 25+ threshold that signals an overgrown surface. The broad scope—membership, authorities, operators, advocates, bans, campaigns, relays, and network info—partly justifies the count, but the set feels heavier than necessary and could be consolidated.

    Completeness4/5

    The tool surface covers the core lifecycle for citizens, operators, authorities, advocates, campaigns, and relays, plus governance and network status. Minor gaps exist—no advocate deregistration, no citizen update flow, and some ban tools are stubs—but agents can complete primary workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources