ECCA
com.eccaaiv1.0.0Updated Oct 9, 2026
Compare engine claims, inspect dissent and check study evidence for student questions.
Overview
AI-generated overview
Lets an assistant compare engine claims, inspect dissent, and check study evidence for student questions.
- What it does
- ECCA is a remote MCP server that exposes tools for comparing claims made by engines, inspecting dissent, and checking study evidence in the context of student questions. The registry description is brief, and no tool list is published, so the exact tool names and parameters are not documented here. It is reached over streamable HTTP at a hosted endpoint rather than run locally.
- When to use it
- Worth considering when an assistant needs to weigh competing claims, surface disagreement, or verify study evidence behind student questions. It is less useful if you need a documented, self-hosted toolset, since no tool list is published.
- Requirements
- A remote streamable HTTP endpoint; no local runtime or package is needed. Calls to tools require an Authorization header with a bearer key in the form ecca_sk_..., obtained after signing in at the provider's developer page. The initialize, ping, and tools/list methods work without a key.
Before you install
The Authorization header carries a secret API key; treat it as a credential and avoid exposing it in logs or shared configuration. The server is hosted by a third party, so queries and any content sent to it leave your machine. No tool list is published, so review what each tool does before relying on it.
Installation
In SourceWeft
- Open ECCA in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"ecca": {
"type": "http",
"url": "https://eccaai.com/api/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v1.0.0LatestOct 9, 2026

