OhGiftPlease Gift Discovery MCP server
io.github.racharmi/ohgiftpleaseracharmistreamable-httpv1.0.0Scanned
Person-first gift discovery from OhGiftPlease with curated ideas, guides, categories, and brands.
10 tools: 1 can delete or cancel things, 3 change things and 6 only read.
- Reads private data · 4
- Reads text others write · 5
- Can send data out · 1
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the OhGiftPlease Gift Discovery MCP server can do
The OhGiftPlease Gift Discovery MCP server is published by the GitHub account racharmi. It has 10 tools. It can delete or cancel things (1 tool: ExecuteWixAPI) and create or change data (3 tools: WixREADME, CallWixSiteAPI and GenerateVisitorToken). 6 tools only read.
4 tools read private data (ReadFullDocsArticle, ReadFullDocsMethodSchema, BrowseWixRESTDocsMenu and 1 more); 5 tools bring in text other people can write (BrowseWixRESTDocsMenu, SearchSiteApiDocs, GetBusinessDetails and 2 more); 1 tool can send data out of your system (CallWixSiteAPI). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 2 findings (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
10 tools
Deletes or cancels 1Claude Code: deny
ExecuteWixAPIRun JavaScript against the Wix REST API on site "OhGiftPlease" (https://www.ohgiftplease.com/_api/mcp), on the visitor's behalf.Reads text others write1 finding
Why it is in this group
- The name "ExecuteWixAPI" says "execute": a word for a change.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description is 5,362 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...{ cartId: cart.data.cart?.id, productId: product.id, name: product.name }; } ```"
Description, as the server wrote it 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 the one already in your context, do not create a new one each call). Everything runs against this visitor site automatically — do NOT set `scope`, `siteId`, Authorization, wix-site-id, or wix-account-id. File and export limits: ExecuteWixAPI is only for Wix REST API calls and in-memory data shaping. It does not provide Node.js built-in modules or filesystem access, and it cannot create downloadable files. Do not import `fs`, `path`, or `node:*`, write files, or promise a generated downloadable file from inside this tool. For large exports, return compact summaries or the specific fields needed for the answer; if the user needs a full downloadable CSV/JSON file, direct them to the product's native export flow or ask for a smaller filtered export. Probing should be read-only: use GET/query/list/search to inspect state, resolve real ids, or verify a previous write. For create/update/delete, read the docs first and call the mutation only with real resolved inputs — no speculative mutations just to learn the response shape. Error handling: `wix.request()` throws when the Wix API returns an error. For dependent steps, let it throw so the failure is reported clearly. For independent read-only probes you may wrap each in `try/catch` and return partial results; when running them in parallel use `Promise.allSettled` (not `Promise.all`) so one failure doesn't discard the rest. Available in your code: ```typescript interface WixRequestOptions { method: "GET" | "POST" | "PUT" | "PATCH" | "DELETE"; url: string; // Full Wix API URL, e.g. "https://www.wixapis.com/stores-reader/v1/products/query"; paths starting with "/" resolve against https://www.wixapis.com body?: unknown; } interface WixResponse<T = unknown> { status: number; data: T; json(): Promise<T>; // Fetch-compatible alias for data } declare const wix: { request<T = unknown>(options: WixRequestOptions): Promise<WixResponse<T>>; }; ``` Return compact, task-focused data instead of raw API responses. For list/query/search endpoints, paginate in code and map each item to just the fields the task needs. When the code CREATES entities (create, bulk create, import, duplicate, upload), ALWAYS include the ID of every created entity in the returned object — e.g. `{ cartId }` or `{ createdIds: [...] }` — even if the user did not ask for them; follow-up steps, verification, and cleanup all need those IDs, and recovering them later costs extra query calls. Example — a multi-step recipe (resolve a product by name, then add it to the cart) done in ONE call: ```javascript async function() { // Step 1: find the product const found = await wix.request({ method: "POST", url: "https://www.wixapis.com/stores-reader/v1/products/query", body: { query: { filter: JSON.stringify({ name: "Florie Eau de Parfum" }) } } }); const product = found.data.products?.[0]; if (!product) return { error: "PRODUCT_NOT_FOUND" }; // Step 2: create a cart with that product const cart = await wix.request({ method: "POST", url: "https://www.wixapis.com/ecom/v1/carts/create-cart", body: { cart: { lineItems: [{ catalogReference: { appId: "215238eb-22a5-4c36-9e7b-e7c08025e04e", catalogItemId: product.id }, quantity: 1 }] } } }); return { cartId: cart.data.cart?.id, productId: product.id, name: product.name }; } ```
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- openWorldHint: true
Changes things 3Claude Code: ask
CallWixSiteAPICall apis on site "OhGiftPlease" (https://www.ohgiftplease.com/_api/mcp).Can send data outNo findings
Why it is in this group
- The name "CallWixSiteAPI" says "call": a word for a change.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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".
GenerateVisitorTokenCreate a new visitor session and obtain a visitor access token for site "OhGiftPlease" (https://www.ohgiftplease.com/_api/mcp).No findings
Why it is in this group
- The name "GenerateVisitorToken" says "generate": a word for a change.
Description, as the server wrote it 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.
WixREADME# Tool: WixREADME The context every other Wix tool assumes.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The description is 5,673 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...nd questions as you can; don't tell them which docs to read or which API to call."
Description, as the server wrote it # Tool: WixREADME The context every other Wix tool assumes. Call it first, once per conversation, for any Wix task or question; for another site later in the conversation, call `GetSiteContext` instead of calling this again. A Wix task includes reading or changing a site's or account's data: products, inventory, carts, checkouts, orders, bookings, services, staff, time slots, rentals, restaurant menus, online orders, reservations, events, tickets, RSVPs, blog posts, CMS collections and items, pricing plans, subscriptions, portfolios, gift cards, coupons, donations, forms, form submissions, contacts, members, loyalty points, groups, reviews, inbox messages, CRM tasks, automations, email campaigns, payments, invoices, SEO, redirects, translations, locations, analytics, media files, site properties, installed apps, and the account's sites and domains (searching whether a domain is available, buying one, and connecting one bought elsewhere). These requests skip it and go straight to their own tool: - **Creating a new site.** Skip the docs too. A site is written in code and uploaded: StartDeployWebsite returns the upload guide; StartHeadlessBuild returns the headless guide, for a site that needs Wix business features (a store, bookings or appointments, rentals, events and tickets, a restaurant menu with online orders or reservations, a blog, a portfolio, pricing plans and memberships, donations, Wix Forms, members and login, a CMS, payments). Call one right away, without asking the user anything first: StartHeadlessBuild when the site needs Wix business features, otherwise StartDeployWebsite. A Studio Two (Studio 2) site, new or existing (to build, change, export or import it): StartStudioTwoSite. WixHarmonyEditorBuild or SearchSiteTemplates only when the user asked for Wix's editor, the Wix Harmony Editor, a template, Wix Studio or the Classic Editor. Never create a site through ManageWixSite, CallWixSiteAPI or ExecuteWixAPI. - **Suggesting domain names**: call GetSuggestedDomains directly, with the business or site name as the query. - **Listing, showing or finding their Wix sites**: call ListWixSites directly. - **Uploading local or attached files (images, videos, audio, documents) to a Wix site**: call UploadImageToWixSite directly, with no docs, schema or API calls. Do NOT use ExecuteWixAPI, SearchWixAPISpec, or any Media Manager REST API for these uploads. A question about one of those goes to the same tool ("can you show my sites?" is ListWixSites). Any other Wix question is answered from a Wix skill or the docs, never from memory, and never with a reply that you lack the tools to answer. It returns, in full: - **Source of truth**: nothing Wix-specific from memory. Every URL, ID, setting location, product fact, request shape and field name comes from the docs tools, a Wix skill, an earlier tool result in the conversation, or the user. - **The site**: the account's sites with their properties and installed apps. The `siteId` comes from there (ask when several fit); a business solution's API works only on a site with its app installed, and an app's version changes its endpoints. - **Find the method**: an earlier tool result, else a Wix skill's recipe (wix-manage to manage a site, wix-headless-kit to build a headless one), else the docs: SearchWixRESTDocumentation or BrowseWixRESTDocsMenu, then ReadFullDocsArticle; the SDK, CLI, headless and apps docs for code. - **The exact shape**: model a call only on an example that matches the case; fill the rest with SearchWixAPISpec on the method's docs URL (request and response schemas, `method.publicUrl` for REST, `method.sdk` for the JavaScript SDK). A query's filter and sort fields and operators are a closed list per method. - **The call, or the code**: ExecuteWixAPI runs one async function holding every step code can resolve, the reads and the writes they feed together. Code the user keeps (an app, a headless site, a script over REST or the JavaScript SDK) is written from the same shapes; the headless skills are a shortcut on that path. - **When a call fails**: the error says what was wrong and carries a Wix request id; fix that, never resend unchanged or guess. - **Wix skills**, what each is for and how to read one: from disk when installed (the Wix plugin, or `npx skills add wix/skills`, `--skill <name>` for one, `-g` for the user's home, into `.agents/skills/<skill>/` or a similar folder the client reads, such as `.claude/skills/<skill>/`), else online with ReadFullDocsArticle at `https://www.wix.com/skills/<skill>/<path>`. - **wix-manage**: REST recipes for managing a site's business solutions, one per task; follow the recipe and make its calls with ExecuteWixAPI, its docs URL in `sourceDocUrls`. Its list of recipes is `SKILL.md` in the installed skill, or online https://dev.wix.com/docs/api-reference/articles/ai-tools/wix-mcp/skills/wix-management-recipes-index.md, and each API area has its own `<API section>/skills.md` (for example https://dev.wix.com/docs/api-reference/business-solutions/bookings/skills.md). - **wix-headless-kit**: builds a Wix Headless site on shipped, verified code from wix-headless-templates, a `@wix/sdk` React core or the same data layer as plain REST calls: scaffold with the CLI, deploy, seed, design on the shipped hooks, release. https://www.wix.com/skills/headless-kit/SKILL.md - **wix-headless-templates**: the code wix-headless-kit builds from, one folder per Wix Business Solution. https://www.wix.com/skills/headless-templates/ When the user asks you to do something in Wix, do it yourself, in as few steps and questions as you can; don't tell them which docs to read or which API to call.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
Only reads 6Show 6 read-only tools
BrowseWixRESTDocsMenuBrowse the Wix REST API documentation menu hierarchy.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "BrowseWixRESTDocsMenu" says "browse": a word for reading.
What it can reach
- private-dataThe name "BrowseWixRESTDocsMenu" says "browse" and "doc": it reads documents.
- untrusted-inputThe name "BrowseWixRESTDocsMenu" says "browse": it reads web pages, which anyone can write.
- untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
Description, as the server wrote it 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"
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
GetBusinessDetailsGet business and site details for "OhGiftPlease" (https://www.ohgiftplease.com/_api/mcp).Reads text others writeNo findings
Why it is in this group
- The name "GetBusinessDetails" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "get" and "http": it reads web pages, which anyone can write.
Description, as the server wrote it Get business and site details for "OhGiftPlease" (https://www.ohgiftplease.com/_api/mcp). This tool will return business details: timezone, phone, 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.
ReadFullDocsArticleFetches the full Wix docs article or method article with code examples for using the method.Reads private dataNo findings
Why it is in this group
- The name "ReadFullDocsArticle" says "read": a word for reading.
What it can reach
- private-dataThe name "ReadFullDocsArticle" says "read" and "doc": it reads documents.
- private-dataThe description's first sentence says "fetch" and "doc": it reads documents.
Description, as the server wrote it 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. Also reads Wix skills pages — https://www.wix.com/skills/<skill>, https://dev.wix.com/docs/skills/<skill>, and the files they link (e.g. .../<skill>/references/<file>.md) — and Wix Headless agent pages under https://www.wix.com/headless/ (e.g. https://www.wix.com/headless/skill.md), exactly as served. 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. It returns the whole file. For part of a long skills file, ExecuteWixAPI can fetch the same URL, split the text into lines and return only the lines needed ("How to read a skill" in WixREADME has the code). In ExecuteWixAPI, a dev.wix.com docs page needs `.md` added to its URL, and Help Center articles are not reachable: those are read only with this tool. For REST docs, use the URL as-is. For SDK docs, the URL SHOULD include ?apiView=SDK.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
ReadFullDocsMethodSchemaFetches the full method schema for a given method.Reads private dataNo findings
Why it is in this group
- The name "ReadFullDocsMethodSchema" says "read": a word for reading.
What it can reach
- private-dataThe name "ReadFullDocsMethodSchema" says "read" and "doc": it reads documents.
Description, as the server wrote it 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 and SDK API-reference methods, prefer SearchWixAPISpec when it is available: it can fetch and inspect the exact method schema by docs URL, return the request/response shape, the JavaScript SDK call (`method.sdk`: package, namespace, method, positional parameters, examples), and inspect selected nested component schemas without dumping unrelated fields. Use ReadFullDocsMethodSchema 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
SearchInSiteSearches the site "OhGiftPlease" (https://www.ohgiftplease.com/_api/mcp) for information.Reads text others writeNo findings
Why it is in this group
- The name "SearchInSite" says "search": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "search" and "http": it reads web pages, which anyone can write.
Description, as the server wrote it 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". This tool searches the site's regular pages and blog posts. It does NOT cover pages generated from CMS collections (dynamic item pages). When the site has such pages, the result starts with their paths and how to list the pages under each one.
SearchSiteApiDocsSearches for site "OhGiftPlease" (https://www.ohgiftplease.com/_api/mcp) API documentation and returns how to use the site using the API.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "SearchSiteApiDocs" says "search": a word for reading.
What it can reach
- private-dataThe name "SearchSiteApiDocs" says "search" and "doc": it reads documents.
- untrusted-inputThe description's first sentence says "search" and "http": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
20 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data4
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write5
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__ohgiftplease__CallWixSiteAPI"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:10 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 destructive, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.ohgiftplease.com/_api/mcp: tools/list returned 10 tools to an anonymous client, including ExecuteWixAPI (destructive), WixREADME (write), CallWixSiteAPI (write), GenerateVisitorToken (write)
Findings
Matches of fixed checks, with the text they matched.
- InfoWixREADME
The description is 5,673 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...nd questions as you can; don't tell them which docs to read or which API to call."
- InfoExecuteWixAPI
The description is 5,362 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...{ cartId: cart.data.cart?.id, productId: product.id, name: product.name }; } ```"
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools7 changed.~7 changedView diff
- Changed:BrowseWixRESTDocsMenuOnly readsdescription
- Changed:ExecuteWixAPIDeletes or cancelsinputSchemaannotations
- Changed:GetBusinessDetailsOnly readsdescription
- Changed:ReadFullDocsArticleOnly readsdescriptioninputSchema
- Changed:ReadFullDocsMethodSchemaOnly readsdescription
- Changed:SearchInSiteOnly readsdescription
- Changed:WixREADMEChanges thingsdescription
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http ohgiftplease https://www.ohgiftplease.com/_api/mcpclaude mcp add --transport http ohgiftplease https://www.ohgiftplease.com/_api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__ohgiftplease__ReadFullDocsArticle",
"mcp__ohgiftplease__ReadFullDocsMethodSchema",
"mcp__ohgiftplease__BrowseWixRESTDocsMenu",
"mcp__ohgiftplease__SearchSiteApiDocs",
"mcp__ohgiftplease__GetBusinessDetails",
"mcp__ohgiftplease__SearchInSite"
],
"ask": [
"mcp__ohgiftplease__WixREADME",
"mcp__ohgiftplease__CallWixSiteAPI",
"mcp__ohgiftplease__GenerateVisitorToken"
],
"deny": [
"mcp__ohgiftplease__ExecuteWixAPI"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ohgiftplease. Review it before you use it.
Capability tags behind 8 rules
- mcp__ohgiftplease__ReadFullDocsArticle private-data
- mcp__ohgiftplease__ReadFullDocsMethodSchema private-data
- mcp__ohgiftplease__BrowseWixRESTDocsMenu private-data, untrusted-input
- mcp__ohgiftplease__CallWixSiteAPI outbound
- mcp__ohgiftplease__SearchSiteApiDocs private-data, untrusted-input
- mcp__ohgiftplease__GetBusinessDetails untrusted-input
- mcp__ohgiftplease__SearchInSite untrusted-input
- mcp__ohgiftplease__ExecuteWixAPI untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.racharmi/ohgiftplease/verify?hash=77635dfc761f4a5a31c87d1509d4b4b6718fbaa2c5a501860019d91db5ff509f" | jq -e '.changed == false'Pinned hash 77635dfc761f, from Nov 20, 2026, 09:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.racharmi/ohgiftplease/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.racharmi/ohgiftplease)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:45 UTC.
OhGiftPlease Gift Discovery MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the OhGiftPlease Gift Discovery MCP server safe?
- No scan can promise that. What its definitions show: 10 tools, 4 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the OhGiftPlease Gift Discovery MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: ExecuteWixAPI.
Can the OhGiftPlease Gift Discovery MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the OhGiftPlease Gift Discovery MCP server have?
- 10 tools: 1 destructive, 3 write, 6 read. ExecuteWixAPI, WixREADME, CallWixSiteAPI, GenerateVisitorToken, ReadFullDocsArticle, ReadFullDocsMethodSchema, BrowseWixRESTDocsMenu, SearchSiteApiDocs and 2 more.
Does the OhGiftPlease Gift Discovery MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the OhGiftPlease Gift Discovery MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): CallWixSiteAPI.
Has the OhGiftPlease Gift Discovery MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.