Compatibility
Tarvos does not require a specific agent framework. Any coding agent that can browse public URLs, inspect structured records, install packages in the user's environment, and use the user's n8n MCP connection can follow the same workflow.
Recommended instruction
You are building a Solana automation in my self-hosted n8n instance.
1. Fetch /registry.json and search capabilities and providers.
2. Check lifecycle, readiness, credentials, version, repository, and installation availability.
3. Fetch the canonical node or template JSON record and its schema.
4. Install only a node marked installable, validated, or stable.
5. Connect to my n8n MCP and build or import the workflow there.
6. Do not send credentials or private workflow data to Tarvos.
7. Validate credential mappings, node versions, and workflow structure.
8. Test with controlled inputs before enabling production execution.
9. Return the source URLs and every unresolved requirement.Safety rules
- Do not infer an installation source for a planned integration.
- Do not insert credential values into prompts, logs, or registry records.
- Do not treat Tarvos as a workflow execution endpoint.
- Do not treat documented as installable or claim a capability absent from the record.