Reecopedia
REMOTE · IA.REECO.ECO · SCANNED OCT 15
Regulatory search engine for EU textile sustainability law: ESPR, DPP, CSRD, CBAM, CWA 18291.
Available components
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability57
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1441 tokens (~180/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage68
- 88% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
- 14% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Reecopedia MCP server?
Reecopedia is a hosted endpoint at https://ia.reeco.eco/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 · ia.reeco.eco
claude mcp add --transport http eco-reeco-reecopedia 'https://ia.reeco.eco/mcp'
{
"mcpServers": {
"eco-reeco-reecopedia": {
"url": "https://ia.reeco.eco/mcp"
}
}
} {
"servers": {
"eco-reeco-reecopedia": {
"type": "http",
"url": "https://ia.reeco.eco/mcp"
}
}
} [mcp_servers.eco-reeco-reecopedia] url = "https://ia.reeco.eco/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"eco-reeco-reecopedia": {
"type": "remote",
"url": "https://ia.reeco.eco/mcp",
"enabled": true
}
}
} openclaw mcp add eco-reeco-reecopedia --url 'https://ia.reeco.eco/mcp' --transport streamable-http
mcp_servers:
eco-reeco-reecopedia:
url: "https://ia.reeco.eco/mcp" {
"McpServers": {
"eco-reeco-reecopedia": {
"Transport": "http",
"Url": "https://ia.reeco.eco/mcp"
}
}
} assistant mcp add eco-reeco-reecopedia -t streamable-http -u 'https://ia.reeco.eco/mcp'
{
"mcpServers": {
"eco-reeco-reecopedia": {
"type": "http",
"url": "https://ia.reeco.eco/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 12 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
- Stability: 0.97 → pass security
- Tool “document_outline” rewrote its description, which is the text the model reads security
- Tool “fetch” rewrote its description, which is the text the model reads security
- 22 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search” rewrote its description, which is the text the model reads security
- Tool “search_eu_textile_regulations” rewrote its description, which is the text the model reads security
- 21 Sept 26 0
- Tool “fetch” rewrote its description, which is the text the model reads security
- 19 Sept 26 −1
- Stability: pass → 0.87 functional
- 18 Sept 26 −3
- Stability: 0.97 → pass security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “about_reecopedia” rewrote its description, which is the text the model reads security
- Tool “document_outline” rewrote its description, which is the text the model reads security
- Tool “fetch” rewrote its description, which is the text the model reads security
- Tool “find_exact_text” rewrote its description, which is the text the model reads security
- Tool “list_corpus_documents” rewrote its description, which is the text the model reads security
- Tool “search” rewrote its description, which is the text the model reads security
- Tool “search_eu_textile_regulations” rewrote its description, which is the text the model reads security
- Tool coverage: 100% → 14% ▼ functional
- Tool coverage: 100% → 88% ▼ functional
- Schema quality: 441 → 153 ▲ functional
- Schema quality: excellent → good functional
- Server version: 1.4.1 → 2.0.0 functional
- “search_eu_textile_regulations” added an optional parameter “scope” cosmetic
- “document_outline” reworded the description of “document” cosmetic
- “fetch” reworded the description of “id” cosmetic
- “find_exact_text” reworded the description of “case_sensitive” cosmetic
- “find_exact_text” reworded the description of “document” cosmetic
- “find_exact_text” reworded the description of “max_results” cosmetic
- “find_exact_text” reworded the description of “text” cosmetic
- “list_corpus_documents” reworded the description of “contains” cosmetic
- “list_corpus_documents” reworded the description of “max_results” cosmetic
- “search” reworded the description of “query” cosmetic
- “search_eu_textile_regulations” reworded the description of “query” cosmetic
- “search_eu_textile_regulations” reworded the description of “top_k” cosmetic
- Tool “about_reecopedia” changed its title: About Reecopedia & privacy → About Reecopedia cosmetic
- Tool “document_outline” changed its title: Document outline (headings index) → Document structure cosmetic
- Tool “fetch” changed its title: Fetch document page (deep research interface) → Read original evidence cosmetic
- Tool “find_exact_text” changed its title: Find exact text (literal search) → Find exact text cosmetic
- Tool “list_corpus_documents” changed its title: List the documents in the corpus → List corpus documents cosmetic
- Tool “report_answer_issue” changed its title: Report a wrong or misleading answer → Report an answer issue cosmetic
- Tool “search” changed its title: Search (deep research interface) → Search regulatory documents cosmetic
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 15 Oct 2026 · Probed https://ia.reeco.eco/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=reeco.eco | CN=YE2,O=Let's Encrypt,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6c8dd273fdbcfe767c65a33b145610cba27 |
| SANs: *.reeco.eco, reeco.eco | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ia.reeco.eco. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| eco. | present | 28231 | 8 | Verified |
| reeco.eco. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.googletagmanager.com https://www.google-analytics.com https://static.cloudflareinsights.com https://snap.licdn.com https://cdn.iubenda.com https://cs.iubenda.com https://cdn.jsdelivr.net; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://cdn.iubenda.com https://cdn.jsdelivr.net; font-src 'self' data: https://fonts.gstatic.com https://cdn.iubenda.com; img-src 'self' data: blob: https:; connect-src 'self' https://ia.reeco.eco https://www.google-analytics.com https://*.google-analytics.com https://*.analytics.google.com https://stats.g.doubleclick.net https://www.googletagmanager.com https://px.ads.linkedin.com https://*.iubenda.com https://cloudflareinsights.com; frame-src 'self' https://www.youtube-nocookie.com https://www.googletagmanager.com https://*.iubenda.com; worker-src 'self' blob:; frame-ancestors 'self'; base-uri 'self'; object-src 'none'; form-action 'self' https://reeco.eco |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), camera=(), microphone=(), payment=(), usb=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ia.reeco.eco/mcp | Verified | 200 | |
| http (plaintext) | http://ia.reeco.eco/mcp | HTTPS enforced | 301 | https://ia.reeco.eco/mcp |
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 →
about_reecopedia About Reecopedia ~8
No description provided.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
document_outline Document structure ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| document | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
fetch Read original evidence ~52
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
find_exact_text Find exact text ~54
Locate a literal string in the current corpus, optionally restricted to a document.
| Name | Type | Req | Description |
|---|---|---|---|
| case_sensitive | boolean | – | – |
| document | string | – | – |
| max_results | integer | – | – |
| text | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_corpus_documents List corpus documents ~33
List indexed document names matching a substring.
| Name | Type | Req | Description |
|---|---|---|---|
| contains | string | – | – |
| max_results | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
report_answer_issue Report an answer issue ~320
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The original search query the reported answer was built from. |
| reason | string | yes | The user's reason why the answer was wrong (min 10 chars — e.g. which fact was incorrect, which source was misread, what was missing). |
Structured output declared, but exposes no named fields.
No examples provided.
search Search regulatory documents ~49
Return cited corpus results by id; use fetch for full source text. The client verifies the evidence. Query embeddings use Alibaba; candidate passages go to Jina for reranking.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_eu_textile_regulations Search EU textile regulations ~95
Search regulatory evidence in English legal register. Cite original document and unit; verify each claim. Optional scope narrows corpus partitions. No model assesses the answer in this MCP tool; the client must verify each claim against the returned text. Query embeddings use Alibaba; candidate passages are sent to Jina for reranking.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| scope | – | – | – |
| top_k | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Reecopedia MCP server?
Reecopedia is an MCP server listed in the public MCP registry as eco.reeco/reecopedia. Regulatory search engine for EU textile sustainability law: ESPR, DPP, CSRD, CBAM, CWA 18291. This page covers its hosted endpoint (https://ia.reeco.eco/mcp).
Is the Reecopedia MCP server safe to use?
Reecopedia 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 Reecopedia MCP server expose?
Reecopedia exposes 8 tools: search_eu_textile_regulations, search, fetch, document_outline, find_exact_text, and 3 more. Their descriptions and schemas cost roughly 674 tokens of context every time the server is loaded.
Does the Reecopedia MCP server require authentication?
No. We connected to Reecopedia without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Reecopedia MCP server still maintained?
Reecopedia is still listed as active in the MCP registry. We last reached this channel on 15 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.