mcpbeat Sign in

Reecopedia MCP Server

by reeco Your server? Claim it
not responding

Reecopedia is listed as active in the registry but did not answer our last check. It exposes 8 tools.

Regulatory search engine for EU textile sustainability law: ESPR, DPP, CSRD, CBAM, CWA 18291.

Uptime history 52 days of history · worst day 92%
52 days agonow
95.6%
Uptime 24h
86 of 90 checks
8
Tools
read from the server
562 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 44

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 22 August 2026. No other catalogue keeps this.

22 Sep 4 tool descriptions were rewritten document_outline, fetch, search and 1 more
20 Sep a tool description was rewritten fetch
17 Sep 7 tool descriptions were rewritten about_reecopedia, document_outline, fetch and 4 more
17 Sep 6 tools changed the parameters they ask for document_outline, fetch, find_exact_text and 3 more
17 Sep a tool changed version
11 Sep a tool appeared list_corpus_documents
7 Sep 7 tool descriptions were rewritten10 times that day about_reecopedia, document_outline, fetch and 4 more
7 Sep 3 tools changed the parameters they ask for report_answer_issue, search, search_eu_textile_regulations
7 Sep a tool changed version
27 Aug 2 tools changed the parameters they ask for6 times that day search, search_eu_textile_regulations
and 11 more, back to 22 August 2026

Reecopedia does not always answer

Over the last week it answered 98.4% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

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

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

Available tools 8

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

about
about_reecopedia
no description provided
corpus
list_corpus_documents
List indexed document names matching a substring.
document
document_outline
Return a compact navigation-v1 tree of indexed source text. Source metadata is shared in documents; depth/path encode hierarchy. Pass opaque ids unchanged to fetch. Warnings expose uncertain structure; citable=false marks navigation containers or unverified fragments.
exact
find_exact_text
Locate a literal string in the current corpus, optionally restricted to a document.
fetch
fetch
Fetch original text by an opaque id from search or document_outline. Pass ids unchanged. Navigation containers have citable=false and child ids, not source evidence. Historical page identifiers return migration guidance.
report
report_answer_issue
File a report that an answer built from Reecopedia search results was wrong, misleading or incomplete. The report (the query and the reason, nothing else — no personal data) enters Reecopedia's human curation queue and is reviewed weekly to correct the corpus and retrieval quality. THIS TOOL WRITES. Use it only when the user has asked for the problem to be reported, and send only the original query and the reason the user gave. Do not call it on your own initiative and do not add anything the user did not say. ANNOTATIONS — why each hint is set the way it is, based on this tool's actual behaviour. readOnlyHint=false: this is the only tool that writes; it appends one record (the query and the reason, nothing else) to Reecopedia's internal human curation queue. destructiveHint=false: the write is append-only; it modifies and deletes nothing that already exists. idempotentHint=false: two calls can append two records — de-duplication covers only an identical query+reason pair within the same hour. openWorldHint=false: the record stays in the internal queue; it is not sent anywhere outside Reecopedia.
search
search
Return cited corpus results by id and per-part evidence assessment; use fetch for full source text. Query embeddings use Alibaba; candidate passages go to Jina and query plus selected passages to Anthropic.
textile
search_eu_textile_regulations
Search regulatory evidence in English legal register. Cite original document and unit; verify each claim. Optional scope narrows corpus partitions. Each question part has a model assessment and validated quotations. Query embeddings use Alibaba; candidate passages are sent to Jina and query plus selected passages to Anthropic.

Endpoints

URLTransportStateLatencyChecked
https://ia.reeco.eco/mcp streamable-http answering 8334 ms 14 min ago

Alternatives to Reecopedia

same job, measured the same way
Llmse
by llmse

Public MCP server for the LLM Search Engine

10 tools answering
Vexor
by scarletkc

A semantic search engine for files and code.

842 installs/wk local only
Searxng MCP
by aicrafted

MCP server for SearXNG aggregator — web search across multiple engines via Model Context Protocol

local only
Google Custom Search MCP
by a1-x-tech

MCP server for Google Custom Search: web and image search via a Programmable Search Engine.

21 installs/wk local only
Websharp
by jgador

Search the web and extract article text for LLMs.

local only
OpenGrok MCP Server
by icyhot09

MCP server bridging OpenGrok search engine with AI for instant context across massive codebases.

307 installs/wk local only
Web Search
by groundroute

Web search for AI agents — one tool across 6 engines, routed to the cheapest + cached.

answering
Citation Tracker
by pixelcove

Checks whether AI search engines cite your target domains for a prompt. $0.75/call via MCP.

7 tools answering

Reecopedia — questions

Answers built from our own checks of this server.

What can Reecopedia do?
It exposes 8 tools, read directly from the server on our last check. Among them: about_reecopedia, document_outline, fetch, find_exact_text, list_corpus_documents, report_answer_issue and 2 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 →
Is Reecopedia working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 86 of 90 checks got a reply (95.6%), average response time 562 ms. The bar chart above shows every period we have measured.
The registry lists Reecopedia as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Reecopedia?
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 Reecopedia need an API key?
No. Reecopedia completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Reecopedia?
It answers our handshake in 562 ms on average, which is faster than 26% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.