pointguard-mcp@0.5.0
VERIFIED· not startedPublisher claims: "MCP server for Creative Market's Pointguard search platform — discover fonts, graphics, and creative assets through natural conversation." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
MCP_API_KEYOPENAI_APPS_CHALLENGE_TOKENConfiguration, not credentials: CM_PRODUCT_DETAILS_URL, MATCHERATOR_BASE_URL, MATCHERATOR_SITE, MATCHERATOR_TIMEOUT, MCP_EXCLUDE_AI_GENERATED, MCP_HOST, MCP_HTTP, MCP_PORT, MCP_PUBLIC_URL, MCP_UTM_CAMPAIGN, MCP_UTM_MEDIUM, MCP_UTM_SOURCE, POINTGUARD_BASE_URL, POINTGUARD_TIMEOUT- Where it talks to
- no vendor host named in the codeAlso creativemarket.com, cm-ops.com, matcherator.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names creativemarket.com, cm-ops.com, matcherator.com as well as its own vendor. The guard injects MCP_API_KEY, OPENAI_APPS_CHALLENGE_TOKEN only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-14 and scored it 90/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
curl --fail --silent "$REGISTRY_URL/v0.1/servers/$ENCODED/versions/$VERSION" | python -m json.tool | head -40Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.&& rm -rf /root/.cache/pipFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for pointguard-mcp@0.5.0 as of 1 h ago. This is the package itself, not its dependencies.