mcp-sharepoint-cert@0.3.0
VERIFIED· not startedPublisher claims: "MCP Server to integrate with SharePoint" 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
SHP_ID_APP_SECRETConfiguration, not credentials: SHP_BATCH_DELAY, SHP_CERT_PATH, SHP_CERT_THUMBPRINT, SHP_DOC_LIBRARY, SHP_ID_APP, SHP_LEVEL_DELAY, SHP_MAX_DEPTH, SHP_MAX_FOLDERS_PER_LEVEL, SHP_SITE_URL, SHP_TENANT_ID- Where it talks to
- no vendor host named in the codeAlso azure.com, sharepoint.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 azure.com, sharepoint.com as well as its own vendor. The guard injects SHP_ID_APP_SECRET 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-09 and scored it 82/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
# Load .env file for local testingFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.rprint(" Ubuntu: [cyan]sudo apt install openssl[/cyan]")Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.subprocess.run(["xsel", "--clipboard", "--input"], input=text.encode(), check=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.env_file=".env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.subprocess.run(["xclip", "-selection", "clipboard"], input=text.encode(), check=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.run(["pbcopy"], input=text.encode(), check=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.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 mcp-sharepoint-cert@0.3.0 as of 5d ago. This is the package itself, not its dependencies.