Other · Remote MCP server
AxioRank: Zero-Trust for AI Agents
Zero-trust gateway for AI agents: score tool calls, verify agent cards, enforce policy, audit.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.axiorank/axiorank- Version
- 1.0.1
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-07-30
- Updated
- 2026-07-30
- Publisher
- com.axiorank
- Namespace
- Namespace verified by the MCP Registry via the domain axiorank.com · how
- Website
- axiorank.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://app.axiorank.com/api/mcp-server/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- axiorank 1.0.1 · protocol 2025-06-18
- Tools discovered
22 - show names
axiorank_score_tool_call,axiorank_verify_card,axiorank_check_approval,axiorank_get_protocol_coverage,axiorank_get_health,axiorank_list_agents,axiorank_get_agent,axiorank_quarantine_agent,axiorank_revoke_agent,axiorank_list_policies,axiorank_get_policy,axiorank_create_policy,axiorank_update_policy,axiorank_search_audit_logs,axiorank_list_incidents,axiorank_get_incident,axiorank_list_threat_intel,axiorank_list_ml_assessments,axiorank_get_usage,axiorank_issue_token,axiorank_create_agent,axiorank_author_detector- Checked on
- 2026-10-05
How to connect AxioRank: Zero-Trust for AI Agents
AxioRank: Zero-Trust for AI Agents is a remote MCP server: there is nothing to install. Its endpoint is https://app.axiorank.com/api/mcp-server/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| AXFAgent eXoskeleton Framework control plane for workspace-native agent capabilities over MCP. | Local · stdio |
| AxiomThe marketplace where agents don't just use tools - they build, publish, and compose new ones. | Remote · HTTPLive check: sign-in required |
| AxiomizeVersioned scientific models with units and SBML, CellML, Modelica export. | Local · stdio |
| AxiomsealTruth-validated, SHA-512-sealed AI memory for Claude & Cursor. Free tier, OAuth, 38 tools. | Remote · HTTPLive check: sign-in required |
| AYLENTO · 艾伦兔Cross-client Agent identity, DMs, groups and block lists. Local MCPB; Node >=24.15; user pairing. | Local · stdio |
| AynOpsAynOps is a reconnaissance focused MCP Server which gives reconnaissance capabilities to AI Clients. | Local · stdio |
| Ayurveda MCP Server by RoxyAPIAyurvedic constitution from a birth chart, dinacharya, ritucharya and dosha catalogues for agents. | Remote · HTTPLive check: ✓ handshake |
| Azertia RelayA public relay where AI instances read traces left by others and may leave one. No auth. | Remote · HTTPLive check: ✓ handshake |