Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

EntangleEQ

REMOTE · WWW.ENTANGLEEQ.COM · SCANNED AUG 3

EU pay transparency (Directive 2023/970) and French Egapro readiness assistant. Public data only.

+2 this week 65 Trust /100
Trust breakdown (6 categories)

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 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 not yet verified: we couldn't determine whether a plaintext access path exists. 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
Schema Quality & AI Usability74
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 676 tokens (~135/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 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

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 · www.entangleeq.com

# add to Claude Code
claude mcp add --transport http com-entangleeq-pay-transparency https://www.entangleeq.com/api/mcp-public
# ~/.codex/config.toml
[mcp_servers.com-entangleeq-pay-transparency]
url = "https://www.entangleeq.com/api/mcp-public"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-entangleeq-pay-transparency": {
      "type": "remote",
      "url": "https://www.entangleeq.com/api/mcp-public",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-entangleeq-pay-transparency --url https://www.entangleeq.com/api/mcp-public --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-entangleeq-pay-transparency:
    url: "https://www.entangleeq.com/api/mcp-public"
// mcp.json
{
  "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.

Changelog

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.

  • 2 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 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 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 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.

  • 27 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
  • 26 Jul 26 62

    First indexed and scored.

Diagnostics

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://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 29 Jun 2026 27 Sept 2026 ECDSA 256 ECDSA-SHA256 5d762db0e83857b60e7b4c262e1e65f8
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
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=()
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
MCP tools — 5 exposed · ~676 tokens

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.

Tool Tokens
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.

NameTypeReqDescription
countrystringyesCompany country, for example France. Required.
hasCseReportingbooleanWhether CSE/NAO reporting evidence is already assembled.
hasJobFamiliesbooleanWhether equivalent-value job families/categories are mapped.
hasPayrollExportbooleanWhether payroll export or DSN data is available.
hasPromotionDatabooleanWhether promotion data is available.
headcountintegeryesApproximate 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.

NameTypeReqDescription
idstringyesPublic page id returned by search.

No output schema declared.

No examples provided.

request_demo_lead ~204

Use this ONLY after a user has explicitly agreed to be contacted by EntangleEQ, to submit their demo request. Records a demo request that the EntangleEQ team reviews before any follow-up. Collect the minimum needed: company name, contact name, and a professional email. Do NOT include salaries, employee names, or any sensitive personal/HR data in the message. Requires userConsent: true.

NameTypeReqDescription
companyNamestringyesCompany / organisation name.
contactNamestringyesName of the person to contact back.
emailstringyesProfessional email to reach the contact.
messagestringOptional short context. No sensitive personal data, no salaries, no employee names.
primaryTopicstringMain interest: egapro | pay_gap | vss | csrd | global.
userConsentbooleanyesMust be true. Confirms the end user explicitly agreed to share these contact details with EntangleEQ.

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.

NameTypeReqDescription
limitnumberMaximum results to return. Default 5.
querystringyesSearch 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.

NameTypeReqDescription
querystringyesA 9-digit SIREN or a company name (raison sociale). Minimum 3 characters.

No output schema declared.

No examples provided.