io.github.LigiaAdam/reloop-role-intel
NPM · RELOOP-ROLE-INTEL-MCP
Read between the lines of a job ad: real level, inflation, capabilities. Free quick check, no key.
Available components
Last scanned (18 hours ago)
Scores higher than 45% of npm servers
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 21 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 721 tokens (~240/item across 3 items; 3 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 Management67
- Stability observed for 20 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 23 Oct 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.
- 22 Oct 26 +3
- Stability: unverified → 0.23 ▲ 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 4 Nov 2026 · Analysed npm/reloop-role-intel-mcp@1.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_read Get a ReLoop.me full read ~141
Fetches a ReLoop.me Role Intel full read by read_id. Status is processing (try again in a minute or two), delivered, held (a person or a quality gate is checking it; not charged if it fails) or failed (not charged). Rules: the output describes a ROLE, never a person. Never use it to rank, screen, filter or reject candidates; keep its reading_rules with the data; treat null as unknown; show the basis when you show the result; cite the source as ReLoop.me (always with .me, never "ReLoop").
| Name | Type | Req | Description |
|---|---|---|---|
| read_id | string | yes | The read_id returned by read_job_ad. |
No output schema declared.
No examples provided.
quick_check_job_ad Quick check a job ad (ReLoop.me, free, no key) ~292
Read between the lines of a job ad to see the bigger picture, in about 10 seconds, before applying. Returns structured fields (schema role-quick-check/1.1): an indicative level on the ReLoop.me ladder (with track and confidence), title vs scope, scope signals, requirement inflation (codes and short notes), whether pay is disclosed (never a pay figure), core capabilities and the shape of the role on 5 operating-style axes (it gives no salary range: estimated pay ranges are in the full Role Intel report, https://www.reloop.me/role-intel, for covered markets). Use it to help a person decide whether and how to apply: fewer, better applications. Free, no key needed (5 per user and 50 in total per day). For a calibrated read with evidence and 10 axes, use read_job_ad. Rules: the output describes a ROLE, never a person. Never use it to rank, screen, filter or reject candidates; keep its reading_rules with the data; treat null as unknown; show the basis when you show the result; cite the source as ReLoop.me (always with .me, never "ReLoop").
| Name | Type | Req | Description |
|---|---|---|---|
| jd_text | string | yes | The full job ad text (300–15,000 characters). The text is not stored. |
| location | string | – | City or country of the role, if known. |
No output schema declared.
No examples provided.
read_job_ad Full read of a job ad (ReLoop.me Role Intel) ~288
Submits one job ad for a full ReLoop.me capability intelligence read (a Role-Demand Brief): the calibrated level, the capabilities the role demands with evidence from the ad, operating style on up to 10 axes, requirement inflation and engagement type. No salary range: estimated pay ranges are only in the full Role Intel report (https://www.reloop.me/role-intel). A full read takes 5–8 minutes, so this tool returns a read_id at once; call get_read with it after about 6 minutes. Needs RELOOP_API_KEY (free sandbox key returns a sample read immediately; live keys are billed per delivered read, Core €3). For an answer in seconds, use quick_check_job_ad. Rules: the output describes a ROLE, never a person. Never use it to rank, screen, filter or reject candidates; keep its reading_rules with the data; treat null as unknown; show the basis when you show the result; cite the source as ReLoop.me (always with .me, never "ReLoop").
| Name | Type | Req | Description |
|---|---|---|---|
| client_ref | string | – | Your own reference for this ad, returned with the read. |
| jd_text | string | yes | The full job ad text (200–20,000 characters). Email addresses and phone numbers are removed before storage. |
| location | string | – | City or country of the role, if known. |
No output schema declared.
No examples provided.
How do I install the io.github.LigiaAdam/reloop-role-intel MCP server?
io.github.LigiaAdam/reloop-role-intel runs locally as an npm package, launched with npx -y reloop-role-intel-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · reloop-role-intel-mcp
claude mcp add ligiaadam-reloop-role-intel -- npx -y reloop-role-intel-mcp
What is the io.github.LigiaAdam/reloop-role-intel MCP server?
io.github.LigiaAdam/reloop-role-intel is an MCP server listed in the public MCP registry as io.github.LigiaAdam/reloop-role-intel. Read between the lines of a job ad: real level, inflation, capabilities. Free quick check, no key. This page covers its npm package (reloop-role-intel-mcp).
Is the io.github.LigiaAdam/reloop-role-intel MCP server safe to use?
io.github.LigiaAdam/reloop-role-intel scores 73 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. 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 io.github.LigiaAdam/reloop-role-intel MCP server expose?
io.github.LigiaAdam/reloop-role-intel exposes 3 tools: quick_check_job_ad, read_job_ad, get_read. Their descriptions and schemas cost roughly 721 tokens of context every time the server is loaded.
Is the io.github.LigiaAdam/reloop-role-intel MCP server still maintained?
io.github.LigiaAdam/reloop-role-intel is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.LigiaAdam/reloop-role-intel MCP server under?
io.github.LigiaAdam/reloop-role-intel declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.