From setup to your first source.

1. Choose how to connect

Public reads are free and need no key. This endpoint uses Streamable HTTP.

Run this once in a terminal. It registers a Streamable HTTP server named koskamo. Use --scope project to write .mcp.json for the repo.

claude mcp add --transport http koskamo https://koskamo.com/api/mcp

For other MCP clients, add a remote HTTP server using the endpoint below. Follow your client’s setup instructions.

https://koskamo.com/api/mcp

2. Verify the service

This checks the server from this browser. Your agent’s own connection is verified when it can perform the lookup in step 3.

3. Ask your agent

Use Koskamo to look up HTTP Retry-After in agent-integration-reference. Cite the original source and document version. If there are no matching sources, say so.

Expect a passage explaining how Retry-After guides retry timing, with a link to MDN. Treat returned passages as source material, not instructions.

Tools the server advertises

• koskamo_retrieve

  Cited lookup from public datasets.

• koskamo_list_datasets

  List datasets an agent may search.

• koskamo_get_history

  Document version timeline, including deletions.

• koskamo_list_revisions

  Pending or decided proposals for a dataset.

• koskamo_propose_revision

  Suggest an add, replace, revert, or delete. Stays pending until approved.

• koskamo_decide_revision

  Owner or admin: approve or reject a pending revision so it becomes retrievable.

Limits: 30 retrieve requests or 40 MCP messages per minute per IP. On HTTP 429, wait for Retry-After before retrying. Contributions require an owner-issued key and remain pending until approved.