Results / @percher/mcp
@percher/mcp
Sealmark's automated test of @percher/mcp 1.5.0 on 2026-11-22 gave it grade D, its lowest test-area grade (protocol D). None of the 61 tools could be called with default settings, so this grade covers the handshake and tool metadata only. Of its 10 checks, 3 passed, 1 failed, 2 inconclusive and 4 not applicable. 3 more checks are advisory, and advisory checks never change a grade: 1 passed, 1 failed and 1 not applicable. The run used Sealmark 1.0.1 with the standard settings. The grade includes a finding under private disclosure; it still counts in full.
Grade D
The server's grade is its lowest test-area grade. How grading works
The grade includes a finding under private disclosure. It still counts in full.
None of the 61 tools could be called with default settings, so this grade covers the handshake and tool metadata only.
Grade by test area
Protocol checks
| Check | Verdict | What happened |
|---|---|---|
| protocol Valid MCP handshake and tool schemas | pass | handshake ok, 61 well-formed tool(s) |
| tool-poisoningcritical No tool-poisoning indicators in tool metadata | fail | A security finding is being reported to the maintainer privately. Details will be published when it is fixed or 90 days after the report (disclosure policy). |
| robust-input Survives malformed tool input | pass | 102 invalid call(s) rejected cleanly |
| secret-echocritical No environment secret echoed in responses | pass | Details held back while a security finding in this test area is reported privately. |
| instructions-hygiene (advisory) Server instructions name only tools that exist | fail | the server instructions names 9 tool(s) the server does not offer (run_doctor, ask_user, open_login, set_env_vars, auth_pending) |
| refusal-quality (advisory) Refusals say what to do next | n/a | no refusal was recorded in this run, so there is nothing to judge |
Network checks
| Check | Verdict | What happened |
|---|---|---|
| net-loopback-ssrfcritical Refuses loopback targets (SSRF) | inconclusive | the listener saw nothing, but 18 of 18 probes were not explicitly refused (9 failed without saying the target was refused), so a refusal cannot be told from a tool that cannot fetch at all (a reply that only reports a failed fetch (proxy, socket, DNS) is not read as a refusal; set net.control_url to a URL the tool can reach) |
| net-scheme-allowlistcritical Only http(s) schemes accepted | inconclusive | no scheme had an observable effect, but 12 of 12 scored probes were not explicitly refused, so a refusal cannot be told from a tool that cannot fetch at all (a reply that only reports a failed fetch (proxy, socket, DNS) is not read as a refusal; set net.control_url to a URL the tool can reach) |
| net-caps Response size and time are capped | n/a | net-loopback-ssrf was inconclusive: the server never reached the loopback listener, so no loopback URL is known to be fetchable; response size and time caps were not measured |
| net-redirect Redirects are re-validated | n/a | the server refused or never reached the loopback listener, so redirect handling could not be observed (a server that blocks loopback cannot be sent a redirect it would follow) |
Effects checks
| Check | Verdict | What happened |
|---|---|---|
| annotation-honestycritical Read-only tools change nothing | n/a | no tool declares readOnlyHint: true |
| openworld-honesty Closed-world tools stay on the machine | n/a | no tool declares openWorldHint: false that could be given a harness-owned control argument |
| undeclared-writes (advisory) Unannotated tools leave the sandbox unchanged | pass | percher_supabase carry no annotations and changed nothing |
Each check id links to what it tests and how to fix a failure. The same text is in sealmark explain <id>.
What was not covered
- Database: Not applicable. The start command takes no database connection, so the database tests did not run. ({dsn}, {host} and the like are placeholders that Sealmark fills in with its own test database.)
- HTTP: Not applicable. The server is started over stdio; the http test area needs server.url
- Files: Not applicable. The server config has no {sandbox} placeholder, so the harness cannot tell which directory the server is allowed to use (a server with a wider root would read the canary legitimately); pass {sandbox} as its directory argument, or, if the server has no root argument and works in its working directory, set server.rootless: true
- Git: Not applicable. No tool is classified as taking a git repository path with medium confidence or higher
- Network: Inconclusive. The listener saw nothing, but 18 of 18 probes were not explicitly refused (9 failed without saying the target was refused), so a refusal cannot be told from a tool that cannot fetch at all (a reply that only reports a failed fetch (proxy, socket, DNS) is not read as a refusal; set net.control_url to a URL the tool can reach)
- SQLite: Not applicable. No tool takes a SQL string
- Effects: Not applicable. No tool declares readOnlyHint: true
- Malformed-input probes cover the first 25 of 61 tools
- Tool "percher_restore" (path) was not probed by the fs test area: the server config has no {sandbox} placeholder, so the harness cannot tell which directory the server is allowed to use (a server with a wider root would read the canary legitimately); pass {sandbox} as its directory argument, or, if the server has no root argument and works in its working directory, set server.rootless: true
- Tool "percher_create_from_template" (path) was not probed by the fs test area: the server config has no {sandbox} placeholder, so the harness cannot tell which directory the server is allowed to use (a server with a wider root would read the canary legitimately); pass {sandbox} as its directory argument, or, if the server has no root argument and works in its working directory, set server.rootless: true
- Tool "percher_webhook" (url) was not probed by the net test area: the listener saw nothing, but 18 of 18 probes were not explicitly refused (9 failed without saying the target was refused), so a refusal cannot be told from a tool that cannot fetch at all (a reply that only reports a failed fetch (proxy, socket, DNS) is not read as a refusal; set net.control_url to a URL the tool can reach)
- Tool "percher_appstore_kit" was not covered by the effects test area: no annotations and not a read-style tool, so it is expected to change state
- Tools that a server lists only for clients that declare roots, sampling or elicitation capabilities are not seen: the harness declares none
- Tool "percher_publish_patch" is covered by the protocol checks only: would be path (param "files[].path", description matches /files/), but required parameter "files" cannot be filled by the harness; write a probes: entry to call it
- Tool "percher_publish" is covered by the protocol checks only: free-text parameter "message": no path, URL, command, SQL or repository signal; add it under tools: to include it
- Tool "percher_wait_for_deploy" is covered by the protocol checks only: free-text parameter "app": no path, URL, command, SQL or repository signal; add it under tools: to include it
- Tool "percher_redeploy" is covered by the protocol checks only: free-text parameter "app": no path, URL, command, SQL or repository signal; add it under tools: to include it
- Tool "percher_reproduce" is covered by the protocol checks only: free-text parameter "app": no path, URL, command, SQL or repository signal; add it under tools: to include it
- Tool "percher_login" is covered by the protocol checks only: the tool has no string parameters; add it under tools: to include it
- Tool "percher_wait_for_auth" is covered by the protocol checks only: free-text parameter "deviceCode": no path, URL, command, SQL or repository signal; add it under tools: to include it
- Tool "percher_init" is covered by the protocol checks only: argument "name" could be a path, but nothing in the tool name, its title or the parameter's own description says so; add it under tools: to include it
- Tool "percher_logs" is covered by the protocol checks only: free-text parameter "app": no path, URL, command, SQL or repository signal; add it under tools: to include it
- Tool "percher_unsuspend" is covered by the protocol checks only: free-text parameter "app": no path, URL, command, SQL or repository signal; add it under tools: to include it
- Tool "percher_sleep" is covered by the protocol checks only: free-text parameter "app": no path, URL, command, SQL or repository signal; add it under tools: to include it
- Tool "percher_cache_reset" is covered by the protocol checks only: free-text parameter "app": no path, URL, command, SQL or repository signal; add it under tools: to include it
- 44 more tool(s) are covered by the protocol checks only (see the classification)
- Tool "percher_inspect_link" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_rollback" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_backups" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_restore" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_deploys" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_deploys_inspect" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_doctor" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_reset_superuser" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_data" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_app_topology" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_app_resources" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_app_insights" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_billing" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_create_from_template" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_domain" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_share" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_invites" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_transfer" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_transfers" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_import" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_account_deletion_preview" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_account_delete" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_data_export" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_webhook" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_hook" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_github" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_forgejo" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_set_preview_branch" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_supabase" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_delete_app" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_data_schema" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_data_query" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_data_get" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_data_create" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_data_update" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_data_delete" was not covered by the core test area: beyond the first 25 tools, which are the only ones robust-input probes
- Tool "percher_whoami" was not covered by the core test area: needs probes: to be called (no arguments, and not declared read-only)
- Tool "percher_capabilities" was not covered by the core test area: needs probes: to be called (no arguments, and not declared read-only)
- SSRF: link-local and private-range addresses are never contacted; redirects from a public host to loopback and DNS rebinding are not tested (the harness contacts only its own loopback listener)
- The sandbox is a convention the harness follows, not a security boundary. A malicious server runs with your user's privileges, sees the real file system and network, and can ignore cwd, HOME and PATH. Run untrusted servers in a throwaway VM or container.
- Prompt injection carried in tool output (only tool metadata is scanned)
- Authentication and transport security
- Audit logging (not measured by these test areas; only the db test area has an advisory audit check)
- The net test area's calls do not count toward coverage: every check of the test area was inconclusive or n/a, or the server rejected every call before running it
- The effects test area's calls do not count toward coverage: every check of the test area was inconclusive or n/a, or the server rejected every call before running it
Grade over time
Since the run on
- Network was not graded in this run (it was F before).
- Server version changed from 1.4.0 to 1.5.0.
Unchanged: the same Sealmark version (1.0.1).
- Fv1.4.0Sealmark 1.0.0
- Fv1.4.0Sealmark 1.0.1
- Fv1.4.0Sealmark 1.0.1
- Dv1.5.0Sealmark 1.0.1
Package facts
- License
- FSL-1.1-MIT
From npm, checked 22 Nov 2026. Plain facts about the package; they play no part in the grade.
Run it yourself
The command for this run is withheld while a security finding is reported privately. It is published with the report, when the finding is fixed or 90 days after the report.
Grade alerts
One email when the grade of @percher/mcp changes after a re-test. Nothing else, and every email has a link to stop them.
Each of 613 verdicts was checked independently, and Sealmark was wrong on some: how reliable Sealmark is.
Is this wrong?
Reply to our private report or email disclosure@sealmark.dev and we will recheck it. Maintainers can ask for their server to be removed.
If we were wrong, we correct the page and add your reply. Security findings go to the maintainer privately first; see the disclosure policy.