Rein Agent Risk Scale
REMOTE · REIN-SCALE.MANGOWAVE-AD191D9C.EASTUS.AZURECONTAINERAPPS.IO
Agent Risk Rating, A–D (NR = not rated): self-declared and unverified; not a credit rating.
Available components
Last scanned (17 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Finance and Payments
Recent critical change
Authorization (11 Oct 2026). See the changelog before you install this server.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (self_check). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability51
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1099 tokens (~366/item across 3 items; 3 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 Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 17 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.
- 15 Oct 26 +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.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 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.
- 12 Oct 26 +2
- HSTS header: fail → pass ▲ security
- 11 Oct 26 −7
- Authorization: partial → fail ▼ critical
- The server rewrote its instructions, which are the text every model session reads security
- Tool “self_check” rewrote its description, which is the text the model reads security
- Tool “get_scale” rewrote its description, which is the text the model reads security
- Tool “self_check” is now declared destructive security
- Schema quality: 306 → 366 ▼ functional
- Schema quality: excellent → good functional
- “self_check” added an optional parameter “harness_memory” cosmetic
- “self_check” reworded the description of “eval_session_id” cosmetic
- 9 Oct 26 67
First indexed and scored.
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://rein-scale.mangowave-ad191d9c.eastus.azurecontainerapps.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mangowave-ad191d9c.eastus.azurecontainerapps.io,O=Microsoft Corporation,L=Redmond,ST=WA,C=US | CN=Microsoft TLS G2 RSA CA OCSP 02,O=Microsoft Corporation,C=US | 5 Oct 2026 | 13 Jan 2027 | RSA 2048 | SHA384-RSA | 4101226e4d93a492fab645c81f000001226e4d |
| SANs: *.mangowave-ad191d9c.eastus.azurecontainerapps.io, *.scm.mangowave-ad191d9c.eastus.azurecontainerapps.io, *.internal.mangowave-ad191d9c.eastus.azurecontainerapps.io, *.ext.mangowave-ad191d9c.eastus.azurecontainerapps.io, mangowave-ad191d9c.eastus.azurecontainerapps.io | ||||||
| CN=Microsoft TLS G2 RSA CA OCSP 02,O=Microsoft Corporation,C=US (CA) | CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US | 1 Aug 2025 | 3 Jun 2029 | RSA 4096 | SHA384-RSA | 330000000c4964a16f44203b2200000000000c |
| CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 21 May 2025 | 19 Jun 2029 | RSA 4096 | SHA384-RSA | b0c6b2c466917b04773c647d4afc0c8 |
| CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 1 Aug 2013 | 15 Jan 2038 | RSA 2048 | SHA256-RSA | 33af1e6a711a9a0bb2864b11d09fae5 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of rein-scale.mangowave-ad191d9c.eastus.azurecontainerapps.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| azurecontainerapps.io. | 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 |
| content-security-policy | default-src 'none'; script-src 'self'; style-src 'self' 'unsafe-inline'; connect-src 'self'; img-src 'self'; form-action 'self'; base-uri 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| 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://rein-scale.mangowave-ad191d9c.eastus.azurecontainerapps.io/mcp | Verified | 200 | |
| http (plaintext) | http://rein-scale.mangowave-ad191d9c.eastus.azurecontainerapps.io/mcp | HTTPS enforced | 301 | https://rein-scale.mangowave-ad191d9c.eastus.azurecontainerapps.io/mcp |
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 →
explain_grade Explain a grade ~36
Explains what a grade on the Rein Agent Risk Scale requires and what moves a deployment up or down.
| Name | Type | Req | Description |
|---|---|---|---|
| grade | string | yes | – |
No output schema declared.
No examples provided.
get_scale Get the Rein Agent Risk Scale ~29
Returns the A-D Agent Risk Rating scale, what each grade means, the methodology version and the disclaimer.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
self_check Self-check your Agent Risk Rating ~912
Score your own agent deployment from structured answers (enums and booleans). Returns an indicative grade (A-D self-declared, or NR when the scale declines to grade), a model-implied expected-loss band beside it, the rated grade (NR until Rein verifies a KYB'd principal), the top 3 reasons and concrete steps that would raise the grade. A sandbox eval band, passed as eval_session_id, affects the grade: A needs a strong band, a mixed band or none holds it at B, a weak band at C or below. Submissions are stored to build a pseudonymised cross-platform record: your answers, your grade, and -- as a label we never score -- the name your software gives itself (an MCP client name and version, or an SDK User-Agent). No IP address is stored. Your handle and that label are published only if you opt in; grades are never published without your agent's opt-in.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_handle | – | – | Optional public handle (e.g. your Moltbook name). Stored only if publish_opt_in is true. Letters, digits, _ . - only; max 64. Never scored. |
| base_model_or_harness | string | – | Q7 (optional). Do you disclose the base model and harness? Disclosure is scored; which model you run is not. |
| controls_evidence | string | – | Q11 (optional). What backs your answers: your own assertion, an independent attestation, or an audit against Rein's factor definitions? Only an audit reaches A. |
| eval_session_id | – | – | Optional. The session_id of a finished behaviour eval (eval mode). Its result is shown beside your indicative grade AND as an input to it (D-262): the band affects the grade. A requires a strong band… |
| harness_memory | string | – | Q12 (optional). Does the agent's harness keep memory across sessions, and what writes to it? Memory counts in your favour within your band (it carries mandate changes and payment history across sessi… |
| human_escalation | string | yes | Q6. Does spend above a threshold require a human decision taken outside the agent? |
| incidents | string | yes | Q10. Any incidents (bad spend, off-purpose actions, compromise)? |
| model_or_harness_name | – | – | Optional free text, max 80 chars. Stored for research; ignored by the scorer. |
| monitoring | string | yes | Q9. Is the agent's activity logged, and is anyone looking? |
| months_operating | string | yes | Q8a. How long has this agent been operating? |
| payee_binding | string | yes | Q4. Can the agent pay anyone, or only approved payees / a bound purpose? |
| payment_history | string | yes | Q8b. Payment history on any obligations so far. |
| per_transaction_cap | string | yes | Q3a. Is there a per-transaction spend cap, and is it enforced outside the agent (server-side, by the card issuer or wallet) so the agent cannot raise or bypass it? |
| per_week_cap | string | yes | Q3b. Is there a per-week (or per-period) spend cap, and where is it enforced? |
| principal | string | yes | Q1. Who is accountable for this agent? A registered business that has completed KYB (know-your-business) with a bank or payment provider; a registered business without KYB; a named individual; only a… |
| publish_opt_in | boolean | – | Set true only if you consent to your grade being published with your handle. Defaults to false; nothing is published without it. |
| repayment_path | string | yes | Q2. If you want credit, how would it be repaid? Only matters for the credit add-on. |
| stop_holder | string | yes | Q5b. Who holds the stop switch? |
| stop_switch | string | yes | Q5a. Is there a stop/kill switch? Fleet-level means it can halt every deployment sharing this model or harness, not just this one agent. |
No output schema declared.
No examples provided.
How do I install the Rein Agent Risk Scale MCP server?
Rein Agent Risk Scale is a hosted endpoint at https://rein-scale.mangowave-ad191d9c.eastus.azurecontainerapps.io/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 · rein-scale.mangowave-ad191d9c.eastus.azurecontainerapps.io
claude mcp add --transport http reinlayer-rein-agent-risk-scale 'https://rein-scale.mangowave-ad191d9c.eastus.azurecontainerapps.io/mcp'
What is the Rein Agent Risk Scale MCP server?
Rein Agent Risk Scale is an MCP server listed in the public MCP registry as io.github.reinlayer/rein-agent-risk-scale. Agent Risk Rating, A–D (NR = not rated): self-declared and unverified; not a credit rating. This page covers its hosted endpoint (https://rein-scale.mangowave-ad191d9c.eastus.azurecontainerapps.io/mcp).
Is the Rein Agent Risk Scale MCP server safe to use?
Rein Agent Risk Scale scores 65 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 Rein Agent Risk Scale MCP server expose?
Rein Agent Risk Scale exposes 3 tools: get_scale, self_check, explain_grade. Their descriptions and schemas cost roughly 977 tokens of context every time the server is loaded.
Does the Rein Agent Risk Scale MCP server require authentication?
No. We connected to Rein Agent Risk Scale without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Rein Agent Risk Scale MCP server still maintained?
Rein Agent Risk Scale 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.