Sealmark
Automated re-test on 2026-11-20: not checked by hand, and not yet reviewed by the maintainers.

Results / rillsoft/rillsoft-project-mcp

rillsoft/rillsoft-project-mcp

version tested 10.0.626GitHubtested 2026-11-20Sealmark 1.0.1methodology 0.3-draftSTANDARD run118 tools

Sealmark's automated test of rillsoft/rillsoft-project-mcp 10.0.626 on 2026-11-20 gave it grade A, its lowest test-area grade (protocol A). None of the 118 tools could be called with default settings, so this grade covers the handshake and tool metadata only. Of its 6 checks, 4 passed and 2 inconclusive. 3 more checks are advisory, and advisory checks never change a grade: 1 passed and 2 not applicable. The run used Sealmark 1.0.1 with the standard settings.

A

Grade A

The server's grade is its lowest test-area grade. How grading works

None of the 118 tools could be called with default settings, so this grade covers the handshake and tool metadata only.

Grade by test area

A
Protocol4/4 points

Protocol checks

CheckVerdictWhat happened
protocol
Valid MCP handshake and tool schemas
pass
handshake ok, 118 well-formed tool(s)
Evidence for protocol: 1 line
  1. Probe initialize + tools/list
    Outcome server rillsoft-project 10.0.626.0 answered; 118 tool(s)
    Decided from the MCP exchange (protocol)
tool-poisoningcritical
No tool-poisoning indicators in tool metadata
pass
scanned 118 tool definition(s), the server instructions and serverInfo, including parameter text: nothing suspicious
robust-input
Survives malformed tool input
pass
95 invalid call(s) rejected cleanly
Evidence for robust-input: 1 line
  1. Probe 95 invalid call(s) across 22 tool(s)
    Outcome all rejected cleanly and the server stayed responsive
    Decided from the MCP exchange (protocol)
secret-echocritical
No environment secret echoed in responses
pass
canary secrets absent from tools/list and 98 captured response(s), 0 of them successful result(s)
instructions-hygiene (advisory)
Server instructions name only tools that exist
pass
the instructions name no tool the server lacks
refusal-quality (advisory)
Refusals say what to do next
n/a
no refusal was recorded in this run, so there is nothing to judge

Effects checks

CheckVerdictWhat happened
annotation-honestycritical
Read-only tools change nothing
inconclusive
every control call failed, so the read-only annotation could not be checked
openworld-honesty
Closed-world tools stay on the machine
inconclusive
every control call failed, so the closed-world annotation could not be checked
undeclared-writes (advisory)
Unannotated tools leave the sandbox unchanged
n/a
every tool carries annotations, nothing to check

Each check id links to what it tests and how to fix a failure. The same text is in sealmark explain <id>.

Under a check, Evidence shows what it probed (sent or inspected) and what it observed in this run: up to 6 lines per check, each cut at 240 characters, for checks that are not security checks. The text is shortened, and paths and anything that looks like a secret or token are replaced. Run sealmark run --format json yourself for every line in full.

By tool

Which checks called each tool with a valid call in this run, and which did not exercise it. A check can leave a tool out for several reasons: a limit Sealmark sets, a tool left out by design, input the run could not fill in, or a call that returned an error. The CLI report gives the reason. A verdict belongs to the whole check, not to one tool: a failed check that called three tools does not say which one failed. Security checks are left out of this table.

ToolCalled byNot exercised by
rillsoft_analysis_option_listNo check listed here called it with a valid call.None
rillsoft_analysis_report_getNo check listed here called it with a valid call.
rillsoft_baseline_createNo check listed here called it with a valid call.None
rillsoft_baseline_deleteNo check listed here called it with a valid call.None
rillsoft_baseline_listNo check listed here called it with a valid call.
rillsoft_baseline_selectNo check listed here called it with a valid call.None
rillsoft_calendar_createNo check listed here called it with a valid call.None
rillsoft_calendar_deleteNo check listed here called it with a valid call.None
rillsoft_calendar_listNo check listed here called it with a valid call.None
rillsoft_calendar_source_getNo check listed here called it with a valid call.None
rillsoft_calendar_source_importNo check listed here called it with a valid call.None
rillsoft_calendar_updateNo check listed here called it with a valid call.None
rillsoft_document_ris_createNo check listed here called it with a valid call.None
rillsoft_document_ris_deleteNo check listed here called it with a valid call.None
rillsoft_document_ris_getNo check listed here called it with a valid call.None
rillsoft_document_ris_listNo check listed here called it with a valid call.None
rillsoft_document_ris_updateNo check listed here called it with a valid call.None
rillsoft_element_deleteNo check listed here called it with a valid call.None
rillsoft_element_moveNo check listed here called it with a valid call.None
rillsoft_element_reorderNo check listed here called it with a valid call.None
rillsoft_element_subproject_groupNo check listed here called it with a valid call.None
rillsoft_fixed_element_listNo check listed here called it with a valid call.
rillsoft_folder_ris_createNo check listed here called it with a valid call.None
rillsoft_folder_ris_deleteNo check listed here called it with a valid call.None
rillsoft_folder_ris_listNo check listed here called it with a valid call.None
rillsoft_folder_ris_moveNo check listed here called it with a valid call.
rillsoft_folder_ris_updateNo check listed here called it with a valid call.
rillsoft_history_redoNo check listed here called it with a valid call.
rillsoft_history_undoNo check listed here called it with a valid call.
rillsoft_machine_sharing_createNo check listed here called it with a valid call.
rillsoft_machine_sharing_releaseNo check listed here called it with a valid call.
rillsoft_outline_applyNo check listed here called it with a valid call.
rillsoft_outline_getNo check listed here called it with a valid call.
rillsoft_outline_row_applyNo check listed here called it with a valid call.
rillsoft_portfolio_file_openNo check listed here called it with a valid call.
rillsoft_portfolio_project_files_saveNo check listed here called it with a valid call.
rillsoft_portfolio_ris_createNo check listed here called it with a valid call.
rillsoft_portfolio_ris_deleteNo check listed here called it with a valid call.
rillsoft_portfolio_ris_listNo check listed here called it with a valid call.
rillsoft_portfolio_ris_openNo check listed here called it with a valid call.
rillsoft_portfolio_ris_saveNo check listed here called it with a valid call.
rillsoft_portfolio_ris_updateNo check listed here called it with a valid call.
rillsoft_project_conflict_listNo check listed here called it with a valid call.
rillsoft_project_createNo check listed here called it with a valid call.
rillsoft_project_file_export_xmlNo check listed here called it with a valid call.
rillsoft_project_file_openNo check listed here called it with a valid call.
rillsoft_project_file_saveNo check listed here called it with a valid call.
rillsoft_project_file_save_asNo check listed here called it with a valid call.
rillsoft_project_renumberNo check listed here called it with a valid call.
rillsoft_project_rescheduleNo check listed here called it with a valid call.
rillsoft_project_ris_deleteNo check listed here called it with a valid call.
rillsoft_project_ris_listNo check listed here called it with a valid call.
rillsoft_project_ris_openNo check listed here called it with a valid call.
rillsoft_project_ris_saveNo check listed here called it with a valid call.
rillsoft_project_ris_save_asNo check listed here called it with a valid call.
rillsoft_project_sortNo check listed here called it with a valid call.
rillsoft_project_status_date_rescheduleNo check listed here called it with a valid call.
rillsoft_project_status_date_setNo check listed here called it with a valid call.
rillsoft_project_team_preference_removeNo check listed here called it with a valid call.
rillsoft_project_team_preference_setNo check listed here called it with a valid call.
rillsoft_project_tree_getNo check listed here called it with a valid call.
rillsoft_project_updateNo check listed here called it with a valid call.
rillsoft_property_panel_closeNo check listed here called it with a valid call.
rillsoft_property_panel_getNo check listed here called it with a valid call.
rillsoft_property_panel_openNo check listed here called it with a valid call.
rillsoft_resource_absence_listNo check listed here called it with a valid call.
rillsoft_resource_absence_syncNo check listed here called it with a valid call.
rillsoft_resource_pool_catalog_listNo check listed here called it with a valid call.
rillsoft_resource_pool_edit_closeNo check listed here called it with a valid call.
rillsoft_resource_pool_edit_openNo check listed here called it with a valid call.
rillsoft_resource_pool_edit_saveNo check listed here called it with a valid call.
rillsoft_resource_pool_file_selectNo check listed here called it with a valid call.
rillsoft_resource_pool_getNo check listed here called it with a valid call.
rillsoft_resource_pool_resource_createNo check listed here called it with a valid call.
rillsoft_resource_pool_resource_deleteNo check listed here called it with a valid call.
rillsoft_resource_pool_resource_getNo check listed here called it with a valid call.
rillsoft_resource_pool_resource_updateNo check listed here called it with a valid call.
rillsoft_resource_pool_ris_listNo check listed here called it with a valid call.
rillsoft_resource_pool_ris_selectNo check listed here called it with a valid call.
rillsoft_resource_usage_listNo check listed here called it with a valid call.
rillsoft_resource_usage_setNo check listed here called it with a valid call.
rillsoft_row_selection_applyNo check listed here called it with a valid call.
rillsoft_row_selection_getNo check listed here called it with a valid call.
rillsoft_session_dialogs_setNo check listed here called it with a valid call.
rillsoft_subproject_createNo check listed here called it with a valid call.
rillsoft_subproject_deleteNo check listed here called it with a valid call.
rillsoft_subproject_updateNo check listed here called it with a valid call.
rillsoft_task_createNo check listed here called it with a valid call.
rillsoft_task_deleteNo check listed here called it with a valid call.
rillsoft_task_dependency_createNo check listed here called it with a valid call.
rillsoft_task_dependency_deleteNo check listed here called it with a valid call.
rillsoft_task_employee_assignment_setNo check listed here called it with a valid call.
rillsoft_task_machine_assignment_setNo check listed here called it with a valid call.
rillsoft_task_machine_role_assignment_deriveNo check listed here called it with a valid call.
rillsoft_task_machine_role_assignment_setNo check listed here called it with a valid call.
rillsoft_task_material_assignment_setNo check listed here called it with a valid call.
rillsoft_task_progress_recalculateNo check listed here called it with a valid call.
rillsoft_task_progress_setNo check listed here called it with a valid call.
rillsoft_task_resource_assignment_fillNo check listed here called it with a valid call.
rillsoft_task_resource_assignment_removeNo check listed here called it with a valid call.
rillsoft_task_resource_candidate_listNo check listed here called it with a valid call.
rillsoft_task_role_assignment_deriveNo check listed here called it with a valid call.
rillsoft_task_role_assignment_setNo check listed here called it with a valid call.
rillsoft_task_splitNo check listed here called it with a valid call.
rillsoft_task_split_options_getNo check listed here called it with a valid call.
rillsoft_task_updateNo check listed here called it with a valid call.
rillsoft_timescale_applyNo check listed here called it with a valid call.
rillsoft_variance_report_getNo check listed here called it with a valid call.
rillsoft_view_columns_applyNo check listed here called it with a valid call.
rillsoft_view_columns_getNo check listed here called it with a valid call.
rillsoft_view_favorite_createNo check listed here called it with a valid call.
rillsoft_view_favorite_deleteNo check listed here called it with a valid call.
rillsoft_view_favorite_listNo check listed here called it with a valid call.
rillsoft_view_favorite_selectNo check listed here called it with a valid call.
rillsoft_view_state_applyNo check listed here called it with a valid call.
rillsoft_view_state_getNo check listed here called it with a valid call.
rillsoft_window_layout_applyNo check listed here called it with a valid call.
rillsoft_window_layout_getNo check listed here called it with a valid call.

What was not covered

Grade over time

Since the run on

Same as that run: the same grade in every test area, the same server version (10.0.626), the same Sealmark version (1.0.1).

  1. Av10.0.626Sealmark 1.0.0
  2. Av10.0.626Sealmark 1.0.1
  3. Av10.0.626Sealmark 1.0.1

Project facts

License
CC-BY-4.0
Latest release
10.0.626, published 17 Oct 2026
Repository
rillsoft/rillsoft-project-mcp
Last push
8 Nov 2026
Open issues and pull requests
0

From GitHub, checked 22 Nov 2026. Plain facts about the project; they play no part in the grade.

Run it yourself

This repeats the run with the same Sealmark version and the standard settings, starting the server the same way:

npx -y sealmark@1.0.1 run --start "npx -y github:rillsoft/rillsoft-project-mcp"

To confirm your run used the standard settings, add --format json --out report.json to the command. In the report, config.standard should be true and config.hash should start with sha256:d13e7893a0ac, as they did in this run. If either differs, so did the settings, and the verdicts may too (STANDARD and CUSTOM runs).

To keep the setup, put the start command in sealmark.yaml as the server.

Grade alerts

One email when the grade of rillsoft/rillsoft-project-mcp changes after a re-test. Nothing else, and every email has a link to stop them.

Or follow it in a feed reader: the Atom feed lists each move of the overall grade that came with a different version of this server, tested with the same Sealmark version as the graded run before.

Each of 613 verdicts was checked independently, and Sealmark was wrong on some: how reliable Sealmark is.

Is this wrong?

Reply on the GitHub issue 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.