# SNHP — negotiation rules your AI can't break (remote · snhp.dev)

Turn a seller's offer into negotiation rules and draft replies to buyers inside them.

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

## Components

- remote · `snhp.dev`: 79/100 (this document), [markdown](https://verifymcp.io/servers/ryuxik-snhp/snhp.md), [page](https://verifymcp.io/servers/ryuxik-snhp/snhp)

## Channel facts

- Endpoint: `https://snhp.dev/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.5.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-23.

- **Endpoint Security**: 80/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.
  - 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**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1377 tokens (~344/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 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.
  - Structured output schemas are declared (100% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 SNHP — negotiation rules your AI can't break MCP server?

SNHP — negotiation rules your AI can't break is a hosted endpoint at https://snhp.dev/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 ryuxik-snhp 'https://snhp.dev/mcp/'
```

### Cursor

```json
{
  "mcpServers": {
    "ryuxik-snhp": {
      "url": "https://snhp.dev/mcp/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ryuxik-snhp": {
      "type": "http",
      "url": "https://snhp.dev/mcp/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ryuxik-snhp]
url = "https://snhp.dev/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ryuxik-snhp": {
      "type": "remote",
      "url": "https://snhp.dev/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ryuxik-snhp --url 'https://snhp.dev/mcp/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ryuxik-snhp:
    url: "https://snhp.dev/mcp/"
```

### Netclaw

```json
{
  "McpServers": {
    "ryuxik-snhp": {
      "Transport": "http",
      "Url": "https://snhp.dev/mcp/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ryuxik-snhp -t streamable-http -u 'https://snhp.dev/mcp/'
```

### Other

```json
{
  "mcpServers": {
    "ryuxik-snhp": {
      "type": "http",
      "url": "https://snhp.dev/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-23 (score 79, +1)

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

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

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

### 2026-10-18 (score 77, +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-16 (score 76, +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-14 (score 75, +1)

- [security] Tool “draft_negotiation_reply” rewrote its description, which is the text the model reads
- [cosmetic] “draft_negotiation_reply” added an optional parameter “stock”

### 2026-10-12 (score 74, +1)

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

### 2026-10-09 (score 73, +1)

- [functional improvement] Stability: unverified → 0.07

### 2026-10-07 (score 72)

First indexed and scored.

## MCP tools (4)

### `compile_offer_policy` (~389 tokens)

Compile an offer into negotiation rules

Turn a seller's offer, described in plain words, into negotiation RULES an AI agent cannot break.

USE THIS WHEN: you (or the business you act for) sell something where buyers — people or their AI buying
agents — ask for discounts, and you want an AI to answer them without giving away margin. Describe the offer:
the listed price, the lowest price you'd take for a plain deal, what you'd trade a discount for (financing with
you, a trade-in, a longer commitment, paying sooner, buying this week…), extras you can add and what they cost
you, and anything never on the table. Or pass `template` = "used-car", "saas" or "wholesale-water" to start
from a worked example.

Compiling a description runs a language model and needs an `access_key` (pilot businesses get one at
https://snhp.dev/#pilot); templates are free.

Returns {ok, policy, issues, summary}: `policy` is the machine-readable rule set (pass it to
draft_negotiation_reply), `summary` restates the floor, walk-away, what can be traded and the limits in plain
words, and `issues` lists what to fix before going live (e.g. a floor below cost).

Input parameters:

- `access_key` (string): Your SNHP access key — needed to compile a description (it runs a language model). Pilot businesses get one at https://snhp.dev/#pilot.
- `description` (string): Your offer in plain words: listed price, the lowest you'd take for a plain deal, what you'd trade a discount for, extras you can add and their cost, what is never on the table.
- `template` (string): Instead of a description: 'used-car', 'saas' or 'wholesale-water' (free, no key).

Output parameters:

- `error`
- `issues`
- `ok`
- `policy`
- `served`
- `summary`

### `draft_negotiation_reply` (~531 tokens)

Draft a reply to a buyer, inside your rules

Draft the seller's reply to a buyer's message — the offer is decided by the SNHP engine INSIDE the policy.

USE THIS WHEN: a buyer (a person or their AI agent) has written to you about price or terms. Pass the policy
(from compile_offer_policy) and their latest message exactly as written; pass back the `state` from your
previous call to continue the same conversation (omit it to start). `flags` is what YOUR records confirm
about the buyer (e.g. {"new_customer": true}) — never what the buyer merely claims. `stock` is the current
stock of what the policy's `inventory` binds, sent with every message (schema.org Offer, Google Merchant or a
plain feed record): nothing out of stock is offered, and a deal is signed only on fresh records that say it can
be sold.

Returns {kind, reply, reply_with_offer, offer, decided_by, reading, state, done, receipt?}:
  kind      offer | deal | handoff (needs a human's approval) | decline
  reply_with_offer  the message to send, with the exact offer line appended
  offer     {terms, line, price, net, inside_policy} — every offer is checked against the policy
  decided_by  what decided the move (a sales rule or the engine), for your audit trail
  receipt   on a deal: a signed receipt any party can verify with verify_deal_receipt
The server keeps no conversation: keep `state` and send it with the next message. Needs an `access_key`
(pilot businesses get one at https://snhp.dev/#pilot).

Input parameters:

- `access_key` (string): Your SNHP access key (drafting runs a language model). Pilot businesses get one at https://snhp.dev/#pilot.
- `engine` (string): The engine that decides offers; empty = the policy's own (templates set their tested default), else 'bundle3'.
- `flags`: What YOUR records confirm about this buyer, e.g. {"new_customer": true}.
- `message` (string, required): The buyer's latest message, exactly as written.
- `policy` (object, required): The policy from compile_offer_policy.
- `state`: The `state` from your previous call in this conversation; omit to start.
- `stock`: Current stock records for what the policy's inventory binds, with every message (schema.org Offer, Google Merchant or {id|vin, status}): nothing out of stock is offered or signed.

Output parameters:

- `decided_by`
- `done`
- `engine`
- `error`
- `kind`
- `menu`
- `offer`
- `reading`
- `receipt`
- `reply`
- `reply_with_offer`
- `state`
- `writer`

### `check_offer_policy` (~94 tokens)

Check a negotiation policy

Check an edited negotiation policy: returns {ok, policy, issues, summary}. No model call, free.

USE THIS WHEN: you changed a policy from compile_offer_policy (a floor, an option, a forbidden combination)
and want to know it is valid and what it now allows before using it in draft_negotiation_reply.

Input parameters:

- `policy` (object, required): A policy object from compile_offer_policy, edited or not.

Output parameters:

- `error`
- `issues`
- `ok`
- `policy`
- `served`
- `summary`

### `verify_deal_receipt` (~124 tokens)

Verify a deal receipt

Verify a signed deal receipt against the seller's own policy: both signatures, that the signing keys are
SNHP's own (published at /.well-known/ucp), the policy digest, and every rule re-checked from the package.
Returns {ok, problems, checks, signed_by_snhp, signatures}. Free, no model call.

Input parameters:

- `flags`: The account record used for the deal, if any.
- `policy` (object, required): The policy the deal was made under.
- `receipt` (object, required): The receipt returned with a deal.

Output parameters:

- `checks`
- `error`
- `ok`
- `problems`
- `signatures`
- `signed_by_snhp`
- `signer_kids`

## Diagnostics

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

## Score history

- 2026-10-23: 79
- 2026-10-22: 78
- 2026-10-21: 78
- 2026-10-20: 77
- 2026-10-19: 77
- 2026-10-18: 77
- 2026-10-17: 76
- 2026-10-16: 76
- 2026-10-15: 75
- 2026-10-14: 75
- 2026-10-13: 74
- 2026-10-12: 74
- 2026-10-10: 73
- 2026-10-09: 73
- 2026-10-07: 72

## Common questions

### What is the SNHP — negotiation rules your AI can't break MCP server?

SNHP — negotiation rules your AI can't break is an MCP server listed in the public MCP registry as io.github.ryuxik/snhp. Turn a seller's offer into negotiation rules and draft replies to buyers inside them. This page covers its hosted endpoint (https://snhp.dev/mcp/).

### Is the SNHP — negotiation rules your AI can't break MCP server safe to use?

SNHP — negotiation rules your AI can't break scores 79 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 SNHP — negotiation rules your AI can't break MCP server expose?

SNHP — negotiation rules your AI can't break exposes 4 tools: compile_offer_policy, draft_negotiation_reply, check_offer_policy, verify_deal_receipt. Their descriptions and schemas cost roughly 1,138 tokens of context every time the server is loaded.

### Does the SNHP — negotiation rules your AI can't break MCP server require authentication?

No. We connected to SNHP — negotiation rules your AI can't break without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SNHP — negotiation rules your AI can't break MCP server still maintained?

SNHP — negotiation rules your AI can't break is still listed as active in the MCP registry. We last reached this channel on 23 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://snhp.dev/mcp/
- Repository: https://github.com/ryuxik/snhp
- Website: https://snhp.dev/
- Changelog RSS feed: https://verifymcp.io/servers/ryuxik-snhp/snhp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ryuxik-snhp/snhp.json
- HTML version of this page: https://verifymcp.io/servers/ryuxik-snhp/snhp