EntangleEQ
REMOTE · WWW.ENTANGLEEQ.COM · SCANNED SEP 25
EU pay transparency (Directive 2023/970) and French Egapro readiness assistant. Public data only.
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 Security54
- 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 5 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 enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 635 tokens (~127/item across 5 items; 5 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 Management88
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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 EntangleEQ MCP server?
EntangleEQ is a hosted endpoint at https://www.entangleeq.com/api/mcp-public, 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 · www.entangleeq.com
claude mcp add --transport http com-entangleeq-pay-transparency 'https://www.entangleeq.com/api/mcp-public'
{
"mcpServers": {
"com-entangleeq-pay-transparency": {
"url": "https://www.entangleeq.com/api/mcp-public"
}
}
} {
"servers": {
"com-entangleeq-pay-transparency": {
"type": "http",
"url": "https://www.entangleeq.com/api/mcp-public"
}
}
} [mcp_servers.com-entangleeq-pay-transparency] url = "https://www.entangleeq.com/api/mcp-public"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-entangleeq-pay-transparency": {
"type": "remote",
"url": "https://www.entangleeq.com/api/mcp-public",
"enabled": true
}
}
} openclaw mcp add com-entangleeq-pay-transparency --url 'https://www.entangleeq.com/api/mcp-public' --transport streamable-http
mcp_servers:
com-entangleeq-pay-transparency:
url: "https://www.entangleeq.com/api/mcp-public" {
"McpServers": {
"com-entangleeq-pay-transparency": {
"Transport": "http",
"Url": "https://www.entangleeq.com/api/mcp-public"
}
}
} assistant mcp add com-entangleeq-pay-transparency -t streamable-http -u 'https://www.entangleeq.com/api/mcp-public'
{
"mcpServers": {
"com-entangleeq-pay-transparency": {
"type": "http",
"url": "https://www.entangleeq.com/api/mcp-public"
}
}
} 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.
- 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
- 20 Sept 26 −1
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “request_demo_lead” rewrote its description, which is the text the model reads security
- “request_demo_lead” dropped the required parameter “contactName” ▼ functional
- “request_demo_lead” dropped the required parameter “email” ▼ functional
- “request_demo_lead” dropped the required parameter “userConsent” ▼ functional
- “request_demo_lead” reworded the description of “companyName” cosmetic
- “request_demo_lead” reworded the description of “primaryTopic” cosmetic
- “request_demo_lead” dropped the optional parameter “message” cosmetic
- “request_demo_lead” made “companyName” optional cosmetic
- 26 Aug 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 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 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
- 31 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
- 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 0
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 25 Sept 2026 · Probed https://www.entangleeq.com/api/mcp-public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.entangleeq.com | CN=WE1,O=Google Trust Services,C=US | 27 Aug 2026 | 25 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 8ba7fb1b1516fe8d13971554ade8d652 |
| SANs: www.entangleeq.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 secure
Validation of www.entangleeq.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| entangleeq.com. | present | 26326 | 13 | Verified |
| www.entangleeq.com. | Verified address RRset verified with the apex keys |
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=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://cal.com https://*.cal.com https://app.cal.com https://cal.eu https://*.cal.eu https://app.cal.eu; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: blob: https:; connect-src 'self' https://api.anthropic.com https://s3.fr-par.scw.cloud https://*.s3.fr-par.scw.cloud https://api.resend.com https://cal.com https://*.cal.com https://app.cal.com https://cal.eu https://*.cal.eu https://app.cal.eu; frame-src 'self' https://www.youtube.com https://youtube.com https://cal.com https://*.cal.com https://app.cal.com https://cal.eu https://*.cal.eu https://app.cal.eu; frame-ancestors 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.entangleeq.com/api/mcp-public | Verified | 200 | |
| http (plaintext) | http://www.entangleeq.com/api/mcp-public | Inconclusive | 406 |
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 →
assess_readiness ~174
Use this when a user wants a first-pass readiness check for French/EU pay transparency obligations before requesting an EntangleEQ demo. country and headcount are required — the tool rejects the call (rather than guessing) if they are missing or mis-named, so obligation applicability is never inferred from incomplete input.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | Company country, for example France. Required. |
| hasCseReporting | boolean | – | Whether CSE/NAO reporting evidence is already assembled. |
| hasJobFamilies | boolean | – | Whether equivalent-value job families/categories are mapped. |
| hasPayrollExport | boolean | – | Whether payroll export or DSN data is available. |
| hasPromotionData | boolean | – | Whether promotion data is available. |
| headcount | integer | yes | Approximate employee count (positive whole number). Required. |
No output schema declared.
No examples provided.
fetch ~49
Use this when ChatGPT needs the full public text for a specific EntangleEQ page returned by search. Never returns private company or employee data.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Public page id returned by search. |
No output schema declared.
No examples provided.
request_demo_lead ~163
Use this when a user wants to be contacted by EntangleEQ, or asks for a demo, a quote or a meeting. This tool does NOT transmit contact details: it returns the URL of the EntangleEQ contact form, which the user must fill in themselves. Show them the returned URL. Never send a name, an email, a phone number or any personal data through this tool: EntangleEQ does not accept contact details relayed by an assistant, because the person's consent cannot be verified.
| Name | Type | Req | Description |
|---|---|---|---|
| companyName | string | – | Optional. Company / organisation name, kept as an anonymous usage statistic. Never a person name. |
| primaryTopic | string | – | Optional. Main interest: egapro | pay_gap | vss | csrd | global. |
No output schema declared.
No examples provided.
search ~81
Use this when a ChatGPT user asks about EntangleEQ, Egapro, Directive UE 2023/970, pay transparency, Inclusion Depth Score, or EntangleEQ public product information. Returns public pages only.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum results to return. Default 5. |
| query | string | yes | Search query about EntangleEQ public content. |
No output schema declared.
No examples provided.
simulate_index_2027 ~168
Use this when a French employer (or their advisor) asks what the reform of the French gender-equality index (Index Egapro) means for them, or wants to look up a company's current published index by SIREN or company name. Given a 9-digit SIREN or a company name, returns the latest public Egapro declaration (global score + the 5 current indicators) and the framing of the move to the 7 indicators of the pay-transparency bill (which are new-data indicators, and the 2026 data checklist). Public data only; no private company or employee data. Estimate for decision-support, not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A 9-digit SIREN or a company name (raison sociale). Minimum 3 characters. |
No output schema declared.
No examples provided.
What is the EntangleEQ MCP server?
EntangleEQ is an MCP server listed in the public MCP registry as com.entangleeq/pay-transparency. EU pay transparency (Directive 2023/970) and French Egapro readiness assistant. Public data only. This page covers its hosted endpoint (https://www.entangleeq.com/api/mcp-public).
Is the EntangleEQ MCP server safe to use?
EntangleEQ scores 77 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 EntangleEQ MCP server expose?
EntangleEQ exposes 5 tools: search, fetch, assess_readiness, simulate_index_2027, request_demo_lead. Their descriptions and schemas cost roughly 635 tokens of context every time the server is loaded.
Does the EntangleEQ MCP server require authentication?
No. We connected to EntangleEQ without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the EntangleEQ MCP server still maintained?
EntangleEQ is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.