@pofky/asc-mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 1 of 1 tool tried
Contacts while installing and starting: nothing
Its tool definitions changed since version 1.10.3. If you approved the earlier ones, read them again.
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y -p @pofky/asc-mcp@1.11.2 asc-mcp
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
1 tool that takes no input and looks read-only was called once with nothing. 1 returned a result.
asc_guide | Returned a result under 0.1 s · 1,018 characters |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
asc_setup_check
Diagnose your setup: checks the .p8 key, Key ID, Issuer ID, a LIVE authenticated connection to App Store Connect, and your license tier. For anything wrong, returns the exact fix. Run this first if something isn't working. Free.
asc_guide topic
START HERE. Returns the exact end-to-end playbook for an App Store task, with every manual ASC-website/Xcode step that no API can do flagged inline. Free.
asc_connect issuer_id, key_path
Connect the user's App Store Connect account from this chat, so no config file or terminal is needed. Ask the user for their Issuer ID (the UUID above the keys list at https://appstoreconnect.apple.com/access/integrations/api); never invent one. It finds their downloaded AuthKey_XXXXXXXXXX.p8 (in ~/.appstoreconnect/private_keys, ~/Downloads or ~/Desktop) and moves it into ~/.appstoreconnect/private_keys, tests the pair against Apple, saves the Issuer ID in ~/.asc-mcp/credentials.json, and unlocks every tool in this session. Free.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=18.0.0 |
| Source | github.com/pofky/asc-mcp |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-di94kjU8zCmNri73qK3XYZUBCwf2iQpMYWJBfkQmeEYMn6ExPvSP6UAOSrbqO9/aLy3NPFyU6IqvVgdaFdY2JA== |
Versions reported
| Version | Run | Result | Tools |
|---|---|---|---|
| 1.11.2 | 2026-11-16 | Starts with no setup | 3 |
| 1.10.3 | 2026-11-12 | Starts with no setup | 2 |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40pofky/asc-mcp)
New version out? Ask for a fresh report.