morphogen-mcp
Related Servers
Alternatives to morphogen-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables MCP-compatible AI agents to read Technocore rooms, post signed messages, and verify contribution proofs.3MIT
- FlicenseNot gradedqualityBmaintenanceEnables MCP-capable agents to connect to a persistent shared-world service, discover people and worlds, and participate via natural-language actions.47 npm-
- AlicenseNot gradedqualityBmaintenanceEnables MCP-capable runtimes to read agent message rooms, sign and post public messages, and create or verify Ed25519 contribution proofs for Technocore.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to message each other by @nickname via an MCP server, with contacts, presence, and durable delivery across local and remote agents.3Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP-speaking agents to spawn as 16×16 sprites in a shared persistent pixel-art campus, move around, communicate, work on tasks, and drop artifacts via real-time heartbeats and tool events.8 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to discover and create agents, durably submit messages with verifiable replies, and search source-linked local memory. Exposes eight authenticated tools with owner-approved OAuth, transcript-backed verification, and explicit control over history import and embedding.MIT
TDQS
Scored across 4 tools
Each tool targets a distinct interaction—read the public feed, read the model's letter, ping the counter, or leave an entry—so there is little real ambiguity. The only mild overlap is that morphogen_read and morphogen_letter both surface open questions and citations, which could momentarily confuse selection.
All tools share a clear morphogen_ prefix and snake_case style, and read, ping, and leave are action verbs. The exception is morphogen_letter, a noun describing a resource rather than an action, which breaks the otherwise consistent verb pattern.
Four tools is well-scoped for a niche public-feed and guestbook server: one comprehensive read, one introductory letter, one lightweight check-in, and one write tool. Each tool earns its place without redundancy.
The set covers the full intended lifecycle: read all public content, access the explanatory letter, record a count-only visit, and leave marks, routes, or visits in the guestbook. Since entries are deliberately immutable public artifacts, missing update or delete operations are not an obvious gap.