# REGULARUS (remote · regularus.coniuncta.tech)

Fixed prices, document lists and report verification for EU cosmetic safety reports (CPSR).

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

## Components

- remote · `regularus.coniuncta.tech`: 71/100 (this document), [markdown](https://verifymcp.io/servers/tech-coniuncta-regularus-regularus/regularus.md), [page](https://verifymcp.io/servers/tech-coniuncta-regularus-regularus/regularus)

## Channel facts

- Endpoint: `https://regularus.coniuncta.tech/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-04.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 56/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 941 tokens (~313/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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.

## Install

### How do I install the REGULARUS MCP server?

REGULARUS is a hosted endpoint at https://regularus.coniuncta.tech/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 tech-coniuncta-regularus-regularus 'https://regularus.coniuncta.tech/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "tech-coniuncta-regularus-regularus": {
      "url": "https://regularus.coniuncta.tech/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tech-coniuncta-regularus-regularus": {
      "type": "http",
      "url": "https://regularus.coniuncta.tech/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tech-coniuncta-regularus-regularus]
url = "https://regularus.coniuncta.tech/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tech-coniuncta-regularus-regularus": {
      "type": "remote",
      "url": "https://regularus.coniuncta.tech/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tech-coniuncta-regularus-regularus --url 'https://regularus.coniuncta.tech/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tech-coniuncta-regularus-regularus:
    url: "https://regularus.coniuncta.tech/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tech-coniuncta-regularus-regularus": {
      "Transport": "http",
      "Url": "https://regularus.coniuncta.tech/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tech-coniuncta-regularus-regularus -t streamable-http -u 'https://regularus.coniuncta.tech/mcp'
```

### Other

```json
{
  "mcpServers": {
    "tech-coniuncta-regularus-regularus": {
      "type": "http",
      "url": "https://regularus.coniuncta.tech/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-02 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

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

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-18 (score 64, +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.

## MCP tools (3)

### `get_fixed_price` (~462 tokens)

Calculate fixed price

Calculate the price for a cosmetic product safety report (CPSR) by product type, number of recipes and varieties, markets, company seat, package and add-ons. Same calculation as the questionnaire on the website. Returns prices per package, what is included, what costs extra, assumptions and a confirmUrl for the user.

Input parameters:

- `claims` (string): Whether special claims are made (e.g. "vegan", "anti-wrinkle").
- `claims_review` (boolean): Review of advertising claims per variety (not with claims=no).
- `eu_representative` (boolean): We act as your responsible person in the EU (only with seat=de or eu, yearly price).
- `express` (boolean): Report in 5 instead of 10 working days, with a surcharge.
- `lang` (string): Language of the texts in the response and on the confirmation page (default en).
- `maker` (string): Who manufactures the products (does not change the price).
- `markets` (array): Where the products are sold (default EU).
- `package` (string): Package; without it all three are returned with a recommendation.
- `product_type` (array, required): Product type; several separated by commas, with recipes and varieties in the same order.
- `recipe_status` (string): How far the recipe is (does not change the price).
- `recipes` (array): Own recipes (base formulas) per product type (default 1).
- `responsible_person` (string): Only with seat=non_eu: us = we act as your responsible person in the EU (yearly price), self = you already have one.
- `seat` (string): Seat of the company (default de; determines VAT and the EU representative).
- `stability_test` (boolean): Stability test in our laboratory (products containing water only).
- `uk_documents` (boolean): Documents for Great Britain per variety (only with markets=UK).
- `urgency` (string): How urgent it is (does not change the price; faster with express=true).
- `varieties` (array): Total varieties per product type, base products included (e.g. one recipe with three fragrances: recipes=1, varieties=3). Default: same as recipes.

### `list_documents` (~211 tokens)

List required documents

List the documents needed for the safety report by product type, number of recipes and varieties, manufacturer and package (recipe with quantities, raw material data sheets, fragrance documents, stability test, GMP, packaging, label draft).

Input parameters:

- `claims_review` (boolean): Review of advertising claims per variety (not with claims=no).
- `lang` (string): Language of the texts in the response and on the confirmation page (default en).
- `maker` (string): Who manufactures the products (does not change the price).
- `package` (string): Package; without it all three are returned with a recommendation.
- `product_type` (array, required): Product type; several separated by commas, with recipes and varieties in the same order.
- `recipes` (array): Own recipes (base formulas) per product type (default 1).
- `varieties` (array): Total varieties per product type, base products included (e.g. one recipe with three fragrances: recipes=1, varieties=3). Default: same as recipes.

### `verify_report` (~159 tokens)

Verify a safety report

Check a signed REGULARUS safety report by the verification number printed below the signature and in the footer (16 characters, e.g. K7Q2-9XMV-3HPD-RW4T, also as QR code). Returns product and version as in the report, signing date, assessor with qualification, status (valid, superseded by a newer version, or withdrawn) and the SHA-256 hash of the PDF file. A number that is not found means the report does not come from REGULARUS. The sample number MUSTER returns an example.

Input parameters:

- `lang` (string): Language of the verification page link (default de).
- `number` (string, required): Verification number from the report, with or without hyphens.

## Diagnostics

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

## Score history

- 2026-11-04: 71
- 2026-11-03: 71
- 2026-11-02: 71
- 2026-11-01: 70
- 2026-10-31: 70
- 2026-10-30: 69
- 2026-10-29: 69
- 2026-10-28: 68
- 2026-10-27: 68
- 2026-10-26: 67
- 2026-10-25: 67
- 2026-10-24: 66
- 2026-10-23: 66
- 2026-10-22: 65
- 2026-10-21: 65
- 2026-10-20: 64
- 2026-10-19: 64
- 2026-10-18: 64
- 2026-10-17: 63
- 2026-10-16: 63
- 2026-10-15: 62
- 2026-10-14: 62

## Common questions

### What is the REGULARUS MCP server?

REGULARUS is an MCP server listed in the public MCP registry as tech.coniuncta.regularus/regularus. Fixed prices, document lists and report verification for EU cosmetic safety reports (CPSR). This page covers its hosted endpoint (https://regularus.coniuncta.tech/mcp).

### Is the REGULARUS MCP server safe to use?

REGULARUS 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 REGULARUS MCP server expose?

REGULARUS exposes 3 tools: get_fixed_price, list_documents, verify_report. Their descriptions and schemas cost roughly 832 tokens of context every time the server is loaded.

### Does the REGULARUS MCP server require authentication?

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

### Is the REGULARUS MCP server still maintained?

REGULARUS is still listed as active in the MCP registry. We last reached this channel on 4 November 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://regularus.coniuncta.tech/mcp
- Website: https://regularus.coniuncta.tech/
- Changelog RSS feed: https://verifymcp.io/servers/tech-coniuncta-regularus-regularus/regularus.xml
- Changelog JSON feed: https://verifymcp.io/servers/tech-coniuncta-regularus-regularus/regularus.json
- HTML version of this page: https://verifymcp.io/servers/tech-coniuncta-regularus-regularus/regularus