# Assay Systems procurement register (remote · assay-systems.com)

Public procurement register, 50+ countries: suppliers, buyers, contracts, single-bid awards

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `assay-systems.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/com-assay-systems-register/assay-systems.md), [page](https://verifymcp.io/servers/com-assay-systems-register/assay-systems)

## Channel facts

- Endpoint: `https://assay-systems.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-10-18.

- **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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1116 tokens (~101/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 93% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Assay Systems procurement register MCP server?

Assay Systems procurement register is a hosted endpoint at https://assay-systems.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-assay-systems-register 'https://assay-systems.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-assay-systems-register": {
      "url": "https://assay-systems.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-assay-systems-register": {
      "type": "http",
      "url": "https://assay-systems.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-assay-systems-register]
url = "https://assay-systems.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-assay-systems-register --url 'https://assay-systems.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-assay-systems-register:
    url: "https://assay-systems.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-assay-systems-register": {
      "Transport": "http",
      "Url": "https://assay-systems.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-assay-systems-register -t streamable-http -u 'https://assay-systems.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-assay-systems-register": {
      "type": "http",
      "url": "https://assay-systems.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-10-18 (score 68)

First indexed and scored.

## MCP tools (11)

### `assay_countries` (~28 tokens)

Countries in the register

Countries covered by the Assay Systems procurement register, with the number of suppliers indexed in each.

### `assay_search` (~86 tokens)

Search suppliers

Search the register for a supplier (firm) by name or line of business. Returns names, countries, ids and endpoints.

Input parameters:

- `country` (string): Two-letter country code in lower case, e.g. ca, us, gb, ua. assay_countries lists them.
- `limit` (integer)
- `q` (string, required): Name or words, two letters or more.

### `assay_supplier` (~84 tokens)

Supplier record

One supplier's record: contracts won, buyers, totals, exclusions and grants, with the source and licence.

Input parameters:

- `country` (string, required): Two-letter country code in lower case, e.g. ca, us, gb, ua. assay_countries lists them.
- `id` (string, required): Record id as given by assay_search (the part after the country in the endpoint).

### `assay_line` (~81 tokens)

Line of business

A line of business (what is bought) in one country: buyers, suppliers and totals.

Input parameters:

- `country` (string, required): Two-letter country code in lower case, e.g. ca, us, gb, ua. assay_countries lists them.
- `id` (string, required): Record id as given by assay_search (the part after the country in the endpoint).

### `assay_contract` (~71 tokens)

Contract record

One contract or award record from the register.

Input parameters:

- `country` (string, required): Two-letter country code in lower case, e.g. ca, us, gb, ua. assay_countries lists them.
- `id` (string, required): Record id as given by assay_search (the part after the country in the endpoint).

### `assay_uncontested` (~60 tokens)

Uncontested awards (summary)

Summary of awards won without a rival (a single bid), for all countries or one country.

Input parameters:

- `country` (string): Two-letter country code in lower case, e.g. ca, us, gb, ua. assay_countries lists them.

### `assay_status` (~20 tokens)

Register freshness

When each source of the register was last read and built.

### `assay_supplier_contracts` (~160 tokens)

Supplier's contract rows

All contract rows of one supplier with the buying office's contact, end dates and amounts. Paid: USD 0.01 per call in USDC on Base via x402 (or an X-API-Key Commercial key on the MCP request).

Input parameters:

- `buyer` (string): Words of the buyer's name.
- `country` (string, required): Two-letter country code in lower case, e.g. ca, us, gb, ua. assay_countries lists them.
- `ends_before` (string): YYYY-MM-DD: only contracts ending before this day.
- `id` (string, required): Record id as given by assay_search (the part after the country in the endpoint).
- `page` (integer): Page of the result list (default 1).

### `assay_line_contracts` (~162 tokens)

Contract rows of a line

All contract rows of one line of business with the buying office's contact, end dates and amounts. Paid: USD 0.01 per call in USDC on Base via x402 (or an X-API-Key Commercial key on the MCP request).

Input parameters:

- `buyer` (string): Words of the buyer's name.
- `country` (string, required): Two-letter country code in lower case, e.g. ca, us, gb, ua. assay_countries lists them.
- `ends_before` (string): YYYY-MM-DD: only contracts ending before this day.
- `id` (string, required): Record id as given by assay_search (the part after the country in the endpoint).
- `page` (integer): Page of the result list (default 1).

### `assay_ending` (~140 tokens)

Contracts ending soon

Contracts of one line that are still running, soonest end first: the next tenders to come. Paid: USD 0.01 per call in USDC on Base via x402 (or an X-API-Key Commercial key on the MCP request).

Input parameters:

- `before` (string): YYYY-MM-DD: only contracts ending before this day.
- `country` (string, required): Two-letter country code in lower case, e.g. ca, us, gb, ua. assay_countries lists them.
- `line` (string, required): Line id from assay_line or assay_search.
- `page` (integer): Page of the result list (default 1).

### `assay_solo` (~145 tokens)

Awards won without a rival

Buyer × supplier pairs where the supplier won without a rival, locks and buyer shares; without country — the list of countries. Paid: USD 0.01 per call in USDC on Base via x402 (or an X-API-Key Commercial key on the MCP request).

Input parameters:

- `buyer` (string): Words of the buyer's name.
- `country` (string): Two-letter country code in lower case, e.g. ca, us, gb, ua. assay_countries lists them.
- `kind` (string)
- `page` (integer): Page of the result list (default 1).
- `supplier` (string): Words of the supplier's name.

## Diagnostics

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

## Score history

- 2026-10-18: 68

## Common questions

### What is the Assay Systems procurement register MCP server?

Assay Systems procurement register is an MCP server listed in the public MCP registry as com.assay-systems/register. Public procurement register, 50+ countries: suppliers, buyers, contracts, single-bid awards. This page covers its hosted endpoint (https://assay-systems.com/mcp).

### Is the Assay Systems procurement register MCP server safe to use?

Assay Systems procurement register scores 68 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 Assay Systems procurement register MCP server expose?

Assay Systems procurement register exposes 11 tools: assay_countries, assay_search, assay_supplier, assay_line, assay_contract, and 6 more. Their descriptions and schemas cost roughly 1,037 tokens of context every time the server is loaded.

### Does the Assay Systems procurement register MCP server require authentication?

No. We connected to Assay Systems procurement register without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Assay Systems procurement register MCP server still maintained?

Assay Systems procurement register is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://assay-systems.com/mcp
- Website: https://assay-systems.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-assay-systems-register/assay-systems.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-assay-systems-register/assay-systems.json
- HTML version of this page: https://verifymcp.io/servers/com-assay-systems-register/assay-systems