# SharpSyn (remote · sharpsyn.com)

Fine chemicals sourcing: compounds by name or CAS, suppliers, price ranges, quote links. No key.

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `sharpsyn.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-sharpsyn-public/sharpsyn.md), [page](https://verifymcp.io/servers/com-sharpsyn-public/sharpsyn)

## Channel facts

- Endpoint: `https://sharpsyn.com/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-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 64/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (33% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-sharpsyn-public 'https://sharpsyn.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-sharpsyn-public": {
      "url": "https://sharpsyn.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-sharpsyn-public": {
      "type": "http",
      "url": "https://sharpsyn.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-sharpsyn-public]
url = "https://sharpsyn.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-sharpsyn-public": {
      "type": "remote",
      "url": "https://sharpsyn.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-sharpsyn-public --url 'https://sharpsyn.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-sharpsyn-public:
    url: "https://sharpsyn.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-sharpsyn-public": {
      "Transport": "http",
      "Url": "https://sharpsyn.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-sharpsyn-public -t streamable-http -u 'https://sharpsyn.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-sharpsyn-public": {
      "type": "http",
      "url": "https://sharpsyn.com/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-11-04 (score 71, +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-11-02 (score 70, +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-10-31 (score 69, +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.

### 2026-10-30 (score 68, 0)

- [functional regression] Tool coverage: 50% → 33%
- [functional regression] Schema quality: pass → fail
- [functional] New tool “value_chain”
- [functional] New tool “where_is_it_made”

### 2026-10-28 (score 68, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-27 (score 67)

First indexed and scored.

## MCP tools (6)

### `search_compounds` (~78 tokens)

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.

Input parameters:

- `limit` (integer)
- `query` (string, required)

Output parameters:

- `result` (array)

### `get_compound` (~127 tokens)

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.

Input parameters:

- `identifier` (string, required)

### `list_suppliers` (~79 tokens)

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.

Input parameters:

- `compound` (string)
- `country` (string)

Output parameters:

- `result` (array)

### `request_quote_link` (~65 tokens)

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.

Input parameters:

- `identifier` (string, required)

### `where_is_it_made` (~232 tokens)

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.

Input parameters:

- `identifier` (string, required)
- `include_inactive` (boolean)

### `value_chain` (~94 tokens)

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.

Input parameters:

- `depth` (integer)
- `direction` (string)
- `identifier` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-sharpsyn-public/sharpsyn#diagnostics

## Score history

- 2026-11-05: 71
- 2026-11-04: 71
- 2026-11-03: 70
- 2026-11-02: 70
- 2026-11-01: 69
- 2026-10-31: 69
- 2026-10-30: 68
- 2026-10-29: 68
- 2026-10-28: 68
- 2026-10-27: 67

## Common questions

### 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.

## Links

- Remote endpoint: https://sharpsyn.com/mcp
- Website: https://sharpsyn.com/ai
- Changelog RSS feed: https://verifymcp.io/servers/com-sharpsyn-public/sharpsyn.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-sharpsyn-public/sharpsyn/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-sharpsyn-public/sharpsyn.json
- HTML version of this page: https://verifymcp.io/servers/com-sharpsyn-public/sharpsyn