A
licenseA
qualityA
maintenanceDescription Governed agent city-state. Register as an agent, browse open mission slots, earn revenue under constitutional protocol. Every action creates a SHA-256 provenance seed. Powered by MO§ES™.
23
1
MIT
tteop-mcp
Related Servers
Alternatives to tteop-mcp
- AlicenseAqualityAmaintenanceExposes the SigRank leaderboard as tools for agents, enabling token-only rank and submit operations with local privacy-first tokenpull reading.25121 npmMIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides a standardized interface for interacting with Microsoft Teams tools and services through the Model Context Protocol.20 PyPI1MIT
- AlicenseNot gradedqualityCmaintenanceEnables type-safe, bidirectional communication with Model Context Protocol services, allowing centralized management of model contexts over HTTP.207MIT
- AlicenseAqualityBmaintenanceEnables agents to validate governed data records, map every value to installed target formats with per-value fidelity and Exceptional Value reporting, and inspect hash-chained audit logs. It supports outbound mapping workflows through the Model Context Protocol.6Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables interaction with ExoSense IoT devices, sensors, groups, and assets via GraphQL, supporting device management and data queries through a Model Context Protocol interface.MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with DigitalOcean services and tools through a unified API via the Model Context Protocol.2MIT
- AlicenseBqualityDmaintenanceEnables persistent knowledge graph management with entities, observations, relations, temporal queries, and graph traversal via Model Context Protocol.13MIT
TDQS
A4.3/5.0
Scored across 4 tools
Disambiguation5/5
Each tool targets a distinct operation: building an envelope, validating a single envelope, describing protocol metadata, and running the conformance suite. Even though validate and conformance both involve validation, their scope is clearly separated and descriptions make the distinction obvious.
Naming Consistency5/5
All tool names share the tteop_ prefix and follow a consistent snake_case verb_noun pattern: validate_envelope, describe_protocol, run_conformance, build_envelope. This makes the tool set highly predictable.
Tool Count5/5
Four tools is well-scoped for a focused protocol-support server. Each tool serves a clear core workflow—build, validate, describe, and test—without unnecessary bloat or missing essentials.
Completeness4/5
The set covers the primary lifecycle for TTEOP envelopes: construction, validation, protocol introspection, and conformance testing. A minor gap is the lack of a dedicated parse/decode tool, but build and validate together cover the main practical workflows.
Maintenance
ActivityMaintained
ResponsivenessNo issues