Reecopedia
REMOTE · IA.REECO.ECO · SCANNED AUG 3
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 →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1121 tokens (~160/item across 7 items; 7 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · ia.reeco.eco
claude mcp add --transport http eco-reeco-reecopedia 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": {
"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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 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
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 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
- 26 Jul 26 62
First indexed and scored.
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 3 Aug 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=YE1,O=Let's Encrypt,C=US | 24 Jul 2026 | 22 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 510882eb5c24d9affe54e7bc492a0018d2c |
| SANs: *.reeco.eco, reeco.eco | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 |
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 |
| 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=() |
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.
about_reecopedia About Reecopedia & privacy ~26
What Reecopedia is, who runs it, and its privacy policy.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
document_outline Document outline (headings index) ~114
Return the heading tree (table of sections) of an indexed document, so you can explore its structure before fetching pages. Each entry has the heading text, its full path, depth and first page: pass the page to `fetch` as "<document>#p<page>" to read it.
| Name | Type | Req | Description |
|---|---|---|---|
| document | string | yes | Exact source file name as returned by `search` / `search_eu_textile_regulations` (e.g. "CELEX-02024R1781-20240628.pdf"). |
Structured output declared, but exposes no named fields.
No examples provided.
fetch Fetch document page (deep research interface) ~62
Fetch the full text of a regulatory document page returned by `search`.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A result id from `search`, format "<source-file>#p<page>" (e.g. "REG_2024_1781_ESPR_EN.pdf#p39"). |
Structured output declared, but exposes no named fields.
No examples provided.
find_exact_text Find exact text (literal search) ~211
Find literal occurrences of an exact string in the corpus — article numbers, regulation ids, precise wording (e.g. "Article 8(3)", "2024/1781"). Complements semantic `search`: use this when you need the exact string, not the concept. Returns one match per (file, page) with an occurrence count and a text snippet; read the full page with `fetch`. Scans the literal chunk text of both indexes the semantic search serves (the two chunkings differ, so some passages exist in only one); the synthetic contextual enrichment is NOT scanned — it is not document text.
| Name | Type | Req | Description |
|---|---|---|---|
| case_sensitive | boolean | — | Exact-case match (default False). |
| document | string | — | Optional exact source file name to restrict the search. |
| max_results | integer | — | Max (file, page) matches to return (1-50, default 20). |
| text | string | yes | The exact string to find (min 3 characters). |
Structured output declared, but exposes no named fields.
No examples provided.
report_answer_issue Report a wrong or misleading answer ~144
Report that an answer built from Reecopedia search results was wrong, misleading or incomplete. The report (query + reason, nothing else — no personal data) enters Reecopedia's human curation queue and is reviewed weekly to correct the corpus and retrieval quality. Call this when the user flags an answer as wrong, or when you notice the retrieved passages contradict the answer you gave.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The original search query the bad answer was built from. |
| reason | string | yes | 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 (deep research interface) ~103
Search EU textile sustainability regulations (ESPR, DPP, CSRD, CBAM, EU ETS, CWA 18291, JRC studies). Deep-research interface: returns a list of matching regulatory passages as {results: [{id, title, text, url}]}. Pass a result `id` to the `fetch` tool to get the full document page.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The regulatory question, in any language (English works best). |
Structured output declared, but exposes no named fields.
No examples provided.
search_eu_textile_regulations Search EU textile regulations ~136
Search the Reecopedia corpus of EU textile sustainability regulations. Returns the most relevant regulatory passages with citations (source file, page, section). Answer the user's question ONLY from these passages and cite them. Corpus: ESPR 2024/1781, Digital Product Passport, CSRD, CBAM, EU ETS, CWA 18291, JRC BREF and textile preparatory studies, EP studies.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The regulatory question, in any language (English works best). |
| top_k | integer | — | Number of passages to return (1-10, default 10). |
Structured output declared, but exposes no named fields.
No examples provided.