EQIQs
REMOTE · ADGMSNWJYNQKHAWHIOIL.SUPABASE.CO
EQIQs: 21-framework personality and compatibility for coaching, communication, and team development.
Available components
Last scanned (21 hours ago)
Scores higher than 98% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Project Management
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2573 tokens (~160/item across 16 items; 16 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 Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% 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 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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.
- 30 Oct 26 0
- Tool “create_profile” rewrote its description, which is the text the model reads security
- “create_profile” reworded the description of “attachment_style” cosmetic
- “create_profile” reworded the description of “date_of_birth” cosmetic
- “create_profile” reworded the description of “disc_type” cosmetic
- “create_profile” reworded the description of “enneagram_type” cosmetic
- “create_profile” reworded the description of “eq_score” cosmetic
- “create_profile” reworded the description of “mbti_type” cosmetic
- 26 Oct 26 +2
- Stability: fail → pass ▲ security
- 20 Oct 26 0
- Tool “suggest_lead” rewrote its description, which is the text the model reads security
- “generate_narrative” added an optional parameter “confirm_cost” cosmetic
- 19 Oct 26 0
- “start_assessment” added an optional parameter “context” cosmetic
- “start_assessment” added an optional parameter “personal_consent” cosmetic
- “submit_assessment” added an optional parameter “context” cosmetic
- “submit_assessment” added an optional parameter “personal_consent” cosmetic
- “start_assessment” reworded the description of “framework” cosmetic
5 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 29 Sept 26 0
- Tool “add_note” now declares an output schema ▲ functional
- Tool “create_profile” now declares an output schema ▲ functional
- Tool “generate_narrative” now declares an output schema ▲ functional
- Tool “get_my_profile” now declares an output schema ▲ functional
- Tool “get_profile” now declares an output schema ▲ functional
- Tool “invite_person” now declares an output schema ▲ functional
- Tool “list_invites” now declares an output schema ▲ functional
- Tool “list_notes” now declares an output schema ▲ functional
- Tool “list_profiles” now declares an output schema ▲ functional
- Tool “list_relationships” now declares an output schema ▲ functional
- Tool “prep_meeting” now declares an output schema ▲ functional
- Tool “score_compatibility” now declares an output schema ▲ functional
- Tool “score_team” now declares an output schema ▲ functional
- Tool “start_assessment” now declares an output schema ▲ functional
- Tool “submit_assessment” now declares an output schema ▲ functional
- Tool “suggest_lead” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Server version: 0.6.0 → 0.7.0 functional
- 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
- 26 Sept 26 0
- Stability: 0.87 → fail ▼ security
- Tool “add_note” rewrote its description, which is the text the model reads security
- Tool “create_profile” rewrote its description, which is the text the model reads security
- Tool “generate_narrative” rewrote its description, which is the text the model reads security
- Tool “get_my_profile” rewrote its description, which is the text the model reads security
- Tool “get_profile” rewrote its description, which is the text the model reads security
- Tool “invite_person” rewrote its description, which is the text the model reads security
- Tool “list_invites” rewrote its description, which is the text the model reads security
- Tool “list_notes” rewrote its description, which is the text the model reads security
- Tool “list_profiles” rewrote its description, which is the text the model reads security
- Tool “list_relationships” rewrote its description, which is the text the model reads security
- Tool “prep_meeting” rewrote its description, which is the text the model reads security
- Tool “score_compatibility” rewrote its description, which is the text the model reads security
- Tool “score_team” rewrote its description, which is the text the model reads security
- Tool “start_assessment” rewrote its description, which is the text the model reads security
- Tool “submit_assessment” rewrote its description, which is the text the model reads security
- Tool “suggest_lead” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- “list_invites” changed the type of “limit”: number → integer ▼ functional
- “list_notes” changed the type of “limit”: number → integer ▼ functional
- “list_profiles” changed the type of “limit”: number → integer ▼ functional
- “list_relationships” changed the type of “limit”: number → integer ▼ functional
- Tool coverage: 12% → 100% ▲ functional
- Schema quality: good → excellent functional
- Server version: 0.4.0 → 0.6.0 functional
- “add_note” reworded the description of “note” cosmetic
- “add_note” reworded the description of “person” cosmetic
- “create_profile” reworded the description of “attachment_style” cosmetic
- “create_profile” reworded the description of “date_of_birth” cosmetic
- “create_profile” reworded the description of “department” cosmetic
- “create_profile” reworded the description of “disc_type” cosmetic
- “create_profile” reworded the description of “email” cosmetic
- “create_profile” reworded the description of “enneagram_type” cosmetic
- “create_profile” reworded the description of “eq_score” cosmetic
- “create_profile” reworded the description of “mbti_type” cosmetic
- “create_profile” reworded the description of “name” cosmetic
- “generate_narrative” reworded the description of “audience” cosmetic
- “generate_narrative” reworded the description of “compare_with” cosmetic
- “generate_narrative” reworded the description of “context” cosmetic
- “generate_narrative” reworded the description of “focus” cosmetic
- “generate_narrative” reworded the description of “length” cosmetic
- “generate_narrative” reworded the description of “person” cosmetic
- “get_my_profile” reworded the description of “context” cosmetic
- “get_profile” reworded the description of “context” cosmetic
- “get_profile” reworded the description of “email” cosmetic
- “get_profile” reworded the description of “name” cosmetic
- “get_profile” reworded the description of “profile_id” cosmetic
- “invite_person” reworded the description of “email” cosmetic
- “invite_person” reworded the description of “name” cosmetic
- “invite_person” reworded the description of “person” cosmetic
- “invite_person” reworded the description of “send_email” cosmetic
- “list_invites” reworded the description of “limit” cosmetic
- “list_invites” reworded the description of “status” cosmetic
- “list_notes” reworded the description of “limit” cosmetic
- “list_notes” reworded the description of “person” cosmetic
- “list_profiles” reworded the description of “context” cosmetic
- “list_profiles” reworded the description of “limit” cosmetic
- “list_profiles” reworded the description of “search” cosmetic
- “list_relationships” reworded the description of “context” cosmetic
- “list_relationships” reworded the description of “limit” cosmetic
- “prep_meeting” reworded the description of “department” cosmetic
- “prep_meeting” reworded the description of “goal” cosmetic
- “prep_meeting” reworded the description of “members” cosmetic
- “score_compatibility” reworded the description of “context” cosmetic
- “score_compatibility” reworded the description of “person_a” cosmetic
- “score_compatibility” reworded the description of “person_b” cosmetic
- “score_team” reworded the description of “context” cosmetic
- “score_team” reworded the description of “department” cosmetic
- “score_team” reworded the description of “label” cosmetic
- “score_team” reworded the description of “members” cosmetic
- “start_assessment” reworded the description of “framework” cosmetic
- “submit_assessment” reworded the description of “answers” cosmetic
- “submit_assessment” reworded the description of “framework” cosmetic
- “suggest_lead” reworded the description of “department” cosmetic
- “suggest_lead” reworded the description of “kind” cosmetic
- “suggest_lead” reworded the description of “members” cosmetic
- “suggest_lead” reworded the description of “project” cosmetic
- Tool “add_note” changed its title: Add a note cosmetic
- Tool “create_profile” changed its title: Add a person cosmetic
- Tool “generate_narrative” changed its title: Write a coaching narrative cosmetic
- Tool “get_my_profile” changed its title: Get my profile cosmetic
- Tool “get_profile” changed its title: Get a person's profile cosmetic
- Tool “invite_person” changed its title: Invite someone to compare cosmetic
- Tool “list_invites” changed its title: List invites cosmetic
- Tool “list_notes” changed its title: List notes cosmetic
- Tool “list_profiles” changed its title: List people cosmetic
- Tool “list_relationships” changed its title: List saved pairings cosmetic
- Tool “prep_meeting” changed its title: Prepare for a meeting cosmetic
- Tool “score_compatibility” changed its title: Score two people cosmetic
- Tool “score_team” changed its title: Score a team cosmetic
- Tool “start_assessment” changed its title: Start an assessment in chat cosmetic
- Tool “submit_assessment” changed its title: Submit assessment answers cosmetic
- Tool “suggest_lead” changed its title: Suggest who should lead cosmetic
- 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
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 5 Nov 2026 · Probed https://adgmsnwjynqkhawhioil.supabase.co/functions/v1/mcp-server
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=supabase.co | CN=WE1,O=Google Trust Services,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | d2b50611cd88e9c50e4e2231f4d3f059 |
| SANs: supabase.co, *.supabase.co | ||||||
| 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 insecure
Validation of adgmsnwjynqkhawhioil.supabase.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| co. | DS published | 7786 | 8 | Verified |
| supabase.co. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp", resource_metadata="https://adgmsnwjynqkhawhioil.supabase.co/functions/v1/mcp-server/.well-known/oauth-protected-resource", error="invalid_token", error_description="Access token is not a JWT"
Bearer realm="mcp", resource_metadata="https://adgmsnwjynqkhawhioil.supabase.co/functions/v1/mcp-server/.well-known/oauth-protected-resource", error="invalid_token", error_description="Access token is not a JWT"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Protected resource metadata
| Document | https://adgmsnwjynqkhawhioil.supabase.co/functions/v1/mcp-server/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://adgmsnwjynqkhawhioil.supabase.co/functions/v1/mcp-server |
| Authorisation server | https://adgmsnwjynqkhawhioil.supabase.co/auth/v1 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://adgmsnwjynqkhawhioil.supabase.co/functions/v1/mcp-server | Verified | 200 | |
| http (plaintext) | http://adgmsnwjynqkhawhioil.supabase.co/functions/v1/mcp-server | HTTPS enforced | 301 | https://adgmsnwjynqkhawhioil.supabase.co/functions/v1/mcp-server |
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 →
add_note Add a note ~116
Save a private note or check-in on one person in the user's workspace; it appears on their EQIQs profile. Use after 1:1s or when the user asks to remember something about someone. Costs 1 unit.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | yes | Note text (up to 4,000 characters). |
| person | string | yes | Who the note is about. Accepts a profile id, an exact email, or a full name. If a name matches more than one person the tool asks which one instead of guessing. |
| Name | Type | Req | Description |
|---|---|---|---|
| created_at | string | – | When the note was saved (ISO 8601). |
| note_id | string | – | Id of the saved note. |
| person | string | – | Who the note is about. |
| profile_id | string | – | Profile id of that person. |
No examples provided.
create_profile Add a person ~274
Add a new person to the user's workspace with a name and, optionally, type labels the person has shared themselves (MBTI, DISC, Enneagram). Birthdate, attachment style and scores are never saved here — use invite_person so the person answers for themselves. Returns the new profile id. Costs 1 unit.
| Name | Type | Req | Description |
|---|---|---|---|
| attachment_style | string | – | Ignored and never saved — the person adds this themselves via invite_person. |
| date_of_birth | string | – | Ignored and never saved — the person adds this themselves via invite_person. |
| department | string | – | Optional team or department, used by score_team, prep_meeting and suggest_lead. |
| disc_type | string | – | Optional DISC style (D, I, S, C or a blend), only if the person shared it themselves. |
| string | – | Optional email; used to match results if they later take the assessment. | |
| enneagram_type | string | – | Optional Enneagram type 1-9, only if the person shared it themselves. |
| eq_score | number | – | Ignored and never saved — scores come only from the person's own assessment. |
| mbti_type | string | – | Optional four-letter MBTI type, only if the person shared it themselves. |
| name | string | yes | Full name (required). |
| Name | Type | Req | Description |
|---|---|---|---|
| profile | object | – | The newly created profile. |
No examples provided.
generate_narrative Write a coaching narrative ~275
Premium: write a plain-language coaching narrative for one person, or for a pair when compare_with is given, synthesized from all 21 frameworks. Business context stays on working behavior only. Slower than other tools. Costs 5 units.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | Who will read it. Hiring or candidate-screening audiences are intentionally not supported. |
| compare_with | string | – | Optional second person for a pair narrative. Accepts a profile id, an exact email, or a full name. If a name matches more than one person the tool asks which one instead of guessing. |
| confirm_cost | boolean | – | Set true only after the user explicitly approves the five-unit cost. False returns a no-charge confirmation prompt. |
| context | string | – | Relationship context that sets framework weighting. 'business' (default) is work-safe and withholds personal-life signals (love language, attachment style, date of birth); the other contexts include… |
| focus | string | – | Optional topic to emphasize, e.g. 'giving feedback'. |
| length | string | – | Approximate length of the narrative. |
| person | string | yes | Who the narrative is about. Accepts a profile id, an exact email, or a full name. If a name matches more than one person the tool asks which one instead of guessing. |
| Name | Type | Req | Description |
|---|---|---|---|
| action_items | – | – | Action items pulled from the narrative. |
| audience | string | – | Who the narrative is written for. |
| billing | object | – | Units billed. |
| compared_with | string|null | – | Second person, for pair narratives. |
| context | string|null | – | Relationship context for pair narratives. |
| disclaimer | string | – | Decision-support disclaimer. |
| guardrails | object | – | Safety check results. |
| narrative | string | – | The written coaching narrative. |
| requires_confirmation | boolean | – | True when the price must be confirmed before running. |
| scoring | – | – | Scores the narrative is based on. |
| sections | – | – | Narrative split into sections. |
| subject | string | – | Person the narrative is about. |
| units | number | – | Tool-call units this narrative costs. |
No examples provided.
get_my_profile Get my profile ~139
Return the signed-in user's own EQIQs profile: results across the 21-framework battery (MBTI, Big Five, Enneagram, DISC, EQ and more), plain-language labels, and which frameworks are still missing. Use when the user asks about themselves, e.g. 'what is my Enneagram type?' or 'how do I come across at work?'. Read-only; costs 1 unit.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Relationship context that sets framework weighting. 'business' (default) is work-safe and withholds personal-life signals (love language, attachment style, date of birth); the other contexts include… |
| Name | Type | Req | Description |
|---|---|---|---|
| context | string|null | – | Relationship context the profile was filtered for. |
| framework_coverage | number | – | How many of the 21 frameworks have data. |
| frameworks_total | number | – | Total frameworks EQIQs uses (21). |
| frameworks_withheld | number | – | How many frameworks are hidden in this context (e.g. personal-life signals at work). |
| label_meanings | object | – | Plain-language meanings for the framework labels on the profile. |
| matched_by | string | – | How the signed-in user's own profile was found. |
| profile | object | – | The person's profile fields that are visible in this context. |
No examples provided.
get_profile Get a person's profile ~148
Return the full 21-framework read for one saved person: results per framework with plain-language labels, strengths, and working-style notes. Provide exactly one of profile_id, email or name. Read-only; costs 1 unit.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Relationship context that sets framework weighting. 'business' (default) is work-safe and withholds personal-life signals (love language, attachment style, date of birth); the other contexts include… |
| string | – | The person's exact email. | |
| name | string | – | Full name. Ambiguous names return a list to choose from rather than a guess. |
| profile_id | string | – | Profile id from list_profiles (preferred). |
| Name | Type | Req | Description |
|---|---|---|---|
| context | string|null | – | Relationship context the profile was filtered for. |
| framework_coverage | number | – | How many of the 21 frameworks have data. |
| frameworks_total | number | – | Total frameworks EQIQs uses (21). |
| frameworks_withheld | number | – | How many frameworks are hidden in this context (e.g. personal-life signals at work). |
| label_meanings | object | – | Plain-language meanings for the framework labels on the profile. |
| profile | object | – | The person's profile fields that are visible in this context. |
No examples provided.
invite_person Invite someone to compare ~186
Create a private invite link for someone to take the EQIQs assessment and compare with the user. Finishing the assessment is their consent to share results. Optionally emailed by EQIQs; otherwise the link is returned to hand over. Limited to 10 invites per hour; no self-invites or opted-out addresses. Costs 1 unit.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Invitee's email, when they are not saved yet. | |
| name | string | – | Invitee's name, shown in the invite. |
| person | string | – | Existing saved person to invite (optional if email is given). Accepts a profile id, an exact email, or a full name. If a name matches more than one person the tool asks which one instead of guessing. |
| send_email | boolean | – | true: EQIQs emails the link. false: only return the link. |
| Name | Type | Req | Description |
|---|---|---|---|
| emailed | boolean | – | Whether EQIQs emailed the invite. |
| invitee | string | – | Who was invited. |
| link | string|null | – | Private invite link. |
| status | string | – | Invite status. |
No examples provided.
list_invites List invites ~66
List comparison invites the user has sent and each one's status: pending, clicked, started or completed. Read-only; costs 1 unit.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum rows to return (1-50, default 20). |
| status | string | – | Filter by status. |
| Name | Type | Req | Description |
|---|---|---|---|
| invites | array | – | Sent invites with status (sent, opened, started, finished). |
No examples provided.
list_notes List notes ~107
Read the user's saved notes and check-ins on one person, newest first. Use before a 1:1 or with prep_meeting. Read-only; costs 1 unit.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum rows to return (1-100, default 20). |
| person | string | yes | Whose notes to read. Accepts a profile id, an exact email, or a full name. If a name matches more than one person the tool asks which one instead of guessing. |
| Name | Type | Req | Description |
|---|---|---|---|
| notes | array | – | Notes, newest first. |
| person | string | – | Who the notes are about. |
| profile_id | string | – | Profile id of that person. |
No examples provided.
list_profiles List people ~142
List the people saved in the signed-in user's EQIQs workspace (id, name, department, how many of 21 frameworks are complete). Use to find someone before calling get_profile, score_compatibility or score_team. Read-only; costs 1 unit.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Relationship context that sets framework weighting. 'business' (default) is work-safe and withholds personal-life signals (love language, attachment style, date of birth); the other contexts include… |
| limit | integer | – | Maximum rows to return (1-100, default 25). |
| search | string | – | Optional case-insensitive filter on name or email. |
| Name | Type | Req | Description |
|---|---|---|---|
| profiles | array | – | Matching profiles. |
No examples provided.
list_relationships List saved pairings ~86
List compatibility pairings the user has already saved, with each pair's score and the context it was scored in. Use to recall earlier comparisons without re-scoring. Read-only; costs 1 unit.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Optional filter: only pairings scored in this context. |
| limit | integer | – | Maximum rows to return (1-100, default 25). |
| Name | Type | Req | Description |
|---|---|---|---|
| relationships | array | – | Saved pairings with their context. |
No examples provided.
prep_meeting Prepare for a meeting ~145
Build a meeting prep brief for 1-12 attendees: how to communicate with and persuade each person, and which pairings in the room need care. Name attendees or pass a department. Read-only; costs 2 units.
| Name | Type | Req | Description |
|---|---|---|---|
| department | string | – | Use everyone tagged with this department instead of naming members. Exact match first; refuses and asks for names if more than 12 people match or the name spans several departments. |
| goal | string | – | Optional meeting goal, e.g. 'agree the Q4 roadmap', used to tailor the advice. |
| members | array | – | Profile ids or full names of attendees (1-12). Omit when using department. |
| Name | Type | Req | Description |
|---|---|---|---|
| goal | string|null | – | Stated meeting goal. |
| goal_tips | array | – | Tips tied to the goal. |
| people | array | – | How to work with each attendee. |
| watch_pairs | array | – | Pairings that need care. |
| weakest_pair | – | – | The pairing with the lowest score. |
No examples provided.
score_compatibility Score two people ~221
Score how two people work (or relate) together, 0-100, with a visual score card, sub-scores (communication, values, conflict and more), why the score landed where it did, and practical tips. Use for one pair; use score_team for three or more. Decision-support only, never the sole basis for hiring, promotion or termination. Read-only; costs 1 unit.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Relationship context that sets framework weighting. 'business' (default) is work-safe and withholds personal-life signals (love language, attachment style, date of birth); the other contexts include… |
| person_a | string | yes | First person. Accepts a profile id, an exact email, or a full name. If a name matches more than one person the tool asks which one instead of guessing. |
| person_b | string | yes | Second person. Accepts a profile id, an exact email, or a full name. If a name matches more than one person the tool asks which one instead of guessing. |
| Name | Type | Req | Description |
|---|---|---|---|
| disclaimer | string | – | Decision-support disclaimer. |
| donts | array | – | Things to avoid with this person. |
| dos | array | – | Things to do with this person. |
| drivers | array | – | Frameworks that moved the score most. |
| frameworks_total | number | – | Total frameworks considered. |
| frameworks_used | number | – | Frameworks with data for both people. |
| friction_points | array | – | Where the pair is likely to clash. |
| overall_score | number | – | Overall compatibility score, 0-100. |
| strengths | array | – | Where the pair works well together. |
| subscore_reasons | array | – | Why each dimension scored as it did, with a tip. |
| subscores | object | – | Score per dimension, 0-100. |
No examples provided.
score_team Score a team ~222
Score a whole group in one call: every pairing is rolled up into a team cohesion score (visual card), the weakest shared dimension, the best-connected person, who is most isolated, pairings to watch (<55) and anchor pairings (75+), and the role mix with what is missing. Use instead of looping score_compatibility for 3+ people. Decision-support only. Read-only; costs 2 units.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Relationship context that sets framework weighting. 'business' (default) is work-safe and withholds personal-life signals (love language, attachment style, date of birth); the other contexts include… |
| department | string | – | Use everyone tagged with this department instead of naming members. Exact match first; refuses and asks for names if more than 12 people match or the name spans several departments. |
| label | string | – | Optional group name echoed in the summary. |
| members | array | – | Profile ids or full names of the people in the group (2-12). Omit when using department. |
| Name | Type | Req | Description |
|---|---|---|---|
| anchor_pairs | array | – | Strongest pairings. |
| cohesion_score | number | – | Team cohesion, 0-100. |
| connector | – | – | Best-connected member. |
| context | string | – | Relationship context used. |
| disclaimer | string | – | Decision-support disclaimer. |
| label | string|null | – | Team or department name. |
| member_count | number | – | People in the team. |
| members | array | – | Each member with their average fit. |
| most_isolated | – | – | Member furthest from the rest. |
| pair_count | number | – | Pairings scored. |
| pairs | array | – | Every pairing and its score. |
| role_coverage | – | – | Mix of working-style roles, counting each person once. |
| subscore_averages | object | – | Average score per dimension across the team. |
| thin_data | – | – | Members with too little data for a reliable read. |
| watch_pairs | array | – | Pairings that need care. |
| weakest_subscore | – | – | The team's weakest shared dimension. |
No examples provided.
start_assessment Start an assessment in chat ~123
Get the questions for one EQIQs framework so the user can take it inside the chat. Ask them one at a time, word for word, accepting only A or B. Call with no framework to list what the user has not completed yet. Personal frameworks (attachment, love language) need the user's explicit consent. Read-only; costs 1 unit.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | – |
| framework | string | – | Framework key. Omit to list remaining frameworks. |
| personal_consent | boolean | – | True only after explicit user consent to this personal framework. |
| Name | Type | Req | Description |
|---|---|---|---|
| completed | array | – | Frameworks already completed. |
| framework | string | – | Framework whose questions are returned. |
| missing | array | – | Frameworks still to take. |
| questions | array | – | Questions with A/B options. |
No examples provided.
submit_assessment Submit assessment answers ~126
Score the answers collected via start_assessment with EQIQs' own scoring and save the result to the signed-in user's profile (overwrites an earlier result for that framework). Returns the result in plain language. Costs 1 unit.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | yes | Map of question id to the user's answer, 'A' or 'B', for every question returned. |
| context | string | – | – |
| framework | string | yes | The same framework key passed to start_assessment. |
| personal_consent | boolean | – | True only after explicit user consent to save this personal framework. |
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | – | Framework scored. |
| profile_id | string | – | Profile the result was saved to. |
| result | string | – | Resulting type or level. |
No examples provided.
suggest_lead Suggest who should lead ~146
Discuss leadership considerations for 2-12 people and voluntary work (execution, people, innovation or analysis), showing available results and gaps without ranking people. Decision-support only. Read-only; costs 1 unit.
| Name | Type | Req | Description |
|---|---|---|---|
| department | string | – | Use everyone tagged with this department instead of naming members. Exact match first; refuses and asks for names if more than 12 people match or the name spans several departments. |
| kind | string | – | Kind of leadership the work needs. |
| members | array | – | Profile ids or full names of the people in the group (2-12). Omit when using department. |
| project | string | – | Optional project description echoed in the ranking. |
| Name | Type | Req | Description |
|---|---|---|---|
| considerations | array | – | People to consider and why (not a ranking). |
| kind | string | – | Type of work being led. |
No examples provided.
How do I install the EQIQs MCP server?
EQIQs is a hosted endpoint at https://adgmsnwjynqkhawhioil.supabase.co/functions/v1/mcp-server, 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 · adgmsnwjynqkhawhioil.supabase.co
claude mcp add --transport http eqiqs-rapport-axis-core 'https://adgmsnwjynqkhawhioil.supabase.co/functions/v1/mcp-server'
What is the EQIQs MCP server?
EQIQs is an MCP server listed in the public MCP registry as io.github.EQIQs/rapport-axis-core. EQIQs: 21-framework personality and compatibility for coaching, communication, and team development. This page covers its hosted endpoint (https://adgmsnwjynqkhawhioil.supabase.co/functions/v1/mcp-server).
Is the EQIQs MCP server safe to use?
EQIQs scores 91 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 EQIQs MCP server expose?
EQIQs exposes 16 tools: get_my_profile, list_profiles, get_profile, create_profile, list_relationships, and 11 more. Their descriptions and schemas cost roughly 2,522 tokens of context every time the server is loaded.
Does the EQIQs MCP server require authentication?
Yes. EQIQs asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the EQIQs MCP server still maintained?
EQIQs is still listed as active in the MCP registry. We last reached this channel on 5 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 EQIQs MCP server?
VerifyMCP ran 13 checks on EQIQs, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.