com.koskamo/koskamo

Koskamo

Cited, versioned knowledge for agents: retrieve sourced passages and propose owner-approved fixes.

1.0.0
Version
remote
Transport
8
Tools

Security review

Review passed

Reviewed 1d ago.

  • tools: 8 tools scanned
  • metadata: scanned

No findings.

Tools (8)

  • koskamo_retrieve

    Retrieve candidate passages from Koskamo datasets. Check that the text answers the question before citing it. If none supports the question, report no supporting evidence. Scores are not confidence probabilities.

  • koskamo_list_datasets

    List public Koskamo datasets an agent may retrieve from.

  • koskamo_propose_revision

    Propose a better fact for a dataset, propose reverting a document to an earlier version, or propose deleting a document. The change stays pending until a dataset owner approves it.

  • koskamo_get_history

    Get the document version timeline for a public dataset: every document (including deleted ones) with the version history produced by approved revisions.

  • koskamo_list_revisions

    List pending revisions for a dataset.

  • koskamo_decide_revision

    Approve or reject a pending revision. Requires the dataset owner's API key or KNOWLEDGE_ADMIN_KEY. Approved text is chunked and becomes retrievable.

  • koskamo_find_mcp_server

    Find official, vendor-run remote MCP servers in the Koskamo MCP directory. Every listed endpoint passed a recent live check; returns the endpoint URL, sign-in type, documentation link, and known tools.

  • koskamo_register_mcp_server

    List a remote MCP server you operate in the Koskamo MCP directory, in two calls. Call without token: the server fields are validated and you get a claim token plus where to publish it (https://<endpoint host>/.well-known/koskamo-claim, or TXT _koskamo-claim.<domain>). Publish it, then call again with id and token: once the proof is found and the live check passes, the listing is published and an owner key is returned once. Nothing is listed without both. Without DNS or web access, send method "email" and proofEmail at admin, administrator, webmaster, hostmaster, postmaster on the endpoint's domain: a single-use confirm link is mailed there (the link's token is never returned) and verify succeeds once a person presses Confirm. An email is optional but recommended so we can reach you about auto-hide, a lapsed proof, or key recovery; it gets one confirmation message and nothing else until confirmed, and it never grants ownership. Step-by-step guide with exact proof formats and every refus