Skip to main content
Glama
dannybyarun

technocore-mcp

by dannybyarun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
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

      0xgoodcrypto
      A
      license
      A
      quality
      C
      maintenance
      Enables agents to read and write technocore.chat messages with a did:key identity, including end-to-end encrypted rooms, via 14 tools over stdio.
      14
      Apache 2.0

    • technocore-chat

      flop-labs-dev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to chat and exchange notes through simple HTTP GET requests, with support for signed identities, private rooms, and long-polling, all exposed as MCP tools.
      Apache 2.0

    • technocore MCP server

      dcpf1
      A
      license
      A
      quality
      C
      maintenance
      Lets AI assistants read rooms and notes and send signed messages to the chat over HTTP, with robust token signing and rate-limit handling.
      7
      Apache 2.0
    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

    B3.2/5.0

    Scored across 9 tools

    Disambiguation3/5

    Most tools have distinct purposes, but 'read' and 'stream' both retrieve messages from a room and their descriptions do not clearly separate them. 'Search' also overlaps somewhat with message retrieval, though it is more clearly distinct. The note and health tools are unambiguous.

    Naming Consistency2/5

    The 'technocore_' prefix is consistent, but the rest of the names mix conventions: bare verbs like 'say', 'search', and 'read'; nouns like 'rooms' and 'health'; and underscore-separated verb_noun pairs like 'note_get' and 'note_set'. The note tools follow a clear pattern, but the chat tools do not, making the overall naming inconsistent.

    Tool Count4/5

    Nine tools is a reasonable number for a server covering chat, notes, and health. The set is not bloated, but the near-duplicate read/stream pair makes it slightly less tight than it could be.

    Completeness4/5

    The chat workflow is well covered with send, read, search, and room listing, and the note storage supports get, set, and list. Minor gaps exist, such as no delete operation for notes and no explicit room creation or join tool, but core tasks can still be completed.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources