Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ECCA

REMOTE · ECCAAI.COM

Compare engine claims, inspect dissent and check study evidence for student questions.

Available components

+3 this week 82 Trust /100

Last scanned (22 hours ago)

Scores higher than 85% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Education and Research

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security89
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 737 tokens (~61/item across 12 items; 12 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 53% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ecca_pre_mortem" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://eccaai.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=eccaai.com CN=WE1,O=Google Trust Services,C=US 21 Oct 2026 19 Jan 2027 ECDSA 256 ECDSA-SHA256 d4c7ded68b2a137a13da6e6058e52b94
SANs: eccaai.com, *.eccaai.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of eccaai.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
eccaai.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self'; script-src-elem 'self'; script-src-attr 'none'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob:; font-src 'self'; connect-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; upgrade-insecure-requests; worker-src 'self' blob:; manifest-src 'self'; frame-src 'self'; frame-ancestors 'self';
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(self), camera=(self), browsing-topics=()

Protected resource metadata

Retrieved No
Problem no_resource_metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://eccaai.com/api/mcp Verified 200
http (plaintext) http://eccaai.com/api/mcp HTTPS enforced 308 https://eccaai.com/api/mcp
MCP tools · 12 exposed · ~737 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
ecca_bts_divergence ~46

Measures lexical and semantic divergence across candidate assertions to penalize sycophancy.

NameTypeReqDescription
assertionsarrayyesArray of candidate assertions or claims to measure divergence for.

No output schema declared.

No examples provided.

ecca_claim_protocol_validate ~88

Check one ecca.claim-protocol 1.0 document for shape: versioned, engine slots only (no vendor names), split causes from the published taxonomy, question text only with consent, seal present. Returns ok with the error list; validates shape, never the record behind it.

NameTypeReqDescription
documentobjectyesThe protocol document to check (docs/CLAIM_PROTOCOL.md).

No output schema declared.

No examples provided.

ecca_decision_tournament ~58

Evaluates multi-option decision matrix using minimax regret and Pareto ranking over candidate pathways.

NameTypeReqDescription
decisionContextstringyesContext of the decision to evaluate.
optionsarrayyesList of discrete options or strategic pathways.

No output schema declared.

No examples provided.

ecca_learning ~46

Learning and study skills: refine the question, fetch studies, and show named claims before the verdict. Applies evidence and claims checks; spends one solve.

NameTypeReqDescription
questionstringyes–

No output schema declared.

No examples provided.

ecca_money ~45

Money and business: refine the question, fetch studies, and show named claims before the verdict. Applies evidence and claims checks; spends one solve.

NameTypeReqDescription
questionstringyes–

No output schema declared.

No examples provided.

ecca_nutrition ~47

Nutrition and supplements: refine the question, fetch studies, and show named claims before the verdict. Applies evidence and claims checks; spends one solve.

NameTypeReqDescription
questionstringyes–

No output schema declared.

No examples provided.

ecca_pre_mortem ~68

Executes an adversarial pre-mortem identifying failure modes and early warning indicators using empirical argument verification.

NameTypeReqDescription
horizonMonthsinteger–Time horizon in months to simulate forward failure modes.
premisestringyesThe strategic plan, architecture, or business premise to stress-test.

No output schema declared.

No examples provided.

ecca_psychology ~46

Psychology research: refine the question, fetch studies, and show named claims before the verdict. Applies evidence and claims checks; spends one solve.

NameTypeReqDescription
questionstringyes–

No output schema declared.

No examples provided.

ecca_refine ~48

Use one keyed tier-quota slot to sharpen rough student questions without adding facts; return detected niches and refinement chips. A closed engine ceiling falls back locally.

NameTypeReqDescription
textstringyes–

No output schema declared.

No examples provided.

ecca_research ~52

Use one keyed tier-quota slot and dispatch-ceiling reservation to fetch and grade studies from scholarly indexes; return fetched evidence and explicit gaps.

NameTypeReqDescription
nichestring––
questionstringyes–

No output schema declared.

No examples provided.

ecca_synthesize ~147

Compare answers from configured engines and inspect disagreement, with lexical similarity and final-answer agreement when measurable.

NameTypeReqDescription
antagonistboolean–When true, forces one engine to act as adversarial red-team antagonist.
depthstring–intuitive and fast route to one engine; executive, pioneer and deep route a multi-engine dispatch (free callers: two engines first, expanding on measured divergence, one deep solve per day). Any othe…
modelstring–Label echoed in the result. Every value dispatches through the same registered engines; depth decides fast or multi-engine.
querystringyesThe core inquiry, hypothesis, or decision challenge to synthesize.

No output schema declared.

No examples provided.

ecca_verify ~46

Independently answer a question and compare the candidate against deterministic panel agreement. Show named dissent; spends one solve.

NameTypeReqDescription
candidate_answerstringyes–
questionstringyes–

No output schema declared.

No examples provided.

Install

How do I install the ECCA MCP server?

ECCA is a hosted endpoint at https://eccaai.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · eccaai.com

# add to Claude Code
claude mcp add --transport http com-eccaai-ecca 'https://eccaai.com/api/mcp'
Common questions

What is the ECCA MCP server?

ECCA is an MCP server listed in the public MCP registry as com.eccaai/ecca. Compare engine claims, inspect dissent and check study evidence for student questions. This page covers its hosted endpoint (https://eccaai.com/api/mcp).

Is the ECCA MCP server safe to use?

ECCA scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the ECCA MCP server expose?

ECCA exposes 12 tools: ecca_synthesize, ecca_pre_mortem, ecca_decision_tournament, ecca_bts_divergence, ecca_refine, and 7 more. Their descriptions and schemas cost roughly 737 tokens of context every time the server is loaded.

Does the ECCA MCP server require authentication?

Yes. ECCA asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the ECCA MCP server still maintained?

ECCA is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.