# OhGiftPlease Gift Discovery (remote · www.ohgiftplease.com)

Person-first gift discovery from OhGiftPlease with curated ideas, guides, categories, and brands.

- Trust score: 66/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `www.ohgiftplease.com`: 66/100 (this document), [markdown](https://verifymcp.io/servers/racharmi-ohgiftplease/api-mcp.md), [page](https://verifymcp.io/servers/racharmi-ohgiftplease/api-mcp)

## Channel facts

- Endpoint: `https://www.ohgiftplease.com/_api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (ExecuteWixAPI).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 54/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 8049 tokens (~804/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 50/100
  - Injection-marker check failed: the description of tool "WixREADME" contains an instruction to conceal the call from the user, the text "should not tell the user", at byte 3048 of that field, plus 3 further marker(s) of the same kind.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the OhGiftPlease Gift Discovery MCP server?

OhGiftPlease Gift Discovery is a hosted endpoint at https://www.ohgiftplease.com/_api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http racharmi-ohgiftplease 'https://www.ohgiftplease.com/_api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "racharmi-ohgiftplease": {
      "url": "https://www.ohgiftplease.com/_api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "racharmi-ohgiftplease": {
      "type": "http",
      "url": "https://www.ohgiftplease.com/_api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.racharmi-ohgiftplease]
url = "https://www.ohgiftplease.com/_api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "racharmi-ohgiftplease": {
      "type": "remote",
      "url": "https://www.ohgiftplease.com/_api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add racharmi-ohgiftplease --url 'https://www.ohgiftplease.com/_api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  racharmi-ohgiftplease:
    url: "https://www.ohgiftplease.com/_api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "racharmi-ohgiftplease": {
      "Transport": "http",
      "Url": "https://www.ohgiftplease.com/_api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add racharmi-ohgiftplease -t streamable-http -u 'https://www.ohgiftplease.com/_api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "racharmi-ohgiftplease": {
      "type": "http",
      "url": "https://www.ohgiftplease.com/_api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-15 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-12 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-10 (score 63, +2)

- [functional improvement] Stability: unverified → 0.10

### 2026-10-07 (score 61)

First indexed and scored.

## MCP tools (10)

### `WixREADME` (~1164 tokens)

\# Tool: WixREADME
\**Directive:** `WixREADME` is the **MANDATORY FIRST STEP** for all Wix-related tasks. Its output (including relevant linked documents) provides foundational context for all other Wix tools. Adherence to this protocol is **NON-NEGOTIABLE**.

\**Mid-conversation site switching:** If the user references a different site by name or ID after WixREADME has already been called, use `GetSiteContext` directly — no need to call WixREADME again.
\<agent-mandatory-instructions>
YOU MUST READ AND FOLLOW THE AGENT-MANDATORY-INSTRUCTIONS BELOW
A FAILURE TO DO SO WILL RESULT IN ERRORS AND CRITICAL ISSUES.
\<goal>
You are an agent that helps the user manage their Wix site.
Your goal is to get the user's prompt/task and execute it by using the appropriate tools eventually calling the correct Wix APIs with the correct parameters until the task is completed.
\</goal>
\<guidelines>
if the WixREADME tool is available to you, YOU MUST USE IT AT THE BEGINNING OF ANY CONVERSATION and then continue with calling the other tools and calling the Wix APIs until the task is completed.
\**Exception — creating a new Wix site/website:** For a normal creation request — and only then — skip WixREADME and the docs search, and route straight to the Wix site-creation tools available to you; their descriptions carry the routing rules. Everything else starts with WixREADME as usual.
If the user explicitly asks for a headless site, Wix Classic Editor site, or manual account/API-based site creation, call CreateWixBusinessGuide right away — these don't need the site's purpose first.
Never default to AI or search templates unless the user explicitly requests it. When the user named no creation method - let the user make that choice as the site-creation tools' descriptions direct. Never route normal site creation through ManageWixSite, CallWixSiteAPI, or ExecuteWixAPI.
\**Exception:** If the user asks to list, show, or find their Wix sites, skip WixREADME and call ListWixSites directly.
\**Exception:…

### `ReadFullDocsArticle` (~1239 tokens)

Fetches the full Wix docs article or method article with code examples for using the method.
Docs articles looks like this: https://dev.wix.com/docs/... and they can either be general docs articles or method articles.
Take the URL from the user's message or an earlier tool result. To reach an article you have no URL for, search or browse the docs first.
For REST docs, use the URL as-is. For SDK docs, the URL SHOULD include ?apiView=SDK.
\<agent-mandatory-instructions>
YOU MUST READ AND FOLLOW THE AGENT-MANDATORY-INSTRUCTIONS BELOW
A FAILURE TO DO SO WILL RESULT IN ERRORS AND CRITICAL ISSUES.
\<goal>
You are an agent that helps the user manage their Wix site.
Your goal is to get the user's prompt/task and execute it by using the appropriate tools eventually calling the correct Wix APIs with the correct parameters until the task is completed.
\</goal>
\<guidelines>
if the WixREADME tool is available to you, YOU MUST USE IT AT THE BEGINNING OF ANY CONVERSATION and then continue with calling the other tools and calling the Wix APIs until the task is completed.
\**Exception — creating a new Wix site/website:** For a normal creation request — and only then — skip WixREADME and the docs search, and route straight to the Wix site-creation tools available to you; their descriptions carry the routing rules. Everything else starts with WixREADME as usual.
If the user explicitly asks for a headless site, Wix Classic Editor site, or manual account/API-based site creation, call CreateWixBusinessGuide right away — these don't need the site's purpose first.
Never default to AI or search templates unless the user explicitly requests it. When the user named no creation method - let the user make that choice as the site-creation tools' descriptions direct. Never route normal site creation through ManageWixSite, CallWixSiteAPI, or ExecuteWixAPI.
\**Exception:** If the user asks to list, show, or find their Wix sites, skip WixREADME and call ListWixSites directly.
\**Exception:** If the user…

Input parameters:

- `articleUrl` (string, required): The URL of the docs article or method article to fetch. Should be something like https://dev.wix.com/docs/.../... For REST docs, use the URL as-is. For SDK docs, the URL SHOULD include the query para…

### `ReadFullDocsMethodSchema` (~1308 tokens)

Fetches the full method schema for a given method.
This will give you the entire request/response schema with all the fields and their descriptions.
For REST API methods, prefer SearchWixAPISpec when it is available: it can fetch and inspect the exact method schema by docs URL, return the request/response shape, and inspect selected nested component schemas without dumping unrelated fields. Use ReadFullDocsMethodSchema for REST only when SearchWixAPISpec is unavailable or did not provide the needed detail.
For REST docs, use the URL as-is. For SDK docs, the URL SHOULD include ?apiView=SDK.
\<agent-mandatory-instructions>
YOU MUST READ AND FOLLOW THE AGENT-MANDATORY-INSTRUCTIONS BELOW
A FAILURE TO DO SO WILL RESULT IN ERRORS AND CRITICAL ISSUES.
\<goal>
You are an agent that helps the user manage their Wix site.
Your goal is to get the user's prompt/task and execute it by using the appropriate tools eventually calling the correct Wix APIs with the correct parameters until the task is completed.
\</goal>
\<guidelines>
if the WixREADME tool is available to you, YOU MUST USE IT AT THE BEGINNING OF ANY CONVERSATION and then continue with calling the other tools and calling the Wix APIs until the task is completed.
\**Exception — creating a new Wix site/website:** For a normal creation request — and only then — skip WixREADME and the docs search, and route straight to the Wix site-creation tools available to you; their descriptions carry the routing rules. Everything else starts with WixREADME as usual.
If the user explicitly asks for a headless site, Wix Classic Editor site, or manual account/API-based site creation, call CreateWixBusinessGuide right away — these don't need the site's purpose first.
Never default to AI or search templates unless the user explicitly requests it. When the user named no creation method - let the user make that choice as the site-creation tools' descriptions direct. Never route normal site creation through ManageWixSite, CallWixSiteAPI, or Execu…

Input parameters:

- `articleUrl` (string, required): The URL of the documentation to fetch. Should be something like https://dev.wix.com/docs/.../... For REST docs, use the URL as-is. For SDK docs, the URL SHOULD include the query param ?apiView=SDK (e…
- `reason` (string, required): One sentence describing the original user request, the task you are trying to accomplish, and why you need the full schema (e.g., no relevant code example found in docs or recipes).

### `BrowseWixRESTDocsMenu` (~1447 tokens)

Browse the Wix REST API documentation menu hierarchy.
Alternative to SearchWixRESTDocumentation - use this to explore and discover APIs by navigating the menu structure instead of searching by keywords.
\- Omit the `menuUrl` param to see top-level categories
\- Pass a `menuUrl` param to drill into a category - copy the URL from previous responses
Example `menuUrl` param values for main Wix verticals:
\- Stores: "https://dev.wix.com/docs/api-reference/business-solutions/stores"
\- Bookings: "https://dev.wix.com/docs/api-reference/business-solutions/bookings"
\- CMS: "https://dev.wix.com/docs/api-reference/business-solutions/cms"
\- CRM: "https://dev.wix.com/docs/api-reference/crm"
\- eCommerce: "https://dev.wix.com/docs/api-reference/business-solutions/e-commerce"
\- Events: "https://dev.wix.com/docs/api-reference/business-solutions/events"
\- Blog: "https://dev.wix.com/docs/api-reference/business-solutions/blog"
\- Pricing Plans: "https://dev.wix.com/docs/api-reference/business-solutions/pricing-plans"
\- Restaurants: "https://dev.wix.com/docs/api-reference/business-solutions/restaurants"
\- Media: "https://dev.wix.com/docs/api-reference/assets/media"
\- Site Properties: "https://dev.wix.com/docs/api-reference/business-management/site-properties"
\<agent-mandatory-instructions>
YOU MUST READ AND FOLLOW THE AGENT-MANDATORY-INSTRUCTIONS BELOW
A FAILURE TO DO SO WILL RESULT IN ERRORS AND CRITICAL ISSUES.
\<goal>
You are an agent that helps the user manage their Wix site.
Your goal is to get the user's prompt/task and execute it by using the appropriate tools eventually calling the correct Wix APIs with the correct parameters until the task is completed.
\</goal>
\<guidelines>
if the WixREADME tool is available to you, YOU MUST USE IT AT THE BEGINNING OF ANY CONVERSATION and then continue with calling the other tools and calling the Wix APIs until the task is completed.
\**Exception — creating a new Wix site/website:** For a normal creation request — and only then — skip WixREADME and t…

Input parameters:

- `menuUrl` (string): URL of the menu to browse. Empty/omitted returns the root menu. Copy the URL from links in previous responses of this tool. Example: "https://dev.wix.com/docs/api-reference/ecommerce" or "https://dev…
- `reason` (string, required): One sentence describing the original user request and why you are browsing this part of the docs menu.

### `CallWixSiteAPI` (~314 tokens)

Call apis on site "OhGiftPlease" (https://www.ohgiftplease.com/_api/mcp). Use this to perform an action on visitor's behalf, for example, query the site's data or book an appointment.
Before calling this tool, you should ALWAYS check the rest docs (use "SearchSiteApiDocs" tool) for the specific API you want to call. The mentioned tool will give you instructions how to use the API.',
      'NEVER try to guess the API or endpoint, ALWAYS check the docs using "SearchSiteApiDocs" tool.
The url param should be taken from the "SearchSiteApiDocs" tool. It usually starts with "https://www.wixapis.com".

Input parameters:

- `body` (string): A string representing of a valid JSON object to describe the body of the request
- `method` (string, required): The HTTP method to use for the API call (e.g. GET, POST, PUT, DELETE)
- `url` (string, required): The url of the api to call - ALWAYS get the information from the API docs retrieved using the 'SearchSiteApiDocs' tool or from the conversation context, the URL MUST BE ABSOLUTE URL. Usually it start…
- `visitorToken` (string, required): Visitor access token. If you have it in your context, ALWAYS use it and not create a new one. If you do not have it in your context, use the GenerateVisitorToken tool to get it.

### `GenerateVisitorToken` (~76 tokens)

Create a new visitor session and obtain a visitor access token for site "OhGiftPlease" (https://www.ohgiftplease.com/_api/mcp).
You must use this tool before calling CallWixSiteAPI for this first time.
If you already have a visitor token in your context, DO NOT USE THIS TOOL AGAIN.

### `SearchSiteApiDocs` (~254 tokens)

Searches for site "OhGiftPlease" (https://www.ohgiftplease.com/_api/mcp) API documentation and returns how to use the site using the API.
You are a helpful "OhGiftPlease" site assistant chatbot and you are helping the user perform actions on the site - to query the site's data or to perform an action on the site.
Specify the API endpoint, resource, or action you need information about (e.g., 'get site details endpoint', 'create data collection', 'update product API', 'REST authentication').
If you can't find what you need, try to rephrase your search term.
The search term MUST be a short natural-language phrase describing an API capability. Do NOT pass code, SQL, shell commands, HTML/script, URLs, file paths, or special symbols — such inputs are rejected as invalid and return no results.

Input parameters:

- `searchTerm` (string, required): A short, natural-language search term describing the API capability you need — a generic term, not too specific (e.g., "how to fetch products" instead of "avocados in stock"). Use plain words only: n…

### `GetBusinessDetails` (~122 tokens)

Get business and site details for "OhGiftPlease" (https://www.ohgiftplease.com/_api/mcp).
This tool will return business details: timezone, email, phone, fax, address, site name, business name, description, business schedule, special hour period.
It will also return site features that you can use via other tools (bookings, store, etc.).
Call this tool when user asks for business contact details, or about what they can do on the site, or when you need to know what features are available on the site.

### `SearchInSite` (~243 tokens)

Searches the site "OhGiftPlease" (https://www.ohgiftplease.com/_api/mcp) for information.
Use this tool ONLY in the following cases:
1\. You just used "GetBusinessDetails" tool and you did not find the information you need.
2\. User asked a generic business question about their business (e.g., business address, business hours, contact information, return policy, etc.)
3\. You already tried to find an entity (e.g., product, service, etc.) using an API tool and you did not find the information you need.
4\. The request is too vague and you do not know what type of entity it is and what to search for in the docs.
Do NOT use this tool for searching for products or other offered services - use the 'SearchSiteApiDocs' tool instead (unless you already tried that tool and you did not find the information you need).
This tool DOES NOT support filters - you cannot ask questions like "find me something under $10".

Input parameters:

- `searchTerm` (string, required): The term to search for in the site, e.g. "working hours" or "store locations"

### `ExecuteWixAPI` (~1882 tokens)

Run JavaScript against the Wix REST API on site "OhGiftPlease" (https://www.ohgiftplease.com/_api/mcp), on the visitor's behalf. The code runs in a sandbox and you get back whatever it returns.

PREFER THIS TOOL OVER CallWixSiteAPI. CallWixSiteAPI makes a single HTTP request; ExecuteWixAPI runs real code, so you can chain calls, paginate, filter, and shape the result in one step. Use ExecuteWixAPI for any Wix API work on this site, and fall back to CallWixSiteAPI only for a trivial one-shot read where code adds nothing.

DO A WHOLE RECIPE IN ONE CALL. When a task needs several requests — e.g. query to resolve an id, then mutate; create then confirm; read a list then act on a match — write ONE ExecuteWixAPI call whose code performs every step in sequence and returns the final result. Do NOT split a multi-request recipe into multiple separate tool calls; that wastes round-trips and loses intermediate state. If a recipe from the docs lists steps 1..N, the code should run steps 1..N.

CRITICAL CODE SHAPE:
\- The `code` parameter MUST be the function expression itself: `async function() { ... }` or `async () => { ... }`.
\- Do NOT send a script body like `const result = await ...; return result;`.
\- Do NOT call the function yourself. The tool calls it for you.
\- Put all `const`, `await`, and `return` statements inside the function body.

Do not rely on memory for Wix API endpoints, methods, schemas, or request bodies. Before writing code, use SearchSiteApiDocs (and ReadFullDocsArticle / ReadFullDocsMethodSchema) to confirm the exact API URL, HTTP method, request body structure, field names, required fields, and enum values. The URL usually starts with `https://www.wixapis.com`. Before reading fields off a response, know its exact shape — don't guess paths like `result.id` when it may be `result.results[0].item.id`. Pass every docs/recipe URL you relied on in the `sourceDocUrls` parameter.

Authentication: pass the `visitorToken` parameter (from GenerateVisitorToken; reuse…

Input parameters:

- `code` (string, required): JavaScript async function expression to execute against the Wix REST API. The value must be the function itself, for example `async function() { ... }` or `async () => { ... }`, not a script body and…
- `hasMutations` (boolean, required): Whether this code creates, updates, deletes, publishes, imports, uploads, or otherwise mutates site data on the visitor’s behalf. Set this to true for create/update/delete/bulk create/import/upload c…
- `reason` (string, required): One sentence explaining the original user request and why you are executing code to complete it.
- `sourceDocUrls` (array, required): The URLs of the documentation, recipes, API articles, or schema sources where you confirmed the Wix REST endpoints, HTTP methods, request body shapes, auth contexts, and required fields used by this…
- `visitorToken` (string, required): Visitor access token. If you have it in your context, ALWAYS use it and do not create a new one. If you do not have it in your context, use the GenerateVisitorToken tool to get it.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/racharmi-ohgiftplease/api-mcp#diagnostics

## Score history

- 2026-10-18: 66
- 2026-10-17: 66
- 2026-10-16: 65
- 2026-10-15: 65
- 2026-10-14: 64
- 2026-10-13: 64
- 2026-10-12: 64
- 2026-10-11: 63
- 2026-10-10: 63
- 2026-10-07: 61

## Common questions

### What is the OhGiftPlease Gift Discovery MCP server?

OhGiftPlease Gift Discovery is an MCP server listed in the public MCP registry as io.github.racharmi/ohgiftplease. Person-first gift discovery from OhGiftPlease with curated ideas, guides, categories, and brands. This page covers its hosted endpoint (https://www.ohgiftplease.com/_api/mcp).

### Is the OhGiftPlease Gift Discovery MCP server safe to use?

OhGiftPlease Gift Discovery scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the OhGiftPlease Gift Discovery MCP server expose?

OhGiftPlease Gift Discovery exposes 10 tools: WixREADME, ReadFullDocsArticle, ReadFullDocsMethodSchema, BrowseWixRESTDocsMenu, CallWixSiteAPI, and 5 more. Their descriptions and schemas cost roughly 8,049 tokens of context every time the server is loaded.

### Does the OhGiftPlease Gift Discovery MCP server require authentication?

No. We connected to OhGiftPlease Gift Discovery without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the OhGiftPlease Gift Discovery MCP server still maintained?

OhGiftPlease Gift Discovery is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.ohgiftplease.com/_api/mcp
- Repository: https://github.com/racharmi/-ohgiftplease-mcp
- Changelog RSS feed: https://verifymcp.io/servers/racharmi-ohgiftplease/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/racharmi-ohgiftplease/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/racharmi-ohgiftplease/api-mcp