mcpbeat

eDiscovery Decoder News/Calc MCP Server

com.ediscoverydecoder/mcp
answering

eDiscovery Decoder News/Calc is answering right now. Last checked 12 min ago. It exposes 15 tools.

Free educational MCP for read-only eDiscovery news and TAR/review calculators.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
15
Tools
read from the server
304 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add mcp --transport http https://mcp.ediscoverydecoder.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.ediscoverydecoder.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.ediscoverydecoder.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.ediscoverydecoder.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.ediscoverydecoder.com/mcp"
    }
  }
}

Available tools 15

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

calculate
calculate_control_set_recall
Calculate recall against a known control set: the share of documents already confirmed relevant that the workflow found, with a Wilson confidence interval. Use when you have relevant-found and relevant-missed counts from a fixed reference set. For recall from a confusion matrix use calculate_review_metrics; from a discard-set sample use calculate_tar_recall_estimate. Aggregate counts only; not legal advice.
calculate_elusion
Estimate how much responsive/relevant material may remain in a set you chose NOT to review (the discard, null, or 'elusion' set). Use when a random sample of that excluded set has been coded — e.g. 'we sampled 400 culled docs and found 2 relevant.' Returns the elusion rate and a Wilson confidence interval. For an overall recall % from the same sample, use calculate_tar_recall_estimate. Aggregate counts only; not legal advice.
calculate_prevalence_richness
Estimate how rich or prevalent a population is — the share that is responsive/relevant/positive — from positive hits in a random sample, with a Wilson confidence interval. Use for 'what % of this set is relevant?' or to size review scope and cost expectations. Aggregate counts only; not legal advice.
calculate_review_metrics
Score a coded sample when you have a full confusion matrix (true/false positives and negatives) — e.g. comparing a TAR model's calls against a reviewer's. Returns recall, precision, F1, accuracy, and in-sample elusion. Use calculate_control_set_recall if you only have relevant-found vs relevant-missed; calculate_elusion for a discard/null-set sample. Aggregate counts only; not legal advice.
calculate_sample_size
Work out how many documents to randomly sample to estimate a proportion (e.g. richness or elusion) at a target confidence level and margin of error, with finite-population correction. Use when planning a sample before review — 'how big a sample do we need?' Aggregate inputs only; not legal advice.
calculate_tar_recall_estimate
Estimate overall TAR recall and how many responsive docs were missed, by combining the responsive count already found with an elusion sample of the excluded set. Use when the user wants a recall % for the whole workflow, not just the elusion rate. For only the elusion rate and its interval, use calculate_elusion. Aggregate counts only; not legal advice.
news
get_news_brief
Get the current eDiscovery Decoder news brief: top stories plus a Week in Review breakdown, returned both as structured data and as display-ready Markdown (formatted_brief) with a 'why it matters' line per story. Use when the user wants a roundup or summary of current eDiscovery AI news rather than a keyword search.
search_news
Find recent eDiscovery / legal-AI / TAR news by topic, tag, or date range. Use when the user asks what's new or recent in eDiscovery, wants stories on a subject, or asks about a time window. For a ready-made top-stories roundup instead, use get_news_brief.
capabilities
list_capabilities
List the full eDiscovery Decoder MCP surface — every tool, prompt, and resource, plus the suggested demo flow and safety boundaries — with an example prompt for each. Call this first when you are unsure which tool fits the user's question, or when tool-search shows only a partial list.
compare
compare_tar_cutoffs
Compare candidate TAR score or rank cutoffs side by side: for each cutoff, how many docs sit above it, its share of the scored set, and (if responsive counts are given) an estimated precision. Use when deciding where to draw the review/cull line. Aggregate counts only; not legal advice.
demo
get_demo_guide
Return a short, human-readable walkthrough for testing this server: the endpoint, the tool/prompt/resource names, and ready-to-paste sample prompts. Use to give someone a guided demo. For the full machine-readable capability catalog, use list_capabilities instead.
ping
ping
Health check: confirm the eDiscovery Decoder News/Calc MCP server is reachable before a demo or when troubleshooting a connection. Returns server name and version. No inputs.
prompt
get_prompt_template
Return the rendered text of one of this server's guided prompts (mcp-demo-tour, tar-matter-kickoff, weekly-digest). Use when the client can call tools but cannot open MCP prompts directly, or when you want to inspect a prompt's wording before using it.
resource
get_resource_content
Fetch the JSON behind a supported edd:// resource — the demo guide, TAR learning path, glossary, or news (latest / brief / by-date). Use when you want resource content but the client cannot read MCP resources directly, e.g. to pull glossary definitions or the news brief as a normal tool result.
validate
validate_sample_design
QC a TAR validation sampling plan: check whether it has the documented elements needed for a defensibility discussion (population, sample size, confidence level, sampling frame/method, randomization, etc.) and flag what is missing or inconsistent. Use to sanity-check a sampling protocol before relying on it. Reviews metadata only — not a legal sufficiency opinion.

Endpoints

URLTransportStateLatencyChecked
https://mcp.ediscoverydecoder.com/mcp streamable-http answering 248 ms 12 min ago

eDiscovery Decoder News/Calc — questions

Answers built from our own checks of this server.

What can eDiscovery Decoder News/Calc do?
It exposes 15 tools, read directly from the server on our last check. Among them: calculate_control_set_recall, calculate_elusion, calculate_prevalence_richness, calculate_review_metrics, calculate_sample_size, calculate_tar_recall_estimate and 9 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is eDiscovery Decoder News/Calc mostly used for?
Its tools cluster around calculate and news. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is eDiscovery Decoder News/Calc working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 304 ms. The bar chart above shows every period we have measured.
How do I connect eDiscovery Decoder News/Calc?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does eDiscovery Decoder News/Calc need an API key?
No. eDiscovery Decoder News/Calc completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 15 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is eDiscovery Decoder News/Calc?
It answers our handshake in 304 ms on average, which is faster than 46% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.