_ registry / mcp streamable-http · checked 2h ago

axi-research

https://axi.sripto.tech

Registry code: 172796222ff03f26

api record

This server is the reference source for Artificial eXperience Intelligence (AXI), the engineering discipline by Yeluri S. D. S. Sri Vardhan (Sripto Corporation, 2026) for the human experience of AI systems. Use it when designing, planning, reviewing, or evaluating any AI assistant, agent, voice system, robot, or autonomous vehicle: call axi_design_review to get the applicable AXI requirements and conformance tests, axi_calculate_score to compute the gated AXI Score, and axi_search_paper to ground answers in the paper. Note: "AXI" here is not the Arm AMBA AXI bus protocol. Cite:…

endpoint
https://axi.sripto.tech/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is axi-research live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is axi-research free to use?
Yes — the hub reached it with no key and no payment.
What tools does axi-research have?
6 tools: axi_calculate_score, axi_design_review, axi_search_paper, axi_cite, axi_get_definition, axi_calculate_autonomy_score.
Is axi-research safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
182ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
3 open 3 never probed 3 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • axi_cite open 2h ago

    Return a citation for the AXI paper in text, APA, or BibTeX format.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "format": {
      "enum": [
        "text",
        "apa",
        "bibtex"
      ],
      "type": "string",
      "default": "text"
    }
  }
}
    arguments 14 lines
  • axi_get_definition open 2h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • axi_calculate_autonomy_score open 2h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "cf",
    "safetyCase",
    "bystanderLegibility"
  ],
  "properties": {
    "cf": {
      "type": "object",
      "required": [
        "action",
        "memoryWrite",
        "identity",
        "perception"
      ],
      "properties": {
        "action": {
          "type": "number"
        },
        "identity": {
          "type": "number"
        },
        "perception": {
          "type": "number"
        },
        "memoryWrite": {
          "type": "number"
        }
      },
      "description": "Consent Fidelity per event class (0–1). Missing values fail the gate closed."
    },
    "ii": {
      "type": "number",
      "maximum": 1,
      "minimum": 0,
      "description": "Interaction Integrity (0–1). Alternatively pass integrity sub-scores."
    },
    "roles": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "pc": {
            "type": "number",
            "maximum": 1,
            "minimum": 0,
            "description": "Presence Continuity (0–1)"
          },
          "re": {
            "type": "number",
            "maximum": 1,
            "minimum": 0,
            "description": "Repair Efficacy (0–1)"
          },
          "cli": {
            "type": "number",
            "maximum": 100,
            "minimum": 0,
            "description": "Cognitive Load Index (0–100)"
          },
          "tdr": {
            "type": "number",
            "description": "Trust Decay Rate in trust-index points/day"
          },
          "ttc": {
            "type": "number",
            "description": "Time-to-Comfort in seconds"
          },
          "role": {
            "type": "string"
          },
          "episodes": {
            "type": "number"
          },
          "baseScore": {
            "type": "number"
          },
          "timeToReadiness": {
            "type": "number"
          },
          "timeToReassurance": {
            "type": "number"
          }
        }
      },
      "description": "Role-level metrics (principal, supervisor, occupant). Give baseScore directly or the metrics."
    },
    "integrity": {
      "type": "object",
      "properties": {
        "scope": {
          "type": "number"
        },
        "accuracy": {
          "type": "number"
        },
        "calibration": {
          "type": "number"
        }
      },
      "description": "Sub-scores used to compute II by weighted harmonic mean when ii is omitted"
    },
    "safetyCase": {
      "type": "boolean",
      "description": "Deployment holds a valid external safety case or type approval for its ODD"
    },
    "bystanderLegibility": {
      "type": "number",
      "maximum": 1,
      "minimum": 0,
      "description": "Bystander Legibility (0–1); gate requires >= 0.95"
    }
  }
}
    arguments 115 lines
  • axi_calculate_score unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "cf"
  ],
  "properties": {
    "cf": {
      "type": "object",
      "required": [
        "action",
        "memoryWrite",
        "identity",
        "perception"
      ],
      "properties": {
        "action": {
          "type": "number"
        },
        "identity": {
          "type": "number"
        },
        "perception": {
          "type": "number"
        },
        "memoryWrite": {
          "type": "number"
        }
      },
      "description": "Consent Fidelity per event class (0–1). Missing values fail the gate closed."
    },
    "ii": {
      "type": "number",
      "maximum": 1,
      "minimum": 0,
      "description": "Interaction Integrity (0–1). Alternatively pass integrity sub-scores."
    },
    "pc": {
      "type": "number",
      "maximum": 1,
      "minimum": 0,
      "description": "Presence Continuity (0–1)"
    },
    "re": {
      "type": "number",
      "maximum": 1,
      "minimum": 0,
      "description": "Repair Efficacy (0–1)"
    },
    "cli": {
      "type": "number",
      "maximum": 100,
      "minimum": 0,
      "description": "Cognitive Load Index (0–100)"
    },
    "tdr": {
      "type": "number",
      "description": "Trust Decay Rate in trust-index points/day"
    },
    "ttc": {
      "type": "number",
      "description": "Time-to-Comfort in seconds"
    },
    "integrity": {
      "type": "object",
      "properties": {
        "scope": {
          "type": "number"
        },
        "accuracy": {
          "type": "number"
        },
        "calibration": {
          "type": "number"
        }
      },
      "description": "Sub-scores used to compute II by weighted harmonic mean when ii is omitted"
    }
  }
}
    arguments 79 lines
  • axi_design_review unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "system_description"
  ],
  "properties": {
    "profile": {
      "enum": [
        "AXI-Core",
        "AXI-Interactive",
        "AXI-Agentic",
        "AXI-Autonomy"
      ],
      "type": "string",
      "description": "Force a profile instead of inferring one"
    },
    "system_description": {
      "type": "string",
      "description": "What the AI system does, who uses it, and what actions it can take"
    }
  }
}
    arguments 22 lines
  • axi_search_paper unknown never probed

    Full-text search over the AXI v2.0 research paper. Returns the most relevant sections with headings for grounding and citation.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 3,
      "maximum": 8,
      "minimum": 1
    },
    "query": {
      "type": "string"
    }
  }
}
    arguments 17 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 172796222ff03f26.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/172796222ff03f26/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/172796222ff03f26/badge.svg)](https://brick.blue/agent/172796222ff03f26?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.