Other · Remote MCP server
AxenomIA AX-SCI-001 - Scientific Novelty & Evidence
Traceable scientific novelty and evidence assessment with source-linked results and a human gate.
Visit AxenomIA AX-SCI-001 - Scientific Novelty & Evidence's website
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Perlita2013/ax-sci-001- Version
- 1.0.1
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-30
- Updated
- 2026-09-30
- Publisher
- Perlita2013 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Perlita2013) · how
- Website
- axenomia.cl
- Repository
- github.com/Perlita2013/lore0-cloud
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://axenomia.cl/mcp | Authorization (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
- AxenomIA AX-SCI-001 1.0.1 · protocol 2025-06-18
- Tools discovered
- 3:
axenomia_agent_passport,axenomia_human_review_gate,ax_sci_001_assess_evidence - Checked on
- 2026-10-05
How to connect AxenomIA AX-SCI-001 - Scientific Novelty & Evidence
AxenomIA AX-SCI-001 - Scientific Novelty & Evidence is a remote MCP server: there is nothing to install. Its endpoint is https://axenomia.cl/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 (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 |
|---|---|
| Awx MCP ServerControl AWX/Ansible Tower through natural language - 49 tools for automation. | Local · stdio |
| Axcient MCPEvery x360Recover endpoint, plus the fleet-wide backup-health answers the API alone can't give. | Local · stdio |
| Axcient x360RecoverMCP server for Axcient x360Recover - BCDR clients, devices, jobs, vaults, and appliances. | Local · stdio |
| Axcient x360RecoverMCP server for Axcient x360Recover - BCDR clients, devices, jobs, vaults, and appliances. | Local · stdio |
| 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 |