---
title: "Opt a verified MCP server in/out of the Honor Roll"
method: PUT
path: "/mcp-servers/{id}/honor-roll"
tags: ["MCP Servers"]
---

# Opt a verified MCP server in/out of the Honor Roll

`PUT /mcp-servers/{id}/honor-roll`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/mcp-servers/{id}/honor-roll`
- Auth: one of:
  - API key in cookie `mnemom_session`
  - HTTP bearer

Sets explicit, revocable Honor Roll consent for a verified MCP server. Verified claims only (409 otherwise). The `{id}` path parameter is the URL-encoded server endpoint URL. Authorization: the update is scoped in SQL to the caller's own organization's verified claim for this server (`owner_org_id = <caller's org>`); a server the caller has not verified for their own org matches no row and returns 409, so another org's claim is never visible or mutable.

## Path parameters

- `id` string, required

## Request body

- object
  - `optIn` boolean, required

## Response `200`

Updated Honor Roll state.

- object
  - `server_id` string, required
  - `honor_roll` boolean, required
  - `verified_at` string, date-time, nullable

## Other responses

- `400`: Bad request
- `401`: Authentication required
- `403`: Cross-origin write refused (`cross_origin_rejected`). A state-changing request that carries the browser session cookie must come from a first-party origin (`Origin`, or failing that `Referer`) and must not send a form-style body (text/plain, urlencoded, multipart) the operation does not declare. Bearer and API-key callers are never subject to this check.
- `409`: Resource conflict — the request cannot proceed because of a current state conflict (e.g., resource already exists, version mismatch, in-flight idempotency key with a different body).
- `429`: Rate-limit exceeded. The global per-IP limiter (100 requests/minute, applied to every `/v1/*` route) rejected this request. Back off until the window resets — `Retry-After` carries the cooldown in seconds and `X-RateLimit-Reset` the absolute reset time.
- `500`: Server error — request was well-formed but the server failed to fulfill it. Typically a downstream dependency (DB / RPC / external API) returned an unexpected error.
- `503`: An upstream dependency is currently unavailable. The request was not processed; retry after the cooldown window.

---

[API](https://skmtc.dev/mnemom/apis/mnemom-api.md) · [All operations](https://skmtc.dev/mnemom/apis/mnemom-api/llms.txt) · [OpenAPI document](https://skmtc.dev/mnemom/apis/mnemom-api/revisions/274b7a6ea182?raw)