io.github.pijusz/mcp-redtrack
NPM · MCP-REDTRACK · SCANNED SEP 25
MCP server for RedTrack affiliate tracking API
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 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 161 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 943 tokens (~72/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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 io.github.pijusz/mcp-redtrack server?
io.github.pijusz/mcp-redtrack runs locally as an npm package, launched with npx -y mcp-redtrack. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-redtrack
claude mcp add pijusz-mcp-redtrack -- npx -y mcp-redtrack
{
"mcpServers": {
"pijusz-mcp-redtrack": {
"command": "npx",
"args": [
"-y",
"mcp-redtrack"
]
}
}
} {
"servers": {
"pijusz-mcp-redtrack": {
"command": "npx",
"args": [
"-y",
"mcp-redtrack"
]
}
}
} codex mcp add pijusz-mcp-redtrack -- npx -y mcp-redtrack
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pijusz-mcp-redtrack": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-redtrack"
],
"enabled": true
}
}
} openclaw mcp add pijusz-mcp-redtrack --command npx --arg -y --arg mcp-redtrack
mcp_servers:
pijusz-mcp-redtrack:
command: "npx"
args: ["-y", "mcp-redtrack"] {
"McpServers": {
"pijusz-mcp-redtrack": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-redtrack"
]
}
}
} assistant mcp add pijusz-mcp-redtrack -t stdio -c npx -a -y mcp-redtrack
{
"mcpServers": {
"pijusz-mcp-redtrack": {
"command": "npx",
"args": [
"-y",
"mcp-redtrack"
]
}
}
} 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
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 −3
- Stability: pass → 0.77 functional
- 21 Sept 26 0
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −2
- Stability: pass → 0.83 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
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 · Analysed npm/mcp-redtrack@0.1.4
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 →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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_campaign ~36
Get a single RedTrack campaign by ID with full configuration details including streams, postbacks, and integrations.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_campaigns ~122
List RedTrack campaigns with optional filtering by title, status, source, tags, and date range. Returns campaign config and optionally embedded stats when total_stat is true.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | – |
| date_to | string | – | – |
| ids | string | – | – |
| page | number | – | – |
| per | number | – | – |
| sources | string | – | – |
| status | string | – | – |
| tags | string | – | – |
| timezone | string | – | – |
| title | string | – | – |
| total_stat | boolean | – | – |
No output schema declared.
No examples provided.
get_campaigns_v2 ~104
List RedTrack campaigns using the v2 endpoint. Similar to get_campaigns but with updated response format.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | – |
| date_to | string | – | – |
| ids | string | – | – |
| page | number | – | – |
| per | number | – | – |
| sources | string | – | – |
| status | string | – | – |
| tags | string | – | – |
| timezone | string | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
get_clicks ~131
Get RedTrack click log entries. Returns click-level data including IP, country, device, campaign, offer, landing, and sub-parameter details. Max 10000 per page.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | – | – |
| clickid | string | – | – |
| country_code | string | – | – |
| date_from | string | – | – |
| date_to | string | – | – |
| fingerprint | string | – | – |
| network_id | string | – | – |
| offer_id | string | – | – |
| page | number | – | – |
| per | number | – | – |
| source_id | string | – | – |
No output schema declared.
No examples provided.
get_conversions ~150
Get RedTrack conversion log entries. Returns conversion-level data including click ID, payout, cost, revenue, country, device, attribution type, and all sub-parameters. Max 10000 per page.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | – | – |
| clickid | string | – | – |
| country_code | string | – | – |
| date_from | string | – | – |
| date_to | string | – | – |
| fingerprint | string | – | – |
| network_id | string | – | – |
| offer_id | string | – | – |
| page | number | – | – |
| per | number | – | – |
| source_id | string | – | – |
| type | string | – | – |
| type_role | string | – | – |
No output schema declared.
No examples provided.
get_landings ~20
List all RedTrack landing pages and prelandings.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_networks ~19
List all RedTrack affiliate networks (offer sources).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_offer ~27
Get a single RedTrack offer by ID with full details.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_offers ~67
List RedTrack offers with optional filtering by title, network, or status.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | string | – | – |
| network_id | string | – | – |
| page | number | – | – |
| per | number | – | – |
| status | string | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
get_report ~201
Get RedTrack aggregated report grouped by a dimension (e.g. campaign, offer, source, country, sub1-sub20, date, hour). Includes metrics like impressions, clicks, conversions, cost, revenue, profit, ROI, CR, EPC, CPC.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | – | – |
| date_from | string | – | – |
| date_to | string | – | – |
| group | string | yes | – |
| landing_id | string | – | – |
| network_id | string | – | – |
| offer_id | string | – | – |
| page | number | – | – |
| per | number | – | – |
| source_id | string | – | – |
| sub1 | string | – | – |
| sub2 | string | – | – |
| sub3 | string | – | – |
| sub4 | string | – | – |
| sub5 | string | – | – |
| time_interval | string | – | – |
| timezone | string | – | – |
| tracks_view | string | – | – |
No output schema declared.
No examples provided.
get_settings ~22
Get RedTrack account settings including timezone, currency, and conversion types.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_source ~25
Get a single RedTrack traffic source by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_sources ~19
List all RedTrack traffic sources configured in the account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.pijusz/mcp-redtrack server?
io.github.pijusz/mcp-redtrack is listed in the public MCP registry as io.github.pijusz/mcp-redtrack. MCP server for RedTrack affiliate tracking API. This page covers its npm package (mcp-redtrack).
Is the io.github.pijusz/mcp-redtrack server safe to use?
io.github.pijusz/mcp-redtrack scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 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.pijusz/mcp-redtrack server expose?
io.github.pijusz/mcp-redtrack exposes 13 tools: get_campaigns, get_campaign, get_campaigns_v2, get_clicks, get_conversions, and 8 more. Their descriptions and schemas cost roughly 943 tokens of context every time the server is loaded.
Is the io.github.pijusz/mcp-redtrack server still maintained?
io.github.pijusz/mcp-redtrack 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.
What licence is the io.github.pijusz/mcp-redtrack server under?
io.github.pijusz/mcp-redtrack declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.