io.github.patwalls/slope-mcp
NPM · SLOPE-MCP · SCANNED SEP 20
Proprietary B2B creator-velocity data: ranked board, live breakouts, and audience-growth curves.
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 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 73 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1304 tokens (~144/item across 9 items; 9 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 Management90
- Stability observed for 27 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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.patwalls/slope-mcp server?
io.github.patwalls/slope-mcp runs locally as an npm package, launched with npx -y slope-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 · slope-mcp
claude mcp add patwalls-slope-mcp -- npx -y slope-mcp
{
"mcpServers": {
"patwalls-slope-mcp": {
"command": "npx",
"args": [
"-y",
"slope-mcp"
]
}
}
} {
"servers": {
"patwalls-slope-mcp": {
"command": "npx",
"args": [
"-y",
"slope-mcp"
]
}
}
} codex mcp add patwalls-slope-mcp -- npx -y slope-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"patwalls-slope-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"slope-mcp"
],
"enabled": true
}
}
} openclaw mcp add patwalls-slope-mcp --command npx --arg -y --arg slope-mcp
mcp_servers:
patwalls-slope-mcp:
command: "npx"
args: ["-y", "slope-mcp"] {
"McpServers": {
"patwalls-slope-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"slope-mcp"
]
}
}
} assistant mcp add patwalls-slope-mcp -t stdio -c npx -a -y slope-mcp
{
"mcpServers": {
"patwalls-slope-mcp": {
"command": "npx",
"args": [
"-y",
"slope-mcp"
]
}
}
} 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.
- 18 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.
- 16 Sept 26 −3
- Stability: pass → 0.77 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −2
- Stability: pass → 0.83 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 4 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.
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 20 Sept 2026 · Analysed npm/slope-mcp@0.1.0
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 95 packages
| Packages resolved | 95 |
|---|---|
| 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 →
breakouts ~160
Get content breaking out right now — individual videos whose velocity (views/hour) far exceeds the creator's OWN typical velocity (relativeScore = current velocity ÷ baseline velocity). Each returns { rank, creator (name, slug, handle, subscribers), relativeScore, viewsPerHour, baselineVph, engagementRate, breakoutCount, confidence ("solid" once enough snapshots are banked), videoId }. This is Slope's core early-warning signal — a breakout is caught a median of ~2 hours after publish. Supports `limit` and `confidence=solid`.
| Name | Type | Req | Description |
|---|---|---|---|
| confidence | string | – | Optional — set to "solid" for only high-confidence breakouts (enough banked snapshots). |
| limit | integer | – | How many breakouts to return. |
No output schema declared.
No examples provided.
content ~157
Get one piece of content by `videoId` (get videoIds from `breakouts`, `creator`, or `cross_platform_rising`) plus its full first-party velocity curve. Returns { content (videoId, title, platform, url, channelHandle, publishedAt, latestViews, latestLikes), viewsPerHour (current velocity), velocityTrend ("climbing"/"cooling"), peakViewsPerHour, breakout (relativeScore, baselineVph, isBreakingOut, confidence), and the banked snapshot series }. This velocity curve is Slope-proprietary — it cannot be backfilled from any public source.
| Name | Type | Req | Description |
|---|---|---|---|
| videoId | string | yes | The content's videoId, e.g. "b-RRbBdMxIg". |
No output schema declared.
No examples provided.
creator ~147
Get one creator's full profile by `slug` (get slugs from `creator_board`, `search_creators`, or `breakouts`). Returns { person (name, niche, bio, photo), rank, accounts (per-platform handles + follower counts), crossPlatform, crossPlatformReach, audienceVelocity (followers/hour), velocity (current content velocity, views/hour), breakoutHistory, videos (recent content, each with videoId, viewsPerHour, relativeScore, and a banked view `curve`) }. This is the deepest single-creator view: the audience growth curve plus per-content velocity.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The creator's slug, e.g. "holy-schmidt". |
No output schema declared.
No examples provided.
creator_board ~202
Get Slope's ranked board of tracked B2B creators — the leaderboard. Each creator returns { rank, slug, name, handle, niche, subscribers (exact YouTube subscriber count), crossPlatformReach (followers summed across captured platforms), velocityViewsPerHour (the creator's current content velocity in views/hour), topRelativeScore (peak breakout intensity vs their own baseline), velocityRankInNiche, engagementRate, audienceRatePerHour (followers gained/hour) }. Use `slug` with the `creator` tool for the full profile. Sorted by subscribers; supports `limit`, `niche`, and `sort`.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many creators to return (default is the API default; the board holds ~3400). |
| niche | string | – | Optional — filter to one niche (e.g. "Entrepreneurship", "Finance"). |
| sort | string | – | Optional sort key (e.g. "subscribers", "velocity"). |
No output schema declared.
No examples provided.
cross_platform_rising ~193
Get creators whose rolled-up cross-platform audience is rising fastest — primary YouTube subscribers/hour plus captured followers/hour across other platforms (X, TikTok, Instagram, Facebook, LinkedIn). Each returns { rank, name, slug, avatar, niche, followers (total across platforms), subscribers (YouTube), ratePerHour (audience gained/hour), ratePercentPerDay, byPlatform (per-platform breakdown) }. The "who is growing their whole audience fastest" view. Supports `limit`, `niche`, `minSubs`, `maxSubs`, `sort`.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many creators to return. |
| maxSubs | integer | – | Optional maximum subscriber count. |
| minSubs | integer | – | Optional minimum subscriber count. |
| niche | string | – | Optional niche filter. |
| sort | string | – | Optional — "absolute" (rate/hour) or "relative" (%/day). |
No output schema declared.
No examples provided.
dataset_summary ~100
Get the whole dataset at a glance in one call — { breakingNow (content breaking out right now), topBreakout, hottestNiche, biggestAudienceMover, creatorsTrackedComplete, creatorsDiscovered, newCreatorsLast24h, velocityPointsBanked (total banked velocity snapshots), liveVelocityCurves, earlyCatch (median hours after publish a breakout is caught) }. The fastest way to orient before drilling in with the other tools. No inputs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rising_creators ~159
Get creators with rising momentum — those with consistent breakout frequency + intensity over the window (steady surgers, not one-offs), ranked. Each returns { rank, name, slug, handle, niche, vertical, subscribers, crossPlatformReach, audienceRatePerHour (followers/hour), breakoutEpisodes (count of breakout content in window), peakRelativeScore }. The "who is heating up" list. Supports `limit`, `niche`, `minSubs`, `maxSubs`.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many creators to return. |
| maxSubs | integer | – | Optional — maximum subscriber count (find smaller creators about to pop). |
| minSubs | integer | – | Optional — minimum subscriber count. |
| niche | string | – | Optional niche filter. |
No output schema declared.
No examples provided.
search_creators ~92
Search tracked creators by name or handle — exact → prefix → substring → typo-tolerant fuzzy. Returns { query, count, results } where each result includes the creator's name, slug, handle, niche, and whether they are breaking out right now. Use the returned `slug` with the `creator` tool for the full profile.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | yes | The name or handle to search for. |
No output schema declared.
No examples provided.
trending_niches ~94
Get trending niches ranked by BREADTH — how many DISTINCT creators are surging in each niche (not raw episode count), over a 7-day window. Each returns { rank, niche, creators (distinct creators breaking out), breakouts (total breakout episodes), topRelativeScore, momentum (rank change vs the prior window) }. Answers "which corner of the B2B creator market is heating up?". No inputs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.patwalls/slope-mcp server?
io.github.patwalls/slope-mcp is listed in the public MCP registry as io.github.patwalls/slope-mcp. Proprietary B2B creator-velocity data: ranked board, live breakouts, and audience-growth curves. This page covers its npm package (slope-mcp).
Is the io.github.patwalls/slope-mcp server safe to use?
io.github.patwalls/slope-mcp scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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.patwalls/slope-mcp server expose?
io.github.patwalls/slope-mcp exposes 9 tools: creator_board, creator, rising_creators, breakouts, content, and 4 more. Their descriptions and schemas cost roughly 1,304 tokens of context every time the server is loaded.
Is the io.github.patwalls/slope-mcp server still maintained?
io.github.patwalls/slope-mcp is still listed as active in the MCP registry. We last reached this channel on 20 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.patwalls/slope-mcp server under?
io.github.patwalls/slope-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.