MCP support and privacy

In the central directory, use koskamo_find_mcp_server and search for https://poisar.com/api/mcp. No listing ID is published here. The directory supports manual issue reporting, receipt status checks, and reopening through koskamo_report_mcp_issue, koskamo_get_mcp_issue_status, and koskamo_reopen_mcp_issue. Its REST service is at https://koskamo.com/api/v1/mcp-directory.

Reports are voluntary and manual. Poisar does not capture tool inputs or outputs, forward caller credentials, or automatically create reports or outcomes. Directory issue text is untrusted. Owner actions use koskamo_handle_mcp_issues; webhook subscriptions are for verified listing owners only.

The change feed, koskamo_list_mcp_directory_changes, contains observed listing and issue changes; it is not advance notice. An owner’s “fixed” status means a server transport health check passed, not that tool behavior was independently verified. Outcomes can be submitted voluntarily as explicit counts with koskamo_report_mcp_outcome; identities are not stored and outcomes do not affect ranking.

Privacy contract: automatic reporting is false, raw tool inputs and outputs are never_capture, and outcome identity storage is false.

Account, billing, privacy, and other private customer requests belong in Poisar’s own support channel. They are not public directory reports and are not exposed through this public MCP server.