EasyStore MCP by usefulapi
REMOTE · EASYSTORE.USEFULAPI.IO
Read EasyStore orders, products and customers; manage stock, fulfillments and customer records.
Available components
Last scanned (4 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 6 Nov 2026.
Category E-commerce
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Nov 26 −47
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- MCP protocol: fail → pass ▲ functional
- New prompt “check_variant_stock_across_locations” functional
- New prompt “find_a_customer_and_review_recent_orders” functional
- New prompt “reconcile_stock_after_a_physical_count” functional
- New prompt “review_paid_orders_waiting_to_ship” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.3.0 → 1.5.0 functional
- Server version: 1.2.0 → 1.3.0 functional
- Server version: 1.1.1 → 1.2.0 functional
- 30 Oct 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Probed https://easystore.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of easystore.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://easystore.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/easystore/ |
| http (plaintext) | http://easystore.usefulapi.io/mcp | Inconclusive | 302 | http://easystore.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
easystore_adjust_inventory_level Adjust inventory level ~143
WRITE. Add to or remove from the stock of one variant at one location by a relative amount (positive adds, negative removes; 0 is rejected). Not idempotent: repeating it changes the stock again. Omit location_id for the primary location. Needs write_products. PUT /api/4.0/inventory_levels/adjust.json.
| Name | Type | Req | Description |
|---|---|---|---|
| adjustment_quantity | integer | yes | Relative change: 5 adds 5, -5 removes 5. |
| location_id | integer | – | Location id (see easystore_list_locations). Default: the primary location. |
| variant_id | integer | yes | Variant id (see easystore_list_product_variants). |
No output schema declared.
No examples provided.
easystore_cancel_order Cancel order ~90
WRITE, hard to undo. Cancel an order, with an optional reason. Confirm the order id and number with the user first. Needs write_orders. POST /api/3.0/orders/{id}/cancel.json.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | yes | EasyStore order id (not the order number). |
| reason | string | – | Why the order is cancelled, e.g. Damaged item. |
No output schema declared.
No examples provided.
easystore_create_customer Create customer ~167
WRITE. Create a customer. Pass at least one of first_name, last_name, email or phone. Not idempotent. Needs write_customers. POST /api/3.0/customers.json.
| Name | Type | Req | Description |
|---|---|---|---|
| birthdate | string | – | yyyy-mm-dd. |
| code | string | – | Your own customer code. |
| country_code | string | – | Two-letter country code, e.g. MY. |
| string | – | Email (unique per store). | |
| first_name | string | – | First name. |
| gender | string | – | Gender. |
| groups | array | – | Group names to assign, e.g. ["VIP"]. |
| last_name | string | – | Last name. |
| phone | string | – | Phone number, e.g. +60192233445. |
No output schema declared.
No examples provided.
easystore_create_fulfillment Create fulfillment ~180
WRITE. Mark an order (or some of its line items) as shipped, with tracking details. Not idempotent: calling it twice creates two fulfillments. With notify_customer true the customer is emailed. Needs write_fulfillments. POST /api/3.0/orders/{id}/fulfillments.json.
| Name | Type | Req | Description |
|---|---|---|---|
| line_items | array | – | Only these line items and quantities; omit to fulfill the whole order. |
| message | string | – | Note about this fulfillment. |
| notify_customer | boolean | – | Email the customer (default false). |
| order_id | integer | yes | EasyStore order id. |
| status | string | – | Shipment status. |
| tracking_company | string | – | Courier name, e.g. DHL. |
| tracking_number | string | – | Tracking number. |
| tracking_url | string | – | Tracking page URL. |
No output schema declared.
No examples provided.
easystore_get_collection Get collection ~45
One collection by id. Needs read_products. GET /api/3.0/collections/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| collection_id | integer | yes | EasyStore collection id. |
No output schema declared.
No examples provided.
easystore_get_customer Get customer ~72
One customer by id. Add fields=points,membership for loyalty data. Needs read_customers. GET /api/3.0/customers/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | integer | yes | EasyStore customer id. |
| fields | string | – | Extra sections, e.g. points,membership. |
No output schema declared.
No examples provided.
easystore_get_customer_points Get customer points ~51
The loyalty points balance of one customer. Needs read_customers. GET /api/3.0/customers/{id}/points.json.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | integer | yes | EasyStore customer id. |
No output schema declared.
No examples provided.
easystore_get_order Get order ~107
One order by id. Ask for extra sections with fields: items, addresses, transactions, fulfillments, refunds, taxes, customer, shipping_fees, discounts, points, cancellation, note_attributes. Needs read_orders. GET /api/3.0/orders/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | Comma-separated extra sections, e.g. items,addresses,fulfillments. |
| order_id | integer | yes | EasyStore order id (not the order number). |
No output schema declared.
No examples provided.
easystore_get_product Get product ~53
One product by id with its variants, options, images and collections. Needs read_products. GET /api/3.0/products/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | integer | yes | EasyStore product id. |
No output schema declared.
No examples provided.
easystore_get_store Get store ~55
The store behind this access token: name, contact emails, easystore domain, plan, locale, country, time zone, currencies and locations. Needs no API access scope. GET /api/3.0/store.json.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
easystore_list_articles List blog articles ~84
List blog articles. Needs read_content. GET /api/3.0/articles.json.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| visibility | string | – | Only published or unpublished articles. |
No output schema declared.
No examples provided.
easystore_list_blogs List blogs ~88
List the store's blogs. Needs read_content. GET /api/3.0/blogs.json.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| visibility | string | – | Only published or unpublished blogs. |
No output schema declared.
No examples provided.
easystore_list_checkouts List checkouts ~102
List checkouts (carts in progress or abandoned). Cart tokens are not returned. Needs read_orders. GET /api/3.0/checkouts.json.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-50 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| since_id | integer | – | Start at this checkout id (inclusive). |
No output schema declared.
No examples provided.
easystore_list_collections List collections ~143
List product collections. Needs read_products. GET /api/3.0/collections.json.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | string | – | Only these collection ids, comma-separated. |
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| since_id | integer | – | Start at this collection id (inclusive). |
| sort | string | – | Sort as field.asc or field.desc, e.g. id.asc (a stable order for paging through everything). |
| visibility | boolean | – | true = only published collections. |
No output schema declared.
No examples provided.
easystore_list_customer_addresses List customer addresses ~94
The saved addresses of one customer. Needs read_customers. GET /api/3.0/customers/{id}/addresses.json.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | integer | yes | EasyStore customer id. |
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
easystore_list_customer_groups List customer groups ~34
List customer groups (for example VIP). Needs read_customers. GET /api/3.0/groups.json.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
easystore_list_customers List customers ~353
List customers with contact details, order count, total spent, groups and store credit. Search by name or email with query. Needs read_customers. GET /api/3.0/customers.json.
| Name | Type | Req | Description |
|---|---|---|---|
| created_at_max | string | – | ISO 8601 date or date-time, e.g. 2026-10-01 or 2026-10-01T00:00:00+08:00. |
| created_at_min | string | – | ISO 8601 date or date-time, e.g. 2026-10-01 or 2026-10-01T00:00:00+08:00. |
| ids | string | – | Only these customer ids, comma-separated. |
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| query | string | – | Match on first name, last name or email. |
| since_id | integer | – | Start at this customer id (inclusive). |
| sort | string | – | Sort as field.asc or field.desc, e.g. id.asc (a stable order for paging through everything). |
| updated_at_max | string | – | ISO 8601 date or date-time, e.g. 2026-10-01 or 2026-10-01T00:00:00+08:00. |
| updated_at_min | string | – | ISO 8601 date or date-time, e.g. 2026-10-01 or 2026-10-01T00:00:00+08:00. |
No output schema declared.
No examples provided.
easystore_list_inventory_levels List inventory levels ~141
Stock per variant per location: available (inventory_quantity), committed, incoming and reserved. Pass variant_ids or location_ids (at least one is required). Needs read_products. GET /api/4.0/inventory_levels.json.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| location_ids | string | – | Location ids, comma-separated (see easystore_list_locations). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| variant_ids | string | – | Variant ids, comma-separated (see easystore_list_product_variants). |
No output schema declared.
No examples provided.
easystore_list_locations List locations ~100
The store's stock and pickup locations (warehouses, outlets) with address, phone, is_primary and pickup settings. Use the ids for inventory levels. Needs read_locations. GET /api/3.0/locations.json.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
easystore_list_order_fulfillments List order fulfillments ~65
The fulfillments (shipments with tracking details and status) of one order. Needs read_fulfillments. GET /api/3.0/orders/{id}/fulfillments.json.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | yes | EasyStore order id. |
No output schema declared.
No examples provided.
easystore_list_order_transactions List order transactions ~54
The payment transactions of one order (gateway, amount, status). Needs read_orders. GET /api/3.0/orders/{id}/transactions.json.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | yes | EasyStore order id. |
No output schema declared.
No examples provided.
easystore_list_orders List orders ~370
List orders from every sales channel with customer, items, totals, payment and fulfillment status. Filter by payment or fulfillment status, customer, or dates (store time zone). Needs read_orders. GET /api/3.0/orders.json.
| Name | Type | Req | Description |
|---|---|---|---|
| created_at_max | string | – | yyyy-mm-dd or yyyy-mm-dd hh:mm:ss, read in the store's own time zone. |
| created_at_min | string | – | yyyy-mm-dd or yyyy-mm-dd hh:mm:ss, read in the store's own time zone. |
| customer_id | integer | – | Only this customer's orders. |
| financial_status | string | – | Payment status. |
| fulfillment_status | string | – | Shipping status. |
| ids | string | – | Only these order ids, comma-separated. |
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| processed_at_max | string | – | yyyy-mm-dd or yyyy-mm-dd hh:mm:ss, read in the store's own time zone. |
| processed_at_min | string | – | yyyy-mm-dd or yyyy-mm-dd hh:mm:ss, read in the store's own time zone. |
| since_id | integer | – | Start at this order id (inclusive: id >= since_id). Use with sort=id.asc. |
| sort | string | – | Sort as field.asc or field.desc, e.g. id.asc (a stable order for paging through everything). |
| updated_at_max | string | – | yyyy-mm-dd or yyyy-mm-dd hh:mm:ss, read in the store's own time zone. |
| updated_at_min | string | – | yyyy-mm-dd or yyyy-mm-dd hh:mm:ss, read in the store's own time zone. |
No output schema declared.
No examples provided.
easystore_list_pages List pages ~75
List the store's content pages. Needs read_content. GET /api/3.0/pages.json.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
easystore_list_product_variants List product variants ~61
The variants of one product (price, SKU, barcode, stock, weight, enabled flag). Needs read_products. GET /api/3.0/products/{id}/variants.json.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | integer | yes | EasyStore product id. |
No output schema declared.
No examples provided.
easystore_list_products List products ~333
List products with variants, prices, SKUs, stock, images and collections. Filter by collection, SKU, published status or dates. Needs read_products. GET /api/3.0/products.json.
| Name | Type | Req | Description |
|---|---|---|---|
| collection_ids | string | – | Only products in these collection ids, comma-separated, e.g. 2311217,2311218. |
| created_at_max | string | – | yyyy-mm-dd or yyyy-mm-dd hh:mm:ss, read in the store's own time zone. |
| created_at_min | string | – | yyyy-mm-dd or yyyy-mm-dd hh:mm:ss, read in the store's own time zone. |
| is_bundle | boolean | – | true = only bundle products, false = no bundle products. |
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| since_id | integer | – | Start at this product id (inclusive: id >= since_id). |
| skus | string | – | Only products with these SKUs, comma-separated. |
| sort | string | – | Sort as field.asc or field.desc, e.g. id.asc (a stable order for paging through everything). |
| updated_at_max | string | – | yyyy-mm-dd or yyyy-mm-dd hh:mm:ss, read in the store's own time zone. |
| updated_at_min | string | – | yyyy-mm-dd or yyyy-mm-dd hh:mm:ss, read in the store's own time zone. |
| visibility | string | – | Only published or only unpublished products. |
No output schema declared.
No examples provided.
easystore_search_customers Search customers ~128
Find customers by exact email, phone number or customer code. Pass at least one. Needs read_customers. GET /api/3.0/customers/search.json.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | Customer code. |
| string | – | Exact email address. | |
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| phone | string | – | Phone number as stored, e.g. 601110768827. |
No output schema declared.
No examples provided.
easystore_set_inventory_level Set inventory level ~129
WRITE. Set the stock of one variant at one location to an exact number (quantity 0 or more). Omit location_id for the primary location. Overwrites the current quantity; use easystore_adjust_inventory_level for a relative change. Needs write_products. PUT /api/4.0/inventory_levels/set.json.
| Name | Type | Req | Description |
|---|---|---|---|
| location_id | integer | – | Location id (see easystore_list_locations). Default: the primary location. |
| quantity | integer | yes | The exact available quantity to set. |
| variant_id | integer | yes | Variant id (see easystore_list_product_variants). |
No output schema declared.
No examples provided.
easystore_update_customer Update customer ~172
WRITE. Change fields of an existing customer; only the fields you pass change. Needs write_customers. PUT /api/3.0/customers/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| birthdate | string | – | yyyy-mm-dd. |
| code | string | – | Your own customer code. |
| country_code | string | – | Two-letter country code, e.g. MY. |
| customer_id | integer | yes | EasyStore customer id. |
| string | – | Email (unique per store). | |
| first_name | string | – | First name. |
| gender | string | – | Gender. |
| groups | array | – | Group names to assign, e.g. ["VIP"]. |
| last_name | string | – | Last name. |
| phone | string | – | Phone number, e.g. +60192233445. |
No output schema declared.
No examples provided.
easystore_update_variant Update variant ~159
WRITE. Change one variant's price, compare-at price, cost price, SKU, barcode or enabled flag. Only the fields you pass change. To change stock use the inventory tools. Needs write_products. PUT /api/3.0/products/{product_id}/variants.json.
| Name | Type | Req | Description |
|---|---|---|---|
| barcode | string | – | Barcode. |
| compare_at_price | number | – | Original price shown struck through. |
| cost_price | number | – | Cost price. |
| is_enabled | boolean | – | Whether the variant can be sold. |
| price | number | – | Selling price in the store's primary currency. |
| product_id | integer | yes | The product the variant belongs to. |
| sku | string | – | SKU. |
| variant_id | integer | yes | Variant id. |
No output schema declared.
No examples provided.
How do I install the EasyStore MCP by usefulapi server?
EasyStore MCP by usefulapi is a hosted endpoint at https://easystore.usefulapi.io/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.
remote · easystore.usefulapi.io
claude mcp add --transport http io-usefulapi-easystore 'https://easystore.usefulapi.io/mcp'
What is the EasyStore MCP by usefulapi server?
EasyStore MCP by usefulapi is listed in the public MCP registry as io.usefulapi/easystore. Read EasyStore orders, products and customers; manage stock, fulfillments and customer records. This page covers its hosted endpoint (https://easystore.usefulapi.io/mcp).
Is the EasyStore MCP by usefulapi server safe to use?
EasyStore MCP by usefulapi scores 18 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 EasyStore MCP by usefulapi server expose?
EasyStore MCP by usefulapi exposes 29 tools: easystore_get_store, easystore_list_locations, easystore_list_products, easystore_get_product, easystore_list_product_variants, and 24 more. Their descriptions and schemas cost roughly 3,648 tokens of context every time the server is loaded.
Does the EasyStore MCP by usefulapi server require authentication?
Its publisher declares no required credentials for EasyStore MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the EasyStore MCP by usefulapi server still maintained?
EasyStore MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the EasyStore MCP by usefulapi server?
VerifyMCP ran 4 checks on EasyStore MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about EasyStore MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.