CacheBy
REMOTE · API.CACHEBY.COM · 2 COMPONENTS
Search lab reagents, antibodies and supplies sold in Korea by name, brand, part no. or CAS (KRW).
Available components
Last scanned (22 hours ago)
Scores higher than 72% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Health and Science
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 Security91
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server, and every tool looks verifiably read-only (it declares readOnlyHint: true, starts its name with a read verb and describes no write), so an anonymous caller can read but cannot change anything. We can't see whether a tool returns data specific to one caller, so keep any per-user data behind authorisation. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 501 tokens (~100/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 21 Nov 26 +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.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 16 Nov 26 76
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 21 Nov 2026 · Probed https://api.cacheby.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cacheby.com | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 26 Aug 2026 | 11 Mar 2027 | RSA 2048 | SHA256-RSA | 7c951fff43f10af1a12c8cc36e34bed |
| SANs: cacheby.com, *.cacheby.com | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.cacheby.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| cacheby.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.cacheby.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.cacheby.com/mcp | HTTPS enforced | 301 | https://api.cacheby.com/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 →
compare_reagent_prices Compare reagent prices ~69
Batch-compare a reagent purchase list against CacheBy prices. Each item needs a CAS number; optionally pass the price you currently pay (KRW) to get the price difference against CacheBy's cheapest exact match. Useful for quoting an entire experiment's materials.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
No output schema declared.
No examples provided.
get_similar_products Similar products ~62
Get products similar to a given CacheBy product (vector similarity). Pass a product id from search_products results.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 10) |
| productId | string | yes | Product id (UUID) from search_products results |
No output schema declared.
No examples provided.
get_substitutes Find substitutes ~98
Find substitute products on CacheBy for a reagent by CAS number — same substance from other brands/specs, sorted by price ascending. Use when a product is out of stock or to find a cheaper equivalent. To get a product page URL, call search_products with the partNumber.
| Name | Type | Req | Description |
|---|---|---|---|
| casNumber | string | yes | CAS registry number of the reagent |
| excludeProductId | string | – | Product id to exclude (the one being replaced) |
No output schema declared.
No examples provided.
search_by_cas Search by CAS numbers ~74
Look up CacheBy products for multiple CAS registry numbers at once (e.g. from a paper's materials list). Returns matching products per CAS number with prices in KRW.
| Name | Type | Req | Description |
|---|---|---|---|
| casNumbers | array | yes | CAS registry numbers, e.g. ["67-68-5", "7647-14-5"] |
No output schema declared.
No examples provided.
search_products Search products ~107
Search lab reagents and research supplies on CacheBy (Korean B2B marketplace for researchers). Query can be a product name (Korean or English), brand, part number, or CAS number. Returns up to 24 products per page with prices in KRW and a product page URL.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (24 results per page, default 1) |
| query | string | yes | Search keyword: product name, brand, part number, or CAS number |
No output schema declared.
No examples provided.
How do I install the CacheBy MCP server?
CacheBy is a hosted endpoint at https://api.cacheby.com/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 · api.cacheby.com
claude mcp add --transport http com-cacheby-search 'https://api.cacheby.com/mcp'
What is the CacheBy MCP server?
CacheBy is an MCP server listed in the public MCP registry as com.cacheby/search. Search lab reagents, antibodies and supplies sold in Korea by name, brand, part no. or CAS (KRW). This page covers its hosted endpoint (https://api.cacheby.com/mcp).
Is the CacheBy MCP server safe to use?
CacheBy scores 78 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 CacheBy MCP server expose?
CacheBy exposes 5 tools: search_products, search_by_cas, compare_reagent_prices, get_substitutes, get_similar_products. Their descriptions and schemas cost roughly 410 tokens of context every time the server is loaded.
Does the CacheBy MCP server require authentication?
No. We connected to CacheBy without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CacheBy MCP server still maintained?
CacheBy is still listed as active in the MCP registry. We last reached this channel on 21 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 CacheBy MCP server?
VerifyMCP ran 13 checks on CacheBy, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.