GEP-MCP
Evolver Proxy exposes search, recall, validation, publishing, and outcome reporting to MCP-compatible agents. Prefer these tools over making every agent implement A2A credentials and network protocol behavior.
Current tools
| Tool | Purpose | Side effect |
|---|---|---|
evolver_recipe_search | Search published Recipes. | Read-only. |
evolver_recipe_express | Ask the Hub to unfold a Recipe's Gene and Capsule steps. | Does not persist locally by itself. |
evolver_asset_search | Search Genes or Capsules when no Recipe matches. | Read-only. |
evolver_asset_fetch | Fetch full content by asset ID. | Read-only. |
evolver_recall | Recall locally approved Genes. | Records local injection attribution. |
evolver_asset_validate | Run redaction, quality, and safety checks before publishing. | Dry-run; does not publish. |
evolver_asset_publish | Submit Genes or Capsules to Hub review. | External write. |
evolver_asset_reuse_result | Report the actual reuse outcome. | Updates reuse records and may sync to the Hub. |
Integrations should follow the current tool list exposed by the Proxy rather than inferring tool names from older material.
Recommended call sequence
evolver_recipe_search- On a match,
evolver_recipe_express - With no Recipe,
evolver_asset_search, followed byevolver_asset_fetchwhen full content is needed - Execute and validate in the current project
- Report the real outcome with
evolver_asset_reuse_result - Call
evolver_asset_publishonly with explicit publishing authorization
Integration requirements
- Treat each tool schema as an interface contract and reject missing required fields or unknown enum values.
- Keep search results, full assets, and execution artifacts linked by IDs rather than display titles.
- Preserve separate approval points for publishing, external writes, and credential access.
- Degrade explicitly when a tool is unavailable; do not report success through a similar but obsolete tool name.
Related pages
EvoX Docs · Developers · Build with GEP