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.

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.

Available components

+3 this week 79 Trust /100

Last scanned (11 hours ago)

Scores higher than 82% of remote servers

Reachable. Last reached 23 Oct 2026.

Category CRM and Sales

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 Security80
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 23 Oct 26 +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.

  • 21 Oct 26 +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.

  • 18 Oct 26 +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.

  • 16 Oct 26 +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.

  • 14 Oct 26 +1
    • Tool “draft_negotiation_reply” rewrote its description, which is the text the model reads security
    • “draft_negotiation_reply” added an optional parameter “stock” cosmetic
  • 12 Oct 26 +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.

  • 9 Oct 26 +1
    • Stability: unverified → 0.07 ▲ functional
  • 7 Oct 26 72

    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 23 Oct 2026 · Probed https://snhp.dev/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=snhp.dev CN=YE2,O=Let's Encrypt,C=US 29 Aug 2026 27 Nov 2026 ECDSA 256 ECDSA-SHA384 5b30a14fbec278eea6c679e3f16cf1cde97
SANs: snhp.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of snhp.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
snhp.dev. 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'none'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://snhp.dev/mcp/ Verified 200
http (plaintext) http://snhp.dev/mcp/ HTTPS enforced 301 https://snhp.dev/mcp/
MCP tools · 4 exposed · ~1,138 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
check_offer_policy ~94

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.

NameTypeReqDescription
policyobjectyesA policy object from compile_offer_policy, edited or not.
NameTypeReqDescription
error–––
issues–––
ok–––
policy–––
served–––
summary–––

No examples provided.

compile_offer_policy ~389

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

NameTypeReqDescription
access_keystring–Your SNHP access key — needed to compile a description (it runs a language model). Pilot businesses get one at https://snhp.dev/#pilot.
descriptionstring–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.
templatestring–Instead of a description: 'used-car', 'saas' or 'wholesale-water' (free, no key).
NameTypeReqDescription
error–––
issues–––
ok–––
policy–––
served–––
summary–––

No examples provided.

draft_negotiation_reply ~531

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

NameTypeReqDescription
access_keystring–Your SNHP access key (drafting runs a language model). Pilot businesses get one at https://snhp.dev/#pilot.
enginestring–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}.
messagestringyesThe buyer's latest message, exactly as written.
policyobjectyesThe 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.
NameTypeReqDescription
decided_by–––
done–––
engine–––
error–––
kind–––
menu–––
offer–––
reading–––
receipt–––
reply–––
reply_with_offer–––
state–––
writer–––

No examples provided.

verify_deal_receipt ~124

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.

NameTypeReqDescription
flags––The account record used for the deal, if any.
policyobjectyesThe policy the deal was made under.
receiptobjectyesThe receipt returned with a deal.
NameTypeReqDescription
checks–––
error–––
ok–––
problems–––
signatures–––
signed_by_snhp–––
signer_kids–––

No examples provided.

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.

remote · snhp.dev

# add to Claude Code
claude mcp add --transport http ryuxik-snhp 'https://snhp.dev/mcp/'
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.