SharpSyn
REMOTE · SHARPSYN.COM
Fine chemicals sourcing: compounds by name or CAS, suppliers, price ranges, quote links. No key.
Available components
Last scanned (10 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 5 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 Security74
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 787 tokens (~131/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (33% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 0
- Tool coverage: 50% → 33% ▼ functional
- Schema quality: pass → fail ▼ functional
- New tool “value_chain” functional
- New tool “where_is_it_made” functional
- 28 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 27 Oct 26 67
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 5 Nov 2026 · Probed https://sharpsyn.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sharpsyn.com | CN=YE2,O=Let's Encrypt,C=US | 23 Oct 2026 | 21 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6380f9b1369c823889fe798e8fc03ac7290 |
| SANs: *.sharpsyn.com, sharpsyn.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sharpsyn.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| sharpsyn.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://sharpsyn.com/mcp | Verified | 200 | |
| http (plaintext) | http://sharpsyn.com/mcp | HTTPS enforced | 301 | https://sharpsyn.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 →
get_compound ~127
Everything SharpSyn publishes about one compound, given its CAS number, InChIKey or name: identifiers, structure (SMILES, InChI), number of verified suppliers with regions, grades and lead times, price range per kg with its confidence label and data date, the cradle-to-gate carbon footprint with tier, source and uncertainty, and the page URL to cite. If the compound has no public page, says so and gives a link where the user can still ask suppliers for it.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | – |
No output schema declared.
No examples provided.
list_suppliers ~79
Suppliers listed publicly on SharpSyn (companies that asked to be listed), optionally only those in one country or offering one compound (CAS, InChIKey or name). Returns company name, country, website, number of public listings and the profile URL.
| Name | Type | Req | Description |
|---|---|---|---|
| compound | string | – | – |
| country | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
request_quote_link ~65
A link the user opens to ask SharpSyn's suppliers for a quote on a compound (CAS number, InChIKey or name). Nothing is sent by calling this: the user fills in quantities and sends the request themselves.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | – |
No output schema declared.
No examples provided.
search_compounds ~78
Find compounds on SharpSyn by name, synonym, CAS number, InChIKey or molecular formula. Returns name, CAS, InChIKey, page URL and a summary of suppliers, price and carbon footprint for each match, best matches first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
value_chain ~94
What a compound is made from (direction 'up', its precursors) or what it is used to make ('down', derived products), following main industrial routes for `depth` steps (1 to 4). Each entry has its name, CAS and page URL where SharpSyn has one.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | – |
| direction | string | – | – |
| identifier | string | yes | – |
No output schema declared.
No examples provided.
where_is_it_made ~232
Where a compound is produced, from the SharpSyn Chemical World Map: the known production sites (name, operator, country, coordinates), how they spread over countries (share per country, single-site warning), the confidence and source of each entry, and the page and map links to cite. Site products from public research are estimates; operators marked 'unclaimed' have profiles built from public sources, not managed by them. Each site has the status of the line (operating, closure_announced, idle, planned, under_construction, closed, with dates), the operator of that line and its capacity (t/a with basis, year and reference substance). By default only lines producing now; include_inactive adds the rest. Shares per country by site count and by capacity, and the coverage: how many sites are known, how many with capacity, and what share of world production that is where the world production is on record.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | – |
| include_inactive | boolean | – | – |
No output schema declared.
No examples provided.
How do I install the SharpSyn MCP server?
SharpSyn is a hosted endpoint at https://sharpsyn.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 · sharpsyn.com
claude mcp add --transport http com-sharpsyn-public 'https://sharpsyn.com/mcp'
What is the SharpSyn MCP server?
SharpSyn is an MCP server listed in the public MCP registry as com.sharpsyn/public. Fine chemicals sourcing: compounds by name or CAS, suppliers, price ranges, quote links. No key. This page covers its hosted endpoint (https://sharpsyn.com/mcp).
Is the SharpSyn MCP server safe to use?
SharpSyn scores 71 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 SharpSyn MCP server expose?
SharpSyn exposes 6 tools: search_compounds, get_compound, list_suppliers, request_quote_link, where_is_it_made, value_chain. Their descriptions and schemas cost roughly 675 tokens of context every time the server is loaded.
Does the SharpSyn MCP server require authentication?
No. We connected to SharpSyn without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SharpSyn MCP server still maintained?
SharpSyn is still listed as active in the MCP registry. We last reached this channel on 5 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 SharpSyn MCP server?
VerifyMCP ran 13 checks on SharpSyn, 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.