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

io.github.aristiun/aribot

REMOTE · MCP.ARIBOT.AYURAK.COM · SCANNED AUG 3

Threat modeling, code/cloud/pipeline scanning, shadow-AI discovery, compliance checks and fixes.

+10 this week 78 Trust /100
Trust breakdown (6 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 →

Endpoint Security97
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
  • The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1648 tokens (~103/item across 16 items; 16 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 98% of tool parameters carry a description.Partial
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.aribot.ayurak.com

# add to Claude Code
claude mcp add --transport http aristiun-aribot https://mcp.aribot.ayurak.com/mcp
# ~/.codex/config.toml
[mcp_servers.aristiun-aribot]
url = "https://mcp.aribot.ayurak.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "aristiun-aribot": {
      "type": "remote",
      "url": "https://mcp.aribot.ayurak.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add aristiun-aribot --url https://mcp.aribot.ayurak.com/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  aristiun-aribot:
    url: "https://mcp.aribot.ayurak.com/mcp"
// mcp.json
{
  "mcpServers": {
    "aristiun-aribot": {
      "type": "http",
      "url": "https://mcp.aribot.ayurak.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 3 Aug 26 +1

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

  • 1 Aug 26 +1

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

  • 31 Jul 26 +6
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 26 +2
    • Schema quality: 1447 → 1648 functional
    • New tool “onboard_agents” functional
  • 28 Jul 26 +1

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

  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 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 3 Aug 2026 · Probed https://mcp.aribot.ayurak.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.aribot.ayurak.com CN=YR2,O=Let's Encrypt,C=US 25 Jun 2026 23 Sept 2026 RSA 2048 SHA256-RSA 54ce6a4f77060948f0fef6658673a132563
SANs: mcp.aribot.ayurak.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f
DNSSEC secure

Validation of mcp.aribot.ayurak.com. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
ayurak.com. present 12824 8 Verified
mcp.aribot.ayurak.com. Verified address RRset verified with the apex keys
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://mcp.aribot.ayurak.com/.well-known/oauth-protected-resource"

Bearer resource_metadata="https://mcp.aribot.ayurak.com/.well-known/oauth-protected-resource"
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=()

Protected resource metadata

Document https://mcp.aribot.ayurak.com/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://mcp.aribot.ayurak.com
Authorisation server https://api.aribot.ayurak.com
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.aribot.ayurak.com/mcp Verified 200
http (plaintext) http://mcp.aribot.ayurak.com/mcp HTTPS enforced 308 https://mcp.aribot.ayurak.com/mcp
MCP tools — 16 exposed · ~1,648 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.

Tool Tokens
apply_remediation ~109

Apply a remediation for real (mode=live). Routed through the full governance funnel — patent reachability/kill-chain gates, autonomy policy and the approval flow. If your policy requires approval it returns 'requires_approval' rather than acting.

NameTypeReqDescription
resource_contextobjectprovider/resource_id/region/account_id/metadata
rule_idstringyesPolicy/rule id (e.g. AWS_S3_PUBLIC_ACCESS)
threat_idstringyesThreat id/code to remediate

No output schema declared.

No examples provided.

code_review_scan ~71

Start (or re-run) a code-security scan for an existing scan/repository in your scope. Returns a poll pointer; results include SAST, secrets, deps, pipeline review and the traceability matrix.

NameTypeReqDescription
scan_idstringyesId of an existing code-review scan to (re)run

No output schema declared.

No examples provided.

compliance_scan ~152

Run a cloud/platform or compliance scan against an account or diagram in your scope (async). scan_type ∈ platform|compliance|pipeline|sbom. Returns a task id to poll.

NameTypeReqDescription
account_idstringCloud account id (account-scoped scans)
diagram_idstringDiagram id/uuid (diagram-scoped scans)
frameworksarrayOptional standard/framework ids to scope the scan
scan_typestringyesplatform | compliance | pipeline | sbom
severity_filterarrayOptional severity levels to include
simulation_modebooleanDry-run the scan without side effects
sourcestringScan source (default: hybrid)

No output schema declared.

No examples provided.

compliance_status ~76

Company-level compliance posture rollup (pass rate, control compliance, mitigated counts, per-framework coverage). Suitable for a CI gate. Wraps the traceability company rollup.

NameTypeReqDescription
diagram_idstringOptional diagram to add framework coverage for
scan_idstringOptional anchor scan; latest is used if omitted

No output schema declared.

No examples provided.

discover_shadow_ai ~104

Shadow-AI posture (part of Code Security): unsanctioned / unknown AI-service usage discovered in code — totals, risk score, provider/type breakdown, hardcoded-key count, and top discoveries. Company latest, or one scan with `scan_id`. Reads code_review ShadowAIReport/ShadowAIDiscovery.

NameTypeReqDescription
limitintegerMax discoveries to return
scan_idstringOptional CodeReviewScan id; company-wide latest if omitted

No output schema declared.

No examples provided.

generate_threat_model ~89

Create a threat model from a normalized architecture (ReactFlow nodes + edges). Ingests components via the shared Stage-0 service; the pipeline then auto-generates threats. Returns the diagram id.

NameTypeReqDescription
edgesarrayReactFlow edges
namestringThreat model name
nodesarrayyesReactFlow nodes (each: id, position, data.label)

No output schema declared.

No examples provided.

get_api_security ~84

API security inventory (part of Code Security): discovered API endpoints with authentication status, risk level and risk factors, plus method/risk breakdowns. Company-wide or one scan with `scan_id`. Reads code_review ApiEndpointDiscovery.

NameTypeReqDescription
limitintegerMax endpoints to return
scan_idstringOptional CodeReviewScan id; company-wide if omitted

No output schema declared.

No examples provided.

get_billing ~214

Billing status + self-service payment for your company: credit-wallet balance, pay-per-use flag, license tier / annual commitment, per-action prices, purchasable plans, and any approved-but-unpaid plans. Pass `checkout_request_id` to get a hosted Stripe Checkout URL to COMPLETE an approved plan, `topup_amount` (EUR) to get one to TOP UP the wallet, or `request_plan` (starter|pay_per_use|pro|max|enterprise) to REQUEST a plan (files a request for super-admin approval — never grants). Use this to view or RESOLVE a 402 without leaving the connector.

NameTypeReqDescription
checkout_request_idstringApproved license_request_id to complete payment for (returns a hosted Checkout URL)
request_planstringOptional plan key to request (pro|max|…) — files a request for super-admin approval; does not grant or charge
topup_amountnumberOptional EUR amount to top up the credit wallet (returns a hosted Checkout URL)

No output schema declared.

No examples provided.

get_cloud_compliance ~78

Cloud security & compliance posture (Cloud Compliance): per connected cloud account, the latest CIS/NIST cloud-policy scan — compliance %, failing policies/records, status — plus a company rollup. Reads customers.Account.latest_scan -> compliances.ScanResults.

NameTypeReqDescription
account_idstringOptional single cloud Account id; all company accounts if omitted

No output schema declared.

No examples provided.

get_diagram_summary ~45

The canonical diagram summary every badge/card/header reads: threat counts by severity, risk value, compliance and framework coverage.

NameTypeReqDescription
diagram_idstringyesDiagram id/uuid

No output schema declared.

No examples provided.

get_framework_coverage ~106

Compliance-framework coverage for a diagram (real, ControlCodeMap-backed), optionally for one framework, plus an optional crossmap relationship graph. Wraps derive_framework_coverage + crossmap_cypher.build_graph.

NameTypeReqDescription
diagram_idstringyesDiagram pk or uuid
frameworkstringOptional framework filter (e.g. 'NIST-800-53', 'SOC2')
include_graphbooleanAlso return the crossmap node/edge graph

No output schema declared.

No examples provided.

get_insights ~43

Threat/control matrix metrics + framework coverage for a diagram, joined with its latest code-security scan when one exists.

NameTypeReqDescription
diagram_idstringyesDiagram id/uuid

No output schema declared.

No examples provided.

get_remediation ~100

Compute a remediation plan for a threat/finding WITHOUT applying it (mode=dry_run). Runs the same governed engine as apply_remediation, including the patent gates, and returns the proposed steps.

NameTypeReqDescription
resource_contextobjectprovider/resource_id/region/account_id/metadata
rule_idstringyesPolicy/rule id (e.g. AWS_S3_PUBLIC_ACCESS)
threat_idstringyesThreat id/code to remediate

No output schema declared.

No examples provided.

get_traceability ~51

Return the diagram→threat→finding→control→requirement→remediation traceability matrix for a scan in your scope, with coverage metrics.

NameTypeReqDescription
scan_idstringyesCode-review scan id

No output schema declared.

No examples provided.

onboard_agents ~201

Bulk-onboard agent identities to the governed fleet (Agent Governance). Accepts plain ids or {agent_id} descriptors in `agents`, A2A 1.0 Agent Cards in `agent_cards` (name/url/provider/version/protocolVersion), or MCP client descriptors, under an optional `cohort` + shared auto-suspend policy. Idempotent. Requires the agent_governance licence + a manage:agents grant (or a first-party super-admin). Agents also self-onboard on first token/call.

NameTypeReqDescription
agent_cardsarrayA2A 1.0 Agent Cards ({name, url, provider, version, protocolVersion, ...})
agentsarrayAgent ids or descriptors ({agent_id, display?, cohort?})
auto_suspend_thresholdnumberOptional 0..1 auto-suspend deviation threshold for the cohort policy
cohortstringOptional shared cohort (provider/model/deployment group)

No output schema declared.

No examples provided.

verify_threats_in_code ~125

Verify whether threats are mitigated in a scan's uploaded code. With `threat_id`, verifies one threat synchronously and returns the verdict; without it, verifies every diagram threat in the background. Wraps code_review ThreatVerificationService.

NameTypeReqDescription
async_boolean
code_contentstringOptional inline code context
repository_idstringOptional connected repo to fetch code from
scan_idstringyesCodeReviewScan id (uuid)
threat_idstringOptional: a single threat id or code

No output schema declared.

No examples provided.