by eep-dev · MCP Server · ★ 22
Entity Engagement Protocol (EEP) An open standard for push-based, verifiable communication between digital entities and the clients that follow them. Two agent paths, side by side. Deterministic — no LLM spend. Reproduce it → Stability (v0.1) The specification and reference packages are v0.1: the spec, schemas, CI and libraries here are meant to be implemented against, but breaking changes can still happen while the ecosystem is small. Pin versions in production and read CHANGELOG.md before upgrades. Governance details: GOVERNANCE.md. Community a
| Stars | 22 |
| Forks | 6 |
| Language | TypeScript |
| Category | MCP Server |
| License | Apache-2.0 |
| Quality Score | 67.0261193398254/100 |
| Open Issues | 11 |
| Last Updated | 2026-07-08 |
| Created | 2026-04-15 |
| Platforms | mcp, node |
| Est. Tokens | ~18k |
These tools work well together with EEP for enhanced workflows:
Explore other popular mcp server tools:
EEP is An open standard for push-based, verifiable communication between digital entities and agents that follow them.. It is categorized as a MCP Server with 22 GitHub stars.
EEP is primarily written in TypeScript. It covers topics such as activitypub, agentic, agents.
You can find installation instructions and usage details in the EEP GitHub repository at github.com/eep-dev/EEP. The project has 22 stars and 6 forks, indicating an active community.
EEP is released under the Apache-2.0 license, making it free to use and modify according to the license terms.