Artificial eXperience Intelligence (AXI)
REMOTE · AXI.SRIPTO.TECH
AXI design reviews, gated AXI Score, and paper search for AI assistants, agents, and robots.
Available components
Last scanned (21 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 4 Nov 2026.
Category AI and Machine Learning
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 Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability53
- 18% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 861 tokens (~57/item across 15 items; 6 tools + 9 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 84% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 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.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Probed https://axi.sripto.tech/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sripto.tech | CN=WE1,O=Google Trust Services,C=US | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | a10a582bf69ad3830e7ba339b44fb560 |
| SANs: sripto.tech, axi.sripto.tech, *.axi.sripto.tech | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of axi.sripto.tech. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tech. | present | 2185 | 13 | Verified |
| sripto.tech. | present | 2371 | 13 | Verified |
| axi.sripto.tech. | Verified address RRset verified with the apex keys |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://axi.sripto.tech/api/mcp | Verified | 200 | |
| http (plaintext) | http://axi.sripto.tech/api/mcp | HTTPS enforced | 301 | https://axi.sripto.tech/api/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 →
axi_calculate_autonomy_score Calculate AXI-Autonomy Score ~191
Compute AXI_A for robotaxis, driver-assistance, delivery robots, and humanoids: safety-case, bystander-legibility, consent, and integrity gates times the episode-weighted role BaseScore.
| Name | Type | Req | Description |
|---|---|---|---|
| bystanderLegibility | number | yes | Bystander Legibility (0–1); gate requires >= 0.95 |
| cf | object | yes | Consent Fidelity per event class (0–1). Missing values fail the gate closed. |
| ii | number | – | Interaction Integrity (0–1). Alternatively pass integrity sub-scores. |
| integrity | object | – | Sub-scores used to compute II by weighted harmonic mean when ii is omitted |
| roles | array | – | Role-level metrics (principal, supervisor, occupant). Give baseScore directly or the metrics. |
| safetyCase | boolean | yes | Deployment holds a valid external safety case or type approval for its ODD |
No output schema declared.
No examples provided.
axi_calculate_score Calculate AXI Score ~188
Compute the multiplicative gated AXI Score (AXI v2.0, Section 4.5.8) from telemetry metrics. Consent and integrity gates fail closed when data is missing.
| Name | Type | Req | Description |
|---|---|---|---|
| cf | object | yes | Consent Fidelity per event class (0–1). Missing values fail the gate closed. |
| cli | number | – | Cognitive Load Index (0–100) |
| ii | number | – | Interaction Integrity (0–1). Alternatively pass integrity sub-scores. |
| integrity | object | – | Sub-scores used to compute II by weighted harmonic mean when ii is omitted |
| pc | number | – | Presence Continuity (0–1) |
| re | number | – | Repair Efficacy (0–1) |
| tdr | number | – | Trust Decay Rate in trust-index points/day |
| ttc | number | – | Time-to-Comfort in seconds |
No output schema declared.
No examples provided.
axi_cite Cite AXI ~35
Return a citation for the AXI paper in text, APA, or BibTeX format.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | – |
No output schema declared.
No examples provided.
axi_design_review AXI design review checklist ~100
Given a description of an AI system (assistant, coding agent, voice bot, background agent, robot, vehicle), return the applicable AXI conformance profile, Bridge components, guardrails, and black-box conformance tests to include in its design and plan.
| Name | Type | Req | Description |
|---|---|---|---|
| profile | string | – | Force a profile instead of inferring one |
| system_description | string | yes | What the AI system does, who uses it, and what actions it can take |
No output schema declared.
No examples provided.
axi_get_definition Define AXI ~55
Return the definition of Artificial eXperience Intelligence (AXI) from the v2.0 paper, its author, citation, and disambiguation from similarly named terms (e.g. the Arm AMBA AXI bus).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
axi_search_paper Search the AXI paper ~50
Full-text search over the AXI v2.0 research paper. Returns the most relevant sections with headings for grounding and citation.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Artificial eXperience Intelligence (AXI) MCP server?
Artificial eXperience Intelligence (AXI) is a hosted endpoint at https://axi.sripto.tech/api/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 · axi.sripto.tech
claude mcp add --transport http tech-sripto-axi-axi 'https://axi.sripto.tech/api/mcp'
What is the Artificial eXperience Intelligence (AXI) MCP server?
Artificial eXperience Intelligence (AXI) is an MCP server listed in the public MCP registry as tech.sripto.axi/axi. AXI design reviews, gated AXI Score, and paper search for AI assistants, agents, and robots. This page covers its hosted endpoint (https://axi.sripto.tech/api/mcp).
Is the Artificial eXperience Intelligence (AXI) MCP server safe to use?
Artificial eXperience Intelligence (AXI) scores 81 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 Artificial eXperience Intelligence (AXI) MCP server expose?
Artificial eXperience Intelligence (AXI) exposes 6 tools: axi_get_definition, axi_calculate_score, axi_calculate_autonomy_score, axi_design_review, axi_search_paper, axi_cite. Their descriptions and schemas cost roughly 619 tokens of context every time the server is loaded.
Does the Artificial eXperience Intelligence (AXI) MCP server require authentication?
No. We connected to Artificial eXperience Intelligence (AXI) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Artificial eXperience Intelligence (AXI) MCP server still maintained?
Artificial eXperience Intelligence (AXI) is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.