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

PariteCK

REMOTE · WWW.ENTANGLEEQ.COM

PariteCK (formerly EntangleEQ): public pay transparency and Egapro data. Public content only.

0 this week 78 Trust /100

Last scanned (19 hours ago)

Scores higher than 72% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Trust breakdown (7 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 → 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
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 640 tokens (~128/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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
What we tested

Checks we ran (11)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 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 Oct 26 0
    • Stability: fail → pass ▲ security
  • 10 Oct 26 0
    • Tool “search” rewrote its description, which is the text the model reads security
  • 4 Oct 26 0
    • Tool “assess_readiness” 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 “request_demo_lead” rewrote its description, which is the text the model reads security
    • Tool “search” rewrote its description, which is the text the model reads security
    • “search” reworded the description of “query” cosmetic
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 21 Nov 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 25 Oct 2026 23 Jan 2027 ECDSA 256 ECDSA-SHA256 d3aa3239d9c0e473133a6ac9565a2edd
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. DS published 19718 13 Verified
entangleeq.com. DS published 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' 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://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://www.youtube-nocookie.com https://cal.com https://*.cal.com https://app.cal.com https://cal.eu https://*.cal.eu https://app.cal.eu; frame-ancestors 'self'; base-uri 'self'; form-action 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
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
MCP tools · 5 exposed · ~640 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. 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 →

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 PariteCK 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.
hasCseReportingboolean–Whether CSE/NAO reporting evidence is already assembled.
hasJobFamiliesboolean–Whether equivalent-value job families/categories are mapped.
hasPayrollExportboolean–Whether payroll export or DSN data is available.
hasPromotionDataboolean–Whether 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 PariteCK 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 ~163

Use this when a user wants to be contacted by PariteCK, or asks for a demo, a quote or a meeting. This tool does NOT transmit contact details: it returns the URL of the PariteCK 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: PariteCK does not accept contact details relayed by an assistant, because the person's consent cannot be verified.

NameTypeReqDescription
companyNamestring–Optional. Company / organisation name, kept as an anonymous usage statistic. Never a person name.
primaryTopicstring–Optional. Main interest: egapro | pay_gap | vss | csrd | global.

No output schema declared.

No examples provided.

search ~86

Use this when a ChatGPT user asks about PariteCK, Egapro, Directive (UE) 2023/970, pay transparency, the Score Parité (IDS), or PariteCK public product information. Returns public pages only.

NameTypeReqDescription
limitnumber–Maximum results to return. Default 5.
querystringyesSearch query about PariteCK 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.

Install

How do I install the PariteCK MCP server?

PariteCK 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

# add to Claude Code
claude mcp add --transport http com-entangleeq-pay-transparency 'https://www.entangleeq.com/api/mcp-public'
Common questions

What is the PariteCK MCP server?

PariteCK is an MCP server listed in the public MCP registry as com.entangleeq/pay-transparency. PariteCK (formerly EntangleEQ): public pay transparency and Egapro data. Public content only. This page covers its hosted endpoint (https://www.entangleeq.com/api/mcp-public).

Is the PariteCK MCP server safe to use?

PariteCK scores 78 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 PariteCK MCP server expose?

PariteCK exposes 5 tools: search, fetch, assess_readiness, simulate_index_2027, request_demo_lead. Their descriptions and schemas cost roughly 640 tokens of context every time the server is loaded.

Does the PariteCK MCP server require authentication?

No. We connected to PariteCK without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the PariteCK MCP server still maintained?

PariteCK is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the PariteCK MCP server?

VerifyMCP ran 11 checks on PariteCK, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about PariteCK: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.