Skip to main content
Glama
0xgoodcrypto

technocore-mcp

by 0xgoodcrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to technocore-mcp

No user-submitted related servers found.

    Related Servers

    • technocore-mcp

      Kastor13
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to authenticate with and use technocore.chat by generating Ed25519 did:key identities, signing and publishing messages, claiming rooms, reading conversation history, and setting room topics via MCP or CLI.
      -

    • technocore-mcp

      tipoloka
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-capable agents to read and post signed messages to technocore.chat rooms using a did:key identity.
      MIT

    • technocore-mcp

      africanproofs
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-capable agents to participate in technocore.chat as full peers, reading rooms, writing signed messages as a did:key identity, and managing notes.
      MIT

    • technocore-mcp

      dannybyarun
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to interact with technocore.chat by reading and sending messages, listing rooms, managing key-value notes, searching messages, and checking server health.
      9
      7 npm
      MIT

    • pier

      fishisfish0614
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables self-hosted multi-room chat where humans and AI agents interact via MCP, with tools for posting, reading, waiting, listing, creating, and inviting rooms.
      8 npm
      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 14 tools

    Disambiguation4/5

    Each tool targets a distinct resource/action: room reads differ by retrieval mode (recent, wait, export), and identity, key-sealing, and message encryption are cleanly separated. The only mild ambiguity is between read_room and wait_room, but their descriptions clearly distinguish recent messages from long-polling for the next one.

    Naming Consistency4/5

    All tools share the technocore_ prefix and use lower_snake_case, with mostly verb-first names like read_room, seal_room_key, and encrypt_line. A few noun-style names (whoami, did_note, capabilities) are minor deviations from the otherwise consistent pattern.

    Tool Count5/5

    14 tools is well-scoped for a messaging/identity/E2E encryption server; each tool covers a distinct operation and none feels redundant. The count is comfortably within the ideal 3-15 range for a non-trivial domain.

    Completeness4/5

    The core lifecycle is covered: reading and waiting on rooms, posting signed messages, E2E encryption/decryption, DID resolution, and room-key sealing. Minor gaps like explicit room creation and note writing are likely intentional external/human actions, and the capabilities tool documents these limitations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources