MCP servers › io.github.pandich93 › creatorloop

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.pandich93/creatorloop

Instagram content studio for Claude: analytics, competitors, Reels, publishing queue. — the publisher's description

8 of 8 record checks metRead-only · tools listed 2026-10-23version 0.3.0PythonMITstandard input/output34 tools

Summary

io.github.pandich93/creatorloop is a local MCP server listed in the official MCP registry at version 0.3.0. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 34 tools, 0 resources and 3 prompts.

Record checks

8 of 8 record checks met · 1 does not apply

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
met: Repository publishes a security policy (SECURITY.md)
met: Package names its licence with a standard (SPDX) identifier
met: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
met: No known critical or high advisory in the package or its dependencies

#14,745 of 15,112 packages by monthly downloads, tied with 367 others
Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: local package
Transport: standard input/output
Package: PyPI · listed version current
License: MIT
Dependencies: no known high or critical advisories
Repository: public
Tools: 34
Described as changing data: 11 of 34 toolsAI-classified
Mainly works on: accounts and data in outside web services; files and code on the machine it runs onAI-classified
Last tested: 2026-10-23

Add to your client

Worth knowing before you connect it

11 tools are described as changing something (track_competitor, untrack_competitor, prepare_post, …): our AI model's reading of the descriptions, not something we tested. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-23

Mode

read-only (no tool calls)

Latest version

0.3.0, published 2026-10-18 (registry, as of the 2026-10-23 snapshot)

First listed version

2026-10-12 (earliest version still in the registry; older removed versions would be earlier)

Version history

3 versions listed, 2026-10-12 to 2026-10-18; 3 in the 90 days before the 2026-10-23 snapshot.

Most recent 3 versions

0.3.0 · 2026-10-18
0.2.0 · 2026-10-13
0.1.0 · 2026-10-12

(versions still listed in the registry only)

Registry data

snapshot 2026-10-23

Package and repository

checked 2026-10-23

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.3.0 (published 2026-10-18).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

34tools

0resources

3prompts

What it mainly works on, as our AI model read its tool descriptions: accounts and data in outside web services; files and code on the machine it runs on.

11 of 34 tools are described as changing something (creating, editing, deleting, sending or running). For 1 the reading was uncertain, so no mark is shown.

get_my_profileon 17 other serversreads or searches
“Own profile: username, bio, followers, following, posts count.”
Publisher declares: read-only yes · open-world yes
1 input
- refreshboolean
get_my_mediareads or searches
“Latest own posts/Reels (newest first) with public counters: likes, comments, type, permalink, timestamp.”
Publisher declares: read-only yes · open-world yes
2 inputs
- limitinteger
- refreshboolean
get_media_insightson 1 other serverreads or searches
“Private insights for ONE own post/Reel/Story: reach, views, saved, shares, profile visits, follows, Reels average watch time (ms).”
Publisher declares: read-only yes · open-world yes
1 input, 1 required
- media_idstringrequired
get_my_content_reportreads or searches
“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, post…”
Publisher declares: read-only yes · open-world yes
3 inputs
- daysinteger“Analyse posts published in the last N days”
- rank_bystring
- max_postsinteger
get_caption_insightsreads or searches
“What in captions works: language (uz/ru/en), question in the hook, call-to-action, caption length; best and worst hooks (first line).”
Publisher declares: read-only yes · open-world yes
3 inputs
- usernamestring or null“Empty = own account (by reach); else a competitor”
- daysinteger
- max_postsinteger
get_account_insightson 1 other serverreads or searches
“Account-level totals for the period: reach, views, accounts engaged, interactions, likes, comments, saves, shares, link taps, follows/unfollows, plus daily reach.”
Publisher declares: read-only yes · open-world yes
1 input
- daysinteger“Period length in days, ending yesterday”
get_audience_demographicsreads or searches
“Audience demographics (top 45 rows).”
Publisher declares: read-only yes · open-world yes
3 inputs
- breakdownstring
- timeframestring
- engagedboolean“True = engaged audience, False = all followers”
get_competitoron 2 other serversreads or searches
“Public analysis of another PROFESSIONAL (business/creator) account via Business Discovery: profile, ER by followers, formats, posting frequency, best times, hashtags, top/worst posts.”
Publisher declares: read-only yes · open-world yes
3 inputs, 1 required
- usernamestringrequired“Instagram username, with or without @”
- media_limitinteger
- refreshboolean
compare_accountsreads or searches
“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, mai…”
Publisher declares: read-only yes · open-world yes
3 inputs, 1 required
- usernamesarrayrequired
- include_meboolean
- media_limitinteger
get_follower_historyreads or searches
“Follower growth from local daily snapshots (own account or any competitor fetched before).”
Publisher declares: read-only yes · open-world yes
2 inputs
- usernamestring or null“Username; empty = own account”
- daysinteger
track_competitoron 2 other serverscreates or changes datadescribed as changing data
“Add an account to the tracked list (validated with one Business Discovery request).”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
- usernamestringrequired“Professional account username, with or without @”
- notestring or null“Why you track it, e.g.”
untrack_competitordeletesdescribed as changing data
“Remove an account from the tracked list.”
Publisher declares: read-only no · destructive no · idempotent yes
1 input, 1 required
- usernamestringrequired

Show 22 more tools

list_tracked_competitorsreads or searches
“Tracked accounts with the date added and note.”
Publisher declares: read-only yes · open-world yes
Takes no inputs.
update_tracked_competitorsreads or searches
“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 med…”
Publisher declares: read-only yes · open-world yes
2 inputs
- media_limitinteger
- viral_multipliernumber
find_viral_postsreads or searches
“Posts that outperformed their account: Reels by views, other formats by likes+comments, compared with the account's own median.”
Publisher declares: read-only yes · open-world yes
4 inputs
- usernamestring or null“Empty = all tracked accounts”
- multipliernumber
- media_limitinteger
- daysinteger“Only posts from the last N days”
get_competitor_postreads or searches
“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 download…”
Publisher declares: read-only yes · open-world yes
3 inputs, 1 required
- urlstringrequired“Instagram post/reel URL, e.g.”
- usernamestring or null“Author's username (required in practice: oEmbed auto-detection needs Meta App Review)”
- show_slidesboolean“Return small previews of the slides as images”
get_post_historyon 1 other serverreads or searches
“Growth curve of one post (own or competitor) from stored snapshots: points by post age, gain per day and status growing/plateau.”
Publisher declares: read-only yes · open-world yes
1 input, 1 required
- media_idstringrequired
search_hashtagon 1 other serverreads or searches
“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.”
Publisher declares: read-only yes · open-world yes
3 inputs, 1 required
- hashtagstringrequired“Hashtag with or without #”
- modestring
- limitinteger
compare_hashtagsreads or searches
“Compare several hashtags by their top posts: avg likes/comments, dominant format, Reels share.”
Publisher declares: read-only yes · open-world yes
2 inputs, 1 required
- hashtagsarrayrequired
- limitinteger
plan_hashtag_researchreads or searches
“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.”
Publisher declares: read-only yes · open-world yes
1 input, 1 required
- hashtagsarrayrequired
prepare_poston 1 other serverdescribed as changing data
“Step 1 of publishing (does NOT publish).”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
2 inputs, 1 required
- folderstringrequired“Folder in the content folder (e.g.”
- captionstring or null“Empty = caption.txt from the folder (text before a '---' line)”
get_post_jobreads or searches
“Status of a prepare_post job: running (with current stage), done (with creation_id + preview) or failed.”
Publisher declares: read-only yes · open-world yes
1 input, 1 required
- job_idstringrequired
publish_mediaon 1 other serverdescribed as changing data
“Step 2: PUBLISHES the prepared post to Instagram (public, irreversible from here).”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
1 input, 1 required
- creation_idstringrequired“creation_id returned by prepare_post”
list_publicationson 9 other serversreads or searches
“Prepared and published posts made through this server, plus the 24h publishing quota.”
Publisher declares: read-only yes · open-world yes
1 input
- limitinteger
queue_poston 1 other servercreates or changes datadescribed as changing data
“Schedule a post/carousel/Reel to be PUBLISHED AUTOMATICALLY at a time (default slots Tue/Thu/Sun 19:00 local).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
3 inputs, 1 required
- folderstringrequired“Folder inside the content folder (same as prepare_post)”
- whenstring or null“'next' / empty = next free slot, or 'YYYY-MM-DD HH:MM' local”
- confirmboolean“false = preview only; true = add to the queue (after approval)”
list_queueon 5 other serversreads or searches
“Publishing queue: scheduled posts (and with include_done=true also published/failed/missed/blocked/cancelled), local times, plus the next free default slots.”
Publisher declares: read-only yes · open-world yes
1 input
- include_doneboolean
cancel_queueddeletesdescribed as changing data
“Remove a scheduled post from the queue (nothing is deleted on Instagram).”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
1 input, 1 required
- queue_idintegerrequired
post_reviewsreads or searchesdescribed as changing data
“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 growt…”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
1 input
- mark_reportedboolean“False = just look, do not mark posts as reported”
get_new_commentsreads or searches
“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).”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
2 inputs
- daysinteger“Posts published in the last N days”
- only_newboolean“false = all unanswered, including ones shown before”
reply_commenton 3 other serverssends messagesdescribed as changing data
“PUBLICLY replies to a comment under your post.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
2 inputs, 2 required
- comment_idstringrequired“reply_to from get_new_comments (the top-level comment of the thread)”
- messagestringrequired“Reply text exactly as the user approved it”
get_api_statuson 11 other serversreads or searches
“Diagnostics: token validity, days until expiry (warns 14 days ahead), last rate-limit usage headers, hashtag quota for the rolling 7 days, cache location.”
Publisher declares: read-only yes · open-world yes
Takes no inputs.
open_setupcontrols a browser or desktopdescribed as changing data
“Connect creatorloop to the user's Instagram account: opens a local setup page in their browser (Meta app, Facebook login, account choice).”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
2 inputs
- open_browserboolean“false: only return the link, e.g.”
- againboolean“true: connect again after a finished setup (expired or revoked token)”
clear_cacheon 5 other serversdeletesdescribed as changing data
“Drop cached API responses so next calls fetch fresh data.”
Publisher declares: read-only no · destructive no · idempotent yes
1 input
- prefixstring or null“me: | media: | bd: | hashtag: ; empty = everything.”
restart_serveron 3 other serversdescribed as changing data
“Restart this MCP server so updated .py code is loaded, without restarting Claude Desktop.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
2 inputs
- exit_codeinteger“1 = report as crash (Desktop restarts it)”
- forceboolean“Restart even if pyproject.toml/uv.lock changed (will likely fail)”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 34 tools
Says what it returns: 73% of 33 tools
States limits, defaults or errors: 0% of 22 tools
Says when to use it: 0% of 28 tools
Items covered per tool: 2.1 of 4 on average

Counted from the listing

Parameters with a description: 49% of 61
Tools with a description: 100% of 34
Typical description length: 226 characters

The tool set

Counted from the listing

Tools: 34
Size of the list: about 6,240 tokens for an agent to load (characters ÷ 4)
Naming: 34 of 34 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 34 of 34 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the PyPI package creatorloop

Our sandbox started this package on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)

{
  "mcpServers": {
    "creatorloop": {
      "command": "uvx",
      "args": [
        "creatorloop==0.3.0"
      ]
    }
  }
}

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "creatorloop": {
      "command": "uvx",
      "args": [
        "creatorloop==0.3.0"
      ]
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "creatorloop": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "creatorloop==0.3.0"
      ]
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"creatorloop","type":"stdio","command":"uvx","args":["creatorloop==0.3.0"]}'

Claude Code

claude mcp add --transport stdio creatorloop -- uvx creatorloop==0.3.0

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 -- uvx creatorloop==0.3.0

Optional settings the entry also lists (left out above): IG_ACCESS_TOKEN, IG_USER_ID.
This runs the publisher's code on your machine (uvx). Read its README first.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists: 0.3.0
Latest stable: 0.3.0
Status: current
Withdrawn: no

Source: pypi.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

Counted in the full dependency tree as resolved on 2026-10-23 (OSV.dev). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity: sha256-3473c84f68365e455…
License: MIT

Source: the package registry · 2026-10-23.

Usage

Downloads: 0 in the last month

Source: pypistats.org · 2026-10-23.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Published package can be started	Started and answered	matches	our test · 2026-10-23
Version 0.3.0 on PyPI	Exists and can be installed	matches	PyPI · 2026-10-23
Repository github.com/pandich93/creatorloop	Opens publicly	matches	api.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.pandich93
GitHub owner: a personal account (pandich93)

Repository: github.com/pandich93/creatorloop
Stars: 0
Repository age: 0–30 days
Last push: 0–30 days ago
Archived: no
Security policy: SECURITY.md

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

8 of 8 record checks met · 1 does not apply

#14,745 of 15,112 packages by monthly downloads, tied with 367 others
Not ranked by stars: 0 stars (ranked from 10)

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
MetPackage names its licence with a standard (SPDX) identifierMIT
MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.pandich93/creatorloop

Answered from the data above

Is io.github.pandich93/creatorloop safe to install?

We do not rate servers as safe or unsafe. 8 of its 8 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. 11 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.pandich93/creatorloop been security tested?

Partly. 4 of the 13 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can io.github.pandich93/creatorloop do?

It lists 34 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, delete, send messages and control a browser or desktop. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.pandich93/creatorloop change or delete data?

11 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.pandich93/creatorloop publish a security policy?

Yes: its repository has a public security policy (github.com/pandich93/creatorloop/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Is the listed version current?

Yes. The registry lists 0.3.0, the latest stable release on PyPI.

Where is the source code of io.github.pandich93/creatorloop?

In github.com/pandich93/creatorloop, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: exercised
Fake assistant turns: exercised
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not applicable
Consent handling: not applicable
Sign-in metadata: not applicable

4 exercised9 not run (reason given)5 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 13 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 4

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
12Hidden content
audience-hidingChecks resources that hide content from the user.exercised
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.exercised

Not run, with the reason · 9

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against

Does not apply to this server · 5

14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
17Consent handling
confused-deputyChecks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted the published package in an isolated sandbox (read-only mode)
2,533 msConnected after 0 redirects.
Read the inventory: 34 tools, 0 resources, 3 prompts.
3,059 msFinished: 4 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

no value

No value: the two AI models (Gemini and Claude) disagreed, so neither answer is shown.

Pricing modelAI-classified

not checked

no website in the registry entry

Programming language

Python

api.github.com · 2026-10-23

Hosting type

local package

registry · 2026-10-23

MCP capability

prompts, resources, tools

our test · 2026-10-23

Transport

standard input/output

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

pypi

registry · 2026-10-23

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

permissive

package registry · 2026-10-23

Integrity hash

declared (sha256)

package registry · 2026-10-23

Signature / provenance

does not apply

PyPI publishes no registry signature or attestation equivalent to npm dist.signatures

Dependency advisories

none known

OSV.dev · 2026-10-23

Popularity

0 downloads a month

package registry · 2026-10-23

Publisher signals

owner: a personal account · repository age: 0–30 days · stars: 0–9

api.github.com · 2026-10-23

Maintenance

active

api.github.com · 2026-10-23

Environment

your machine

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.pandich93/creatorloop: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.pandich93/creatorloop

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.pandich93/creatorloop)](https://protocolprobe.com/mcp/servers/io.github.pandich93/creatorloop)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology