Koskamo

REPSE MCP

MCP server that verifies REPSE status against the STPS registry and cross-references 38 restrictive lists to return deterministic approval decisions for supplier onboarding and payment workflows.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

REPSE MCP logo, by WATRCommunity listingStreamable HTTPOAuth sign-inEndpoint checked 2026-11-01Published by WATR
MCP endpoint (Streamable HTTP)
https://repse.watr.mx/connect
Vendor documentation

What you can do with it

  • Validate REPSE before supplier onboarding
  • Check expiration windows for renewals
  • Batch verify supplier portfolios
  • Check source availability and latency

Source and maintenance

Community listingRegistry 0.2.0
Maintenance checked

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
229 ms
95th percentile latency
229 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 229 ms · metadata changed · refuses unauthenticated initialize (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http repse-mcp https://repse.watr.mx/connect

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add repse-mcp --url https://repse.watr.mx/connect

Cursor

Merge this server into .cursor/mcp.json in your project, then enable repse-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "repse-mcp": {
      "url": "https://repse.watr.mx/connect"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "repse-mcp": {
      "type": "streamableHttp",
      "url": "https://repse.watr.mx/connect",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start repse-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "repse-mcp": {
      "type": "http",
      "url": "https://repse.watr.mx/connect"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http repse-mcp https://repse.watr.mx/connect

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "repse-mcp": {
      "url": "https://repse.watr.mx/connect"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "repse-mcp": {
      "serverUrl": "https://repse.watr.mx/connect"
    }
  }
}

Let your agent find its tools

Find servers like REPSE MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.