creatorloop
PYPI · CREATORLOOP
Instagram content studio for Claude: analytics, competitors, Reels, publishing queue.
Available components
Last scanned (34 minutes ago)
Scores higher than 92% of PyPI servers
Category Marketing and SEO
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 34 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pandich93/creatorloop). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 17 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 3015 tokens (~88/item across 34 items; 34 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 49% of tool parameters carry a description.Partial
- Structured output schemas are declared (97% 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
- All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 35 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 2 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- 29 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.
- 27 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.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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 5 Nov 2026 · Analysed pypi/creatorloop@0.3.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pandich93/creatorloop |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pandich93/creatorloop/.github/workflows/release.yml@refs/tags/v0.3.0 |
| Rekor log index | 3315203302 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:09aae396c828df43c0949e3e1e5f79824719d461c41493dbd8aa18ae63b26ec1 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 34 packages
| Packages resolved | 34 |
|---|---|
| No linked repository | 1 |
| 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 →
cancel_queued ~31
Remove a scheduled post from the queue (nothing is deleted on Instagram).
| Name | Type | Req | Description |
|---|---|---|---|
| queue_id | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
clear_cache ~51
Drop cached API responses so next calls fetch fresh data. Follower history is not affected.
| Name | Type | Req | Description |
|---|---|---|---|
| prefix | – | – | me: | media: | bd: | hashtag: ; empty = everything. Snapshots are kept. |
Structured output declared, but exposes no named fields.
No examples provided.
compare_accounts ~75
Side-by-side comparison of up to 10 professional accounts (optionally including own account, measured the same public way): followers, posts/week, avg likes/comments/Reels views, ER by followers, main format.
| Name | Type | Req | Description |
|---|---|---|---|
| include_me | boolean | – | – |
| media_limit | integer | – | – |
| usernames | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
compare_hashtags ~60
Compare several hashtags by their top posts: avg likes/comments, dominant format, Reels share. Each NEW hashtag uses 1 of 30 weekly slots; check get_api_status first.
| Name | Type | Req | Description |
|---|---|---|---|
| hashtags | array | yes | – |
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
find_viral_posts ~85
Posts that outperformed their account: Reels by views, other formats by likes+comments, compared with the account's own median. Good source of proven topics and hooks.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Only posts from the last N days |
| media_limit | integer | – | – |
| multiplier | number | – | – |
| username | – | – | Empty = all tracked accounts |
Structured output declared, but exposes no named fields.
No examples provided.
get_account_insights ~71
Account-level totals for the period: reach, views, accounts engaged, interactions, likes, comments, saves, shares, link taps, follows/unfollows, plus daily reach. Meta data can lag up to 48h.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Period length in days, ending yesterday |
Structured output declared, but exposes no named fields.
No examples provided.
get_api_status ~44
Diagnostics: token validity, days until expiry (warns 14 days ahead), last rate-limit usage headers, hashtag quota for the rolling 7 days, cache location.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_audience_demographics ~64
Audience demographics (top 45 rows). Requires 100+ followers (or 100+ engagements for engaged=True).
| Name | Type | Req | Description |
|---|---|---|---|
| breakdown | string | – | – |
| engaged | boolean | – | True = engaged audience, False = all followers |
| timeframe | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_caption_insights ~86
What in captions works: language (uz/ru/en), question in the hook, call-to-action, caption length; best and worst hooks (first line). Own account is scored by reach, competitors by likes+comments.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| max_posts | integer | – | – |
| username | – | – | Empty = own account (by reach); else a competitor |
Structured output declared, but exposes no named fields.
No examples provided.
get_competitor ~93
Public analysis of another PROFESSIONAL (business/creator) account via Business Discovery: profile, ER by followers, formats, posting frequency, best times, hashtags, top/worst posts. Saves a daily follower snapshot so growth can be tracked with get_follower_history.
| Name | Type | Req | Description |
|---|---|---|---|
| media_limit | integer | – | – |
| refresh | boolean | – | – |
| username | string | yes | Instagram username, with or without @ |
Structured output declared, but exposes no named fields.
No examples provided.
get_competitor_post ~203
Analyse ONE post of a professional account by its URL, without a browser: caption, hook, likes, comments, Reels views, format, how many times better than the account's median, and all slides downloaded to <content folder>/_refs/<username>_<code>/ (videos: cover image). With show_slides the slide previews are returned as images (up to 20, 400 px wide) so their text and design can be read directly. Pass username: the author can't be detected from the URL without Meta App Review. Comment texts are not available via the API.
| Name | Type | Req | Description |
|---|---|---|---|
| show_slides | boolean | – | Return small previews of the slides as images |
| url | string | yes | Instagram post/reel URL, e.g. https://www.instagram.com/p/DeCHjDpjuI8/ |
| username | – | – | Author's username (required in practice: oEmbed auto-detection needs Meta App Review) |
No output schema declared.
No examples provided.
get_follower_history ~58
Follower growth from local daily snapshots (own account or any competitor fetched before). History starts from the first time the account was fetched through this server.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| username | – | – | Username; empty = own account |
Structured output declared, but exposes no named fields.
No examples provided.
get_media_insights ~61
Private insights for ONE own post/Reel/Story: reach, views, saved, shares, profile visits, follows, Reels average watch time (ms). Metrics the API refuses are listed in `unavailable`.
| Name | Type | Req | Description |
|---|---|---|---|
| media_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_my_content_report ~119
Full content report for own account: best/worst posts with hooks, format comparison (Reels vs carousel vs image), weighted engagement rate, follows/profile visits per 1k reach, Reels watch time, posting frequency, best weekday/hour, most used hashtags, posts still growing (<72h). Makes 1 insights request per post (cached), so large max_posts is slower.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Analyse posts published in the last N days |
| max_posts | integer | – | – |
| rank_by | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_my_media ~47
Latest own posts/Reels (newest first) with public counters: likes, comments, type, permalink, timestamp.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| refresh | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_my_profile ~37
Own profile: username, bio, followers, following, posts count. Also saves a daily follower snapshot.
| Name | Type | Req | Description |
|---|---|---|---|
| refresh | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_new_comments ~129
Comments under own posts that you have not answered yet, including follow-ups inside threads you already answered (new since the last call by default; they are marked as seen). For each: author, text, post, reply_to (the top-level comment to answer in that thread). Draft replies in the comment's language and show them to the user; send with reply_comment(reply_to) only after explicit approval. Needs instagram_manage_comments.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Posts published in the last N days |
| only_new | boolean | – | false = all unanswered, including ones shown before |
Structured output declared, but exposes no named fields.
No examples provided.
get_post_history ~61
Growth curve of one post (own or competitor) from stored snapshots: points by post age, gain per day and status growing/plateau. Snapshots are added on every fresh fetch (max 1 per hour).
| Name | Type | Req | Description |
|---|---|---|---|
| media_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_post_job ~41
Status of a prepare_post job: running (with current stage), done (with creation_id + preview) or failed.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_publications ~33
Prepared and published posts made through this server, plus the 24h publishing quota.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_queue ~49
Publishing queue: scheduled posts (and with include_done=true also published/failed/missed/blocked/cancelled), local times, plus the next free default slots.
| Name | Type | Req | Description |
|---|---|---|---|
| include_done | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_tracked_competitors ~22
Tracked accounts with the date added and note.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
open_setup ~143
Connect creatorloop to the user's Instagram account: opens a local setup page in their browser (Meta app, Facebook login, account choice). Use when settings are missing or the token expired. Never ask for an App Secret or a token in the chat. Call again to check progress: once it reports done, every tool works without restarting Claude Desktop. Does not work inside Docker: there the user runs `creatorloop-auth login` (README, Docker).
| Name | Type | Req | Description |
|---|---|---|---|
| again | boolean | – | true: connect again after a finished setup (expired or revoked token) |
| open_browser | boolean | – | false: only return the link, e.g. when the browser is elsewhere |
Structured output declared, but exposes no named fields.
No examples provided.
plan_hashtag_research ~66
Dry run before search_hashtag / compare_hashtags: which tags are free (queried within the last 7 days), which need a new slot out of 30 per week, and whether they all fit. Makes no API calls.
| Name | Type | Req | Description |
|---|---|---|---|
| hashtags | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
post_reviews ~108
Post-mortems for the daily report: own posts (last 7 days) that crossed 24 h or 72 h since the last run, with fresh insights vs the median of own mature posts of the same format (x_median), and growth 24 h -> 72 h. Each post is reported once per stage. Explain the numbers to the user and give one concrete takeaway.
| Name | Type | Req | Description |
|---|---|---|---|
| mark_reported | boolean | – | False = just look, do not mark posts as reported |
Structured output declared, but exposes no named fields.
No examples provided.
prepare_post ~263
Step 1 of publishing (does NOT publish). Starts a BACKGROUND job and returns job_id immediately. Folder with ONE .mp4/.mov -> Reel: validates the video (3 s-15 min, <=300 MB, moov at front), uploads it straight to Meta (resumable upload; tunnel only as fallback), cover frame and feed sharing from optional reel.json {"cover_ms": 1667, "share_to_feed": true}; images in that folder are ignored. Processing takes 1-10 min. Otherwise 1-10 images (sorted by file name) -> photo/carousel: converts to JPEG, serves them through a temporary Cloudflare tunnel, creates containers and waits until Meta has processed them (30-120 s). Caption: caption.txt (text before a '---' line). Poll get_post_job(job_id) every ~15-30 s. When done it returns creation_id and a preview: show it to the user and call publish_media only after their explicit confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| caption | – | – | Empty = caption.txt from the folder (text before a '---' line) |
| folder | string | yes | Folder in the content folder (e.g. 'my-first-reel') or an absolute path in it |
Structured output declared, but exposes no named fields.
No examples provided.
publish_media ~52
Step 2: PUBLISHES the prepared post to Instagram (public, irreversible from here). Call ONLY after the user explicitly confirmed this exact preview.
| Name | Type | Req | Description |
|---|---|---|---|
| creation_id | string | yes | creation_id returned by prepare_post |
Structured output declared, but exposes no named fields.
No examples provided.
queue_post ~177
Schedule a post/carousel/Reel to be PUBLISHED AUTOMATICALLY at a time (default slots Tue/Thu/Sun 19:00 local). Call first with confirm=false and show the preview (type, caption hook, local time) to the user. Call again with confirm=true ONLY after the user explicitly approved this post AND this time. The server fingerprints caption and media: if they change before the slot, the post is blocked. Late by more than 3 h (laptop asleep) = missed.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | false = preview only; true = add to the queue (after approval) |
| folder | string | yes | Folder inside the content folder (same as prepare_post) |
| when | – | – | 'next' / empty = next free slot, or 'YYYY-MM-DD HH:MM' local |
Structured output declared, but exposes no named fields.
No examples provided.
reply_comment ~66
PUBLICLY replies to a comment under your post. Call ONLY after the user explicitly approved this exact text.
| Name | Type | Req | Description |
|---|---|---|---|
| comment_id | string | yes | reply_to from get_new_comments (the top-level comment of the thread) |
| message | string | yes | Reply text exactly as the user approved it |
Structured output declared, but exposes no named fields.
No examples provided.
restart_server ~127
Restart this MCP server so updated .py code is loaded, without restarting Claude Desktop. The process exits ~1 s after replying; Claude Desktop starts it again on the next call. Use only after a code update (get_api_status shows restart_needed=true). Wait 10-20 s before the next call. Refuses when dependencies/version changed: then Claude Desktop must be restarted manually.
| Name | Type | Req | Description |
|---|---|---|---|
| exit_code | integer | – | 1 = report as crash (Desktop restarts it) |
| force | boolean | – | Restart even if pyproject.toml/uv.lock changed (will likely fail) |
Structured output declared, but exposes no named fields.
No examples provided.
search_hashtag ~97
Top (most popular) or recent (last 24h) public posts for a hashtag, with a trend summary: formats, avg likes/comments, related hashtags, caption length, posting times. Author usernames are NOT available from the API. Uses 1 of 30 weekly hashtag slots for a new tag.
| Name | Type | Req | Description |
|---|---|---|---|
| hashtag | string | yes | Hashtag with or without # |
| limit | integer | – | – |
| mode | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
track_competitor ~71
Add an account to the tracked list (validated with one Business Discovery request). Tracked accounts are refreshed together by update_tracked_competitors.
| Name | Type | Req | Description |
|---|---|---|---|
| note | – | – | Why you track it, e.g. 'AI-blog, uz' |
| username | string | yes | Professional account username, with or without @ |
Structured output declared, but exposes no named fields.
No examples provided.
untrack_competitor ~33
Remove an account from the tracked list. Its history stays in the database.
| Name | Type | Req | Description |
|---|---|---|---|
| username | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
update_tracked_competitors ~83
Refresh all tracked accounts (fresh API data, 1-2 requests each): follower change over the stored history, new posts since the previous update and viral posts (score >= multiplier × the account's median). Run it regularly (e.g. weekly) to build history.
| Name | Type | Req | Description |
|---|---|---|---|
| media_limit | integer | – | – |
| viral_multiplier | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the creatorloop MCP server?
creatorloop runs locally as a PyPI package, launched with uvx creatorloop. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · creatorloop
claude mcp add pandich93-creatorloop -- uvx creatorloop
What is the creatorloop MCP server?
creatorloop is an MCP server listed in the public MCP registry as io.github.pandich93/creatorloop. Instagram content studio for Claude: analytics, competitors, Reels, publishing queue. This page covers its PyPI package (creatorloop).
Is the creatorloop MCP server safe to use?
creatorloop scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 creatorloop MCP server expose?
creatorloop exposes 34 tools: get_my_profile, get_my_media, get_media_insights, get_my_content_report, get_caption_insights, and 29 more. Their descriptions and schemas cost roughly 2,806 tokens of context every time the server is loaded.
Is the creatorloop MCP server still maintained?
creatorloop 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 licence is the creatorloop MCP server under?
creatorloop declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.