com.ayurak/aribot-mcp
REMOTE · MCP.ARIBOT.AYURAK.COM · 2 COMPONENTS · SCANNED SEP 20
Threat modeling, code, API & cloud security, shadow-AI & compliance governance.
Available components
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 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the com.ayurak/aribot-mcp server?
com.ayurak/aribot-mcp is a hosted endpoint at https://mcp.aribot.ayurak.com/, 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 · mcp.aribot.ayurak.com
claude mcp add --transport http com-ayurak-aribot-mcp 'https://mcp.aribot.ayurak.com/'
{
"mcpServers": {
"com-ayurak-aribot-mcp": {
"url": "https://mcp.aribot.ayurak.com/"
}
}
} {
"servers": {
"com-ayurak-aribot-mcp": {
"type": "http",
"url": "https://mcp.aribot.ayurak.com/"
}
}
} [mcp_servers.com-ayurak-aribot-mcp] url = "https://mcp.aribot.ayurak.com/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-ayurak-aribot-mcp": {
"type": "remote",
"url": "https://mcp.aribot.ayurak.com/",
"enabled": true
}
}
} openclaw mcp add com-ayurak-aribot-mcp --url 'https://mcp.aribot.ayurak.com/' --transport streamable-http
mcp_servers:
com-ayurak-aribot-mcp:
url: "https://mcp.aribot.ayurak.com/" {
"McpServers": {
"com-ayurak-aribot-mcp": {
"Transport": "http",
"Url": "https://mcp.aribot.ayurak.com/"
}
}
} assistant mcp add com-ayurak-aribot-mcp -t streamable-http -u 'https://mcp.aribot.ayurak.com/'
{
"mcpServers": {
"com-ayurak-aribot-mcp": {
"type": "http",
"url": "https://mcp.aribot.ayurak.com/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 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
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 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
- 31 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
- 30 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
- 29 Jul 26 0
- Schema quality: 1447 → 1648 ▼ functional
- New tool “onboard_agents” functional
- 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
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 20 Sept 2026 · Probed https://mcp.aribot.ayurak.com/
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 | 24 Aug 2026 | 22 Nov 2026 | RSA 2048 | SHA256-RSA | 5b8c72f33655edd17fc47e27d09762e6d29 |
| 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.aribot.ayurak.com/ | Verified | 200 | |
| http (plaintext) | http://mcp.aribot.ayurak.com/ | HTTPS enforced | 308 | https://mcp.aribot.ayurak.com |
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 →
apply_remediation Apply a remediation (governed) ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| resource_context | object | – | provider/resource_id/region/account_id/metadata |
| rule_id | string | yes | Policy/rule id (e.g. AWS_S3_PUBLIC_ACCESS) |
| threat_id | string | yes | Threat id/code to remediate |
No output schema declared.
No examples provided.
code_review_scan Run a code security 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.
| Name | Type | Req | Description |
|---|---|---|---|
| scan_id | string | yes | Id of an existing code-review scan to (re)run |
No output schema declared.
No examples provided.
compliance_scan Run a platform / 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.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | – | Cloud account id (account-scoped scans) |
| diagram_id | string | – | Diagram id/uuid (diagram-scoped scans) |
| frameworks | array | – | Optional standard/framework ids to scope the scan |
| scan_type | string | yes | platform | compliance | pipeline | sbom |
| severity_filter | array | – | Optional severity levels to include |
| simulation_mode | boolean | – | Dry-run the scan without side effects |
| source | string | – | Scan source (default: hybrid) |
No output schema declared.
No examples provided.
compliance_status Get 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.
| Name | Type | Req | Description |
|---|---|---|---|
| diagram_id | string | – | Optional diagram to add framework coverage for |
| scan_id | string | – | Optional 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max discoveries to return |
| scan_id | string | – | Optional CodeReviewScan id; company-wide latest if omitted |
No output schema declared.
No examples provided.
generate_threat_model 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.
| Name | Type | Req | Description |
|---|---|---|---|
| edges | array | – | ReactFlow edges |
| name | string | – | Threat model name |
| nodes | array | yes | ReactFlow 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max endpoints to return |
| scan_id | string | – | Optional 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.
| Name | Type | Req | Description |
|---|---|---|---|
| checkout_request_id | string | – | Approved license_request_id to complete payment for (returns a hosted Checkout URL) |
| request_plan | string | – | Optional plan key to request (pro|max|…) — files a request for super-admin approval; does not grant or charge |
| topup_amount | number | – | Optional 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.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | – | Optional single cloud Account id; all company accounts if omitted |
No output schema declared.
No examples provided.
get_diagram_summary Get a diagram summary ~45
The canonical diagram summary every badge/card/header reads: threat counts by severity, risk value, compliance and framework coverage.
| Name | Type | Req | Description |
|---|---|---|---|
| diagram_id | string | yes | Diagram id/uuid |
No output schema declared.
No examples provided.
get_framework_coverage 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.
| Name | Type | Req | Description |
|---|---|---|---|
| diagram_id | string | yes | Diagram pk or uuid |
| framework | string | – | Optional framework filter (e.g. 'NIST-800-53', 'SOC2') |
| include_graph | boolean | – | Also return the crossmap node/edge graph |
No output schema declared.
No examples provided.
get_insights Get diagram insights ~43
Threat/control matrix metrics + framework coverage for a diagram, joined with its latest code-security scan when one exists.
| Name | Type | Req | Description |
|---|---|---|---|
| diagram_id | string | yes | Diagram id/uuid |
No output schema declared.
No examples provided.
get_remediation Get Remediation Guidance ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| resource_context | object | – | provider/resource_id/region/account_id/metadata |
| rule_id | string | yes | Policy/rule id (e.g. AWS_S3_PUBLIC_ACCESS) |
| threat_id | string | yes | Threat id/code to remediate |
No output schema declared.
No examples provided.
get_traceability Get Traceability Matrix ~51
Return the diagram→threat→finding→control→requirement→remediation traceability matrix for a scan in your scope, with coverage metrics.
| Name | Type | Req | Description |
|---|---|---|---|
| scan_id | string | yes | Code-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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_cards | array | – | A2A 1.0 Agent Cards ({name, url, provider, version, protocolVersion, ...}) |
| agents | array | – | Agent ids or descriptors ({agent_id, display?, cohort?}) |
| auto_suspend_threshold | number | – | Optional 0..1 auto-suspend deviation threshold for the cohort policy |
| cohort | string | – | Optional shared cohort (provider/model/deployment group) |
No output schema declared.
No examples provided.
verify_threats_in_code 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.
| Name | Type | Req | Description |
|---|---|---|---|
| async_ | boolean | – | – |
| code_content | string | – | Optional inline code context |
| repository_id | string | – | Optional connected repo to fetch code from |
| scan_id | string | yes | CodeReviewScan id (uuid) |
| threat_id | string | – | Optional: a single threat id or code |
No output schema declared.
No examples provided.
What is the com.ayurak/aribot-mcp server?
com.ayurak/aribot-mcp is listed in the public MCP registry as com.ayurak/aribot-mcp. Threat modeling, code, API & cloud security, shadow-AI & compliance governance. This page covers its hosted endpoint (https://mcp.aribot.ayurak.com/).
Is the com.ayurak/aribot-mcp server safe to use?
com.ayurak/aribot-mcp scores 91 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 com.ayurak/aribot-mcp server expose?
com.ayurak/aribot-mcp exposes 16 tools: get_billing, onboard_agents, generate_threat_model, verify_threats_in_code, get_traceability, and 11 more. Their descriptions and schemas cost roughly 1,648 tokens of context every time the server is loaded.
Does the com.ayurak/aribot-mcp server require authentication?
Yes. com.ayurak/aribot-mcp asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the com.ayurak/aribot-mcp server still maintained?
com.ayurak/aribot-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.