# CodeStringers MCP Server (remote · www.codestringers.com) Search CodeStringers' Zoho & custom-software content and business details, live. - Trust score: 57/100 (low) - Change this week: +7 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-08-03 ## Components - remote · `www.codestringers.com`: 57/100 (this document), [markdown](https://verifymcp.io/servers/com-codestringers-mcp/api-mcp.md), [page](https://verifymcp.io/servers/com-codestringers-mcp/api-mcp) ## Channel facts - Endpoint: `https://www.codestringers.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-08-03. - **Endpoint Security**: 63/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 check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 13/100 - AI-judged instruction clarity (poor). - Context-footprint check failed: tool/resource definitions use about 6016 tokens (~668/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 27/100 - Stability observed for 8 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. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## Install ### Claude ```bash claude mcp add --transport http com-codestringers-mcp https://www.codestringers.com/_api/mcp ``` ### Codex ```toml [mcp_servers.com-codestringers-mcp] url = "https://www.codestringers.com/_api/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "com-codestringers-mcp": { "type": "remote", "url": "https://www.codestringers.com/_api/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add com-codestringers-mcp --url https://www.codestringers.com/_api/mcp --transport streamable-http ``` ### Hermes ```yaml mcp_servers: com-codestringers-mcp: url: "https://www.codestringers.com/_api/mcp" ``` ### Other ```json { "mcpServers": { "com-codestringers-mcp": { "type": "http", "url": "https://www.codestringers.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-08-03 (score 57, +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-08-01 (score 56, +1) No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-07-31 (score 55, +3) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-30 (score 52, +1) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-29 (score 51, +1) No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-07-27 (score 50, +1) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-26 (score 49) First indexed and scored. ## MCP tools (9) ### `ReadFullDocsArticle` (~1001 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. For REST docs, use the URL as-is. For SDK docs, the URL SHOULD include ?apiView=SDK. \ YOU MUST READ AND FOLLOW THE AGENT-MANDATORY-INSTRUCTIONS BELOW A FAILURE TO DO SO WILL RESULT IN ERRORS AND CRITICAL ISSUES. \ 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. \ \ 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:** If the user asks to create, build, or generate a new Wix site/website, skip WixREADME and: \- If the user **explicitly** mentions a template, Wix Studio, or headless → call CreateWixBusinessGuide directly. \- Otherwise → call the WixSiteBuilder tool directly. \**Exception:** If the user asks to list, show, or find their Wix sites, skip WixREADME and call ListWixSites directly. \**Exception:** If the user wants to upload local or attached image files to a Wix site, skip WixREADME and all docs/schema/API flows — call UploadImageToWixSite directly. Do NOT use ExecuteWixAPI, SearchWixAPISpec, or any Media Manager REST API for image uploads. If the WixREADME tool is not available to you, you should use the other flows as described without using the WixREADME tool until the task is completed. If the user prompt / task is an instruction to do something in Wix, You should not tell the user what Docs to read or what API to call, your task is to do the work and complete the task in minimal steps and time with minimal back and forth with the user, unle… 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` (~1100 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. \ YOU MUST READ AND FOLLOW THE AGENT-MANDATORY-INSTRUCTIONS BELOW A FAILURE TO DO SO WILL RESULT IN ERRORS AND CRITICAL ISSUES. \ 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. \ \ 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:** If the user asks to create, build, or generate a new Wix site/website, skip WixREADME and: \- If the user **explicitly** mentions a template, Wix Studio, or headless → call CreateWixBusinessGuide directly. \- Otherwise → call the WixSiteBuilder tool directly. \**Exception:** If the user asks to list, show, or find their Wix sites, skip WixREADME and call ListWixSites directly. \**Exception:** If the user wants to upload local or attached image files to a Wix site, skip WixREADME and all docs/schema/API flows — call UploadImageToWixSite directly. Do NOT use ExecuteWixAPI, SearchWixAPISpec, or any Media Manager REST API for image uploads. If the WixREADME tool is not available to you, you should use the other flows as described without using the WixREADME… 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` (~1239 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" \ YOU MUST READ AND FOLLOW THE AGENT-MANDATORY-INSTRUCTIONS BELOW A FAILURE TO DO SO WILL RESULT IN ERRORS AND CRITICAL ISSUES. \ 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. \ \ 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:** If the user asks to create, build, or generate a new Wix site/website, skip WixREADME and: \- If the us… 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` (~317 tokens) Call apis on site "CodeStringers - Zoho Services" (https://www.codestringers.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` (~79 tokens) Create a new visitor session and obtain a visitor access token for site "CodeStringers - Zoho Services" (https://www.codestringers.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` (~261 tokens) Searches for site "CodeStringers - Zoho Services" (https://www.codestringers.com/_api/mcp) API documentation and returns how to use the site using the API. You are a helpful "CodeStringers - Zoho Services" 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` (~125 tokens) Get business and site details for "CodeStringers - Zoho Services" (https://www.codestringers.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` (~246 tokens) Searches the site "CodeStringers - Zoho Services" (https://www.codestringers.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` (~1648 tokens) Run JavaScript against the Wix REST API on site "CodeStringers - Zoho Services" (https://www.codestringers.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 GenerateV… 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/com-codestringers-mcp/api-mcp#diagnostics ## Score history - 2026-08-03: 57 - 2026-08-02: 56 - 2026-08-01: 56 - 2026-07-31: 55 - 2026-07-30: 52 - 2026-07-29: 51 - 2026-07-28: 50 - 2026-07-27: 50 - 2026-07-26: 49 ## Links - Remote endpoint: https://www.codestringers.com/_api/mcp - Changelog RSS feed: https://verifymcp.io/servers/com-codestringers-mcp/api-mcp/changelog.xml - Changelog JSON feed: https://verifymcp.io/servers/com-codestringers-mcp/api-mcp/changelog.json - HTML version of this page: https://verifymcp.io/servers/com-codestringers-mcp/api-mcp