Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Assay Systems procurement register

REMOTE · ASSAY-SYSTEMS.COM

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

68 Trust /100

Last scanned (13 hours ago)

Scores higher than 58% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1116 tokens (~101/item across 11 items; 11 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 93% 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 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

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.

Changelog

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.

  • 18 Oct 26 68

    First indexed and scored.

Diagnostics

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 18 Oct 2026 · Probed https://assay-systems.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=assay-systems.com CN=WE1,O=Google Trust Services,C=US 21 Aug 2026 19 Nov 2026 ECDSA 256 ECDSA-SHA256 f4d47f5cb8e158fa0eb0fe953fb08828
SANs: assay-systems.com
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 assay-systems.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
assay-systems.com. absent 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://assay-systems.com/mcp Verified 200
http (plaintext) http://assay-systems.com/mcp HTTPS enforced 301 https://assay-systems.com/mcp
MCP tools · 11 exposed · ~1,037 tokens

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 →

Tool Tokens
assay_contract ~71

One contract or award record from the register.

NameTypeReqDescription
countrystringyesTwo-letter country code in lower case, e.g. ca, us, gb, ua. assay_countries lists them.
idstringyesRecord id as given by assay_search (the part after the country in the endpoint).

No output schema declared.

No examples provided.

assay_countries ~28

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

assay_ending ~140

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

NameTypeReqDescription
beforestring–YYYY-MM-DD: only contracts ending before this day.
countrystringyesTwo-letter country code in lower case, e.g. ca, us, gb, ua. assay_countries lists them.
linestringyesLine id from assay_line or assay_search.
pageinteger–Page of the result list (default 1).

No output schema declared.

No examples provided.

assay_line ~81

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

NameTypeReqDescription
countrystringyesTwo-letter country code in lower case, e.g. ca, us, gb, ua. assay_countries lists them.
idstringyesRecord id as given by assay_search (the part after the country in the endpoint).

No output schema declared.

No examples provided.

assay_line_contracts ~162

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

NameTypeReqDescription
buyerstring–Words of the buyer's name.
countrystringyesTwo-letter country code in lower case, e.g. ca, us, gb, ua. assay_countries lists them.
ends_beforestring–YYYY-MM-DD: only contracts ending before this day.
idstringyesRecord id as given by assay_search (the part after the country in the endpoint).
pageinteger–Page of the result list (default 1).

No output schema declared.

No examples provided.

assay_search ~86

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

NameTypeReqDescription
countrystring–Two-letter country code in lower case, e.g. ca, us, gb, ua. assay_countries lists them.
limitinteger––
qstringyesName or words, two letters or more.

No output schema declared.

No examples provided.

assay_solo ~145

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

NameTypeReqDescription
buyerstring–Words of the buyer's name.
countrystring–Two-letter country code in lower case, e.g. ca, us, gb, ua. assay_countries lists them.
kindstring––
pageinteger–Page of the result list (default 1).
supplierstring–Words of the supplier's name.

No output schema declared.

No examples provided.

assay_status ~20

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

assay_supplier ~84

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

NameTypeReqDescription
countrystringyesTwo-letter country code in lower case, e.g. ca, us, gb, ua. assay_countries lists them.
idstringyesRecord id as given by assay_search (the part after the country in the endpoint).

No output schema declared.

No examples provided.

assay_supplier_contracts ~160

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

NameTypeReqDescription
buyerstring–Words of the buyer's name.
countrystringyesTwo-letter country code in lower case, e.g. ca, us, gb, ua. assay_countries lists them.
ends_beforestring–YYYY-MM-DD: only contracts ending before this day.
idstringyesRecord id as given by assay_search (the part after the country in the endpoint).
pageinteger–Page of the result list (default 1).

No output schema declared.

No examples provided.

assay_uncontested ~60

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

NameTypeReqDescription
countrystring–Two-letter country code in lower case, e.g. ca, us, gb, ua. assay_countries lists them.

No output schema declared.

No examples provided.

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.

remote · assay-systems.com

# add to Claude Code
claude mcp add --transport http com-assay-systems-register 'https://assay-systems.com/mcp'
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.