目录 / axiom
MCP
鉴权未知
未评级
已上架
axiom
该来源不提供完整文件导出(国内平台多为平台内托管),仅存元数据与原链
接入信息
- 传输形态
- http
- 鉴权方式
- 鉴权未知
- 端点
https://axiom--christiangeorgelucas.run.tools
鉴权方式未标注,请核对官方文档后再接入——不要直接使用以下片段
{
"mcpServers": {
"axiom": {
"url": "https://axiom--christiangeorgelucas.run.tools"
}
}
}
能力清单
| 工具 | 说明 |
|---|---|
| axiom_get_source | Return a published node's handler SOURCE CODE plus a pointer to its full repository (source_url, pinned to the exact published commit) — so you can verify what a node really does before invoking it. Use after axiom_inspect (which returns only the input/output schema): the snippet is the handler body, and source_url is the escape hatch to read code it calls into. For an Instance node the source is the inherited Generic implementation (generic_package labels the origin). |
| axiom_inspect | Return the compiled input/output JSON Schema for a published node or compiled flow — the schema an invoke payload must satisfy. |
| axiom_invoke | Synchronously invoke a published node or compiled flow with a JSON input (sync-only). Resolves the target by id, alias, or a pinned name — a flow may be given as its name, "<handle>/<flow-name>[@<version>]", and a node as "<handle>/<package>/<Node>[@<version>]"; omit @version to run the newest published one. A target that needs human approval (HITL), that streams (a pipeline flow or node), or that cannot finish within the sync budget (~30s) returns a clear "not callable" result rather than running async or returning a truncated answer. |
| axiom_list_my_tools | List your pinned nodes and flows (the targets that surface as typed tools). Optionally filter by kind. |
| axiom_pin | Pin a node or flow as a favorite. Pinned targets surface as first-class typed MCP tools on tools/list (with a derived input schema). A pin targets a node OR a flow. |
| axiom_propose | Propose a new marketplace artifact (a package, node, or flow) that does NOT exist yet. Use this the moment a task needs a node or flow the catalog doesn't have, or an existing one was awkward to use and a better shape would help — after you've searched (axiom_search) and confirmed nothing fits. Your proposal is high-signal demand: you hit the gap doing real work. Give a concrete summary (what it should do, its inputs and outputs); set target_ref to point at an existing artifact the proposal is against (e.g. add a capability to a package). This does NOT file bug reports or feature requests about the product — only requests for catalog artifacts. |
| axiom_search | Search the Axiom catalog for published nodes or compiled flows (tenant-scoped: public + your own + entitled). Describe what you want in plain language — search is hybrid (meaning + keywords) by default. Results carry the invocable id (node_id / graph_id) to pipe into axiom_inspect or axiom_invoke. |
| axiom_unpin | Remove a pinned node or flow favorite. |
纠错与举报(发现条目失效、署名有误或涉及侵权?)
提交举报 / 纠错
侵权举报经核验成立后,我们会即时下线该条目并删除已存的内容副本。