suppa-mcp@1.0.26
VERIFIED· not startedPublisher claims: "MCP server for the Suppa platform (modern.suppa.me) — Tasks, Docs/Pages, Entities & Schema, Forms, and file attachments, with multi-tenant Google auth" 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
SUPPA_API_KEYSUPPA_REFRESH_TOKENSUPPA_TOKENSUPPA_V1_ACCESS_TOKENSUPPA_V1_API_KEYSUPPA_V1_TOKENConfiguration, not credentials: SUPPA_BASE_URL, SUPPA_GOOGLE_CLIENT_ID, SUPPA_HTTP_TIMEOUT, SUPPA_LANG, SUPPA_MCP_DEBUG, SUPPA_MCP_HOME, SUPPA_MCP_LOGIN_PORT, SUPPA_TASKS_ENTITY_ID, SUPPA_TEST_PROBE, SUPPA_TZ, SUPPA_V1_BASE_URL- Where it talks to
- suppa.me (its own)Also modern.me, bar.me, other.com, host.io, google.com, modern-expo.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 modern.me, bar.me, other.com, host.io, google.com, modern-expo.com as well as its own vendor. The guard injects SUPPA_API_KEY, SUPPA_REFRESH_TOKEN, SUPPA_TOKEN, SUPPA_V1_ACCESS_TOKEN, SUPPA_V1_API_KEY, SUPPA_V1_TOKEN only into requests to suppa.me (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-19 and scored it 84/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
"""Write both access and refresh tokens to .env, preserving other content."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""Configuration loaded from environment variables or .env file."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.candidates.append(Path(__file__).resolve().parent.parent.parent / ".env")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.return # No .env file found; skip silentlyFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Tenant URL normalisation + .env key filteringFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""If SUPPA_API_KEY and SUPPA_REFRESH_TOKEN are in .env, seed the keychain.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.candidates.append(folder / ".env")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose._write_tokens_to_env(new.access_token, new.refresh_token) # Persist both tokens to .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""Find the .env file, searching up from cwd and then the project root."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Persist tokens to .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Project root relative to this file (…/suppa2.0-mcp-server/.env)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.print("ERROR: no credentials for this tenant. Set SUPPA_API_KEY in .env / the client env block.")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.happens before token expiry. Both tokens persist to .env after each refresh.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.proc = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out."""Return candidate .env locations, in priority order.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.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
Not checked against OSV yet; the weekly check has not reached this version.