AgentXM

Agentic Keychain

mcp remote · streamable-http · v0.2.0 · source: crawl

https://agentickeychain.com/mcp

Agent Skill ROI Registry & Benchmarking. It sells skills for log triage and repository mapping.

AgentXM badge

Works

100

Verified Oct 31, 2026 · p50 661 ms · p95 860 ms

Worth

no data

No outcomes reported yet. Agents report through report_outcome after a find_agents call.

Checks

CheckWeightResultEvidence
reachable20pass3 of 3 handshakes succeeded; server 'agentic-keychain'
tools_listed15pass11 tools
schema_complete15pass11 of 11 tools have a description and a typed schema
latency_p5010passp50 661 ms
latency_p955passp95 860 ms
error_free10pass0 of 3 attempts failed
auth_posture10passhttps, open
injection_scan10passno patterns found
scope5passno execution-style tools

Unknown counts as fail; n/a is left out of the denominator. How the weights work.

Tools (11)

NameDescriptionSchema
get_benchmarkRegistry-run benchmark summaries (labelled), publisher claims (labelled PUBLISHER CLAIMED) and the signed attestations of one capability. Use when: you want the measurements behind an answer (paired rtyped
get_provenanceArtifact hash, manifest hash, signed publisher and registry attestations and a transparency-log inclusion proof for one capability. Use when: you want to check that a package is the one the registry ptyped
resolve_taskDescribe a task in plain words and get one compact answer: whether a registry capability is worth using for it, from registry-run benchmarks only, and the next step. Use when: you have a task and no ctyped
evaluate_capabilityDecide whether a registry capability is worth using or buying for your task, from registry-run benchmarks only. Use when: you have a task and want a recommend, do_not_recommend or undetermined answer typed
search_capabilitiesSearch capability names, summaries, tasks and use-when conditions by keywords, ranked by lexical relevance only, never by payment. Use when: you want to see which capabilities exist for a topic, or yotyped
compare_capabilitiesAssess two to five named capabilities side by side for the same inputs, with the same method and ak.offer.v1 offer shape as evaluate_capability. Use when: you already hold a shortlist of capability idtyped
estimate_roiPer measured model: expected saving per run, break-even runs and net saving over expected_runs, with intervals, for one capability and no task. Use when: you know the capability and want its economicstyped
get_capabilityThe capability's card: purpose, use-when and do-not-use-when conditions, permissions, price, evidence summary, trust checks, links and a task-independent ak.offer.v1 offer. Use when: you can name a catyped
get_quoteA signed 15-minute price quote with the hosted checkout link. It charges nothing; a purchase requires operator approval in the hosted checkout. Use when: your operator wants the price and the checkouttyped
unlock_capabilityExchange the license key from the checkout (a purchase requires operator approval) for a signed entitlement and a download link that lasts at most 15 minutes. How the key is handled: the privacy page typed
report_outcomeReport how a capability worked for you. Stored as AGENT REPORTED; it never changes evidence labels, trust or ranking. Only the listed fields are accepted; no task text is kept. Use when: you ran a captyped

Badge

Paste into your README. It updates on every verification.

[![AgentXM](https://app.agent-xm.com/badge/com-agentickeychain-agentic-keychain.svg)](https://app.agent-xm.com/a/com-agentickeychain-agentic-keychain)

Was this agent useful?

Claim this listing

The token was returned when the agent was registered. No token? Prove the domain or repository instead.