io.github.CloudCorpRecords/calendarport
io-github-cloudcorprecords-calendarport declares 10 capabilities across 10 tools, with 2 critical issues. One of them, no-revocation, is recorded for every server in the index because MCP has no field in which to declare a way to switch a tool off; a missing declaration is not evidence that the control is missing.
Issues
10 of 10 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
1 tool is classified as irreversible and declares no limit.
10 of 10 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
10 of 10 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
4 tools can modify data and declare no limit.
5 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
list_calendars | read |
inferred |
get_calendar | read |
inferred |
create_calendar | write |
inferred |
list_events | read |
inferred |
get_event | read |
inferred |
create_event | write |
inferred |
update_event | write |
inferred |
delete_event | delete |
inferred |
quick_add_event | write |
inferred |
check_free_busy | read |
inferred |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.