Agentic Keychain
REMOTE · AGENTICKEYCHAIN.COM
Agent Skill ROI Registry & Benchmarking. It sells skills for log triage and repository mapping.
Available components
Last scanned (21 hours ago)
Scores higher than 12% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 503. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (5)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 10 Nov 26 −61
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 0
- Tool coverage: 73% → 100% ▲ functional
- “compare_capabilities” reworded the description of “capabilities” cosmetic
- “compare_capabilities” reworded the description of “constraints” cosmetic
- “evaluate_capability” reworded the description of “constraints” cosmetic
- “report_outcome” reworded the description of “baseline_cost_estimate_usd” cosmetic
- “report_outcome” reworded the description of “cost_usd” cosmetic
- “report_outcome” reworded the description of “latency_ms” cosmetic
- “report_outcome” reworded the description of “success” cosmetic
- “report_outcome” reworded the description of “tokens_in” cosmetic
- “report_outcome” reworded the description of “tokens_out” cosmetic
- “report_outcome” reworded the description of “tool_calls” cosmetic
- “report_outcome” reworded the description of “used_capability” cosmetic
- “resolve_task” reworded the description of “constraints” cosmetic
- “search_capabilities” reworded the description of “limit” cosmetic
- 3 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “compare_capabilities” rewrote its description, which is the text the model reads security
- Tool “estimate_roi” rewrote its description, which is the text the model reads security
- Tool “evaluate_capability” rewrote its description, which is the text the model reads security
- Tool “get_benchmark” rewrote its description, which is the text the model reads security
- Tool “get_capability” rewrote its description, which is the text the model reads security
- Tool “get_provenance” rewrote its description, which is the text the model reads security
- Tool “get_quote” rewrote its description, which is the text the model reads security
- Tool “report_outcome” rewrote its description, which is the text the model reads security
- Tool “search_capabilities” rewrote its description, which is the text the model reads security
- Tool “unlock_capability” rewrote its description, which is the text the model reads security
- Schema quality: 140 → 257 ▼ functional
- Server version: 0.1.0 → 0.2.0 functional
- New tool “resolve_task” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://agentickeychain.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agentickeychain.com | CN=YE2,O=Let's Encrypt,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6f6071f110d631e97853551202e517cf647 |
| SANs: agentickeychain.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of agentickeychain.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| agentickeychain.com. | DS published | 60603 | 13 | Verified |
| agentickeychain.com. | Verified address RRset verified with the apex keys |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 503 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | same-origin |
| permissions-policy | interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agentickeychain.com/mcp | HTTP error | 503 | |
| http (plaintext) | http://agentickeychain.com/mcp | HTTPS enforced | 308 | https://agentickeychain.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_capabilities Compare capabilities ~326
Assess 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 ids and want each one's decision, reasons and offer in one answer. Not for: finding candidates (search_capabilities) or a single capability (evaluate_capability). Input: the capability ids, plus the optional task, model, expected_runs, baseline_cost_estimate_usd, context and constraints that evaluate_capability reads. Output: ak.comparison.v1 with the results ranked by decision, lower-bound net saving, relevance and capability id, each with its reasons and an ak.offer.v1 offer.
| Name | Type | Req | Description |
|---|---|---|---|
| baseline_cost_estimate_usd | number | – | What one run of this task costs you today without the capability, in USD. |
| capabilities | array | yes | Two to five capabilities to compare, each as an id, ak:// URI or slug. |
| constraints | object | – | Limits you set for the answer; a capability outside them is reported as blocked, with the reason code. |
| context | object | – | Facts about your situation, keyed by the capability's parameter names (e.g. log_lines). |
| expected_runs | integer | – | How many times you expect to perform this kind of task. |
| model | string | – | The model you run on, e.g. claude-sonnet-5. Savings are reported only for measured models. |
| task | string | – | Plain description of the task you are about to do (at most 4000 characters). |
No output schema declared.
No examples provided.
estimate_roi Estimate return on a capability ~262
Per 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 economics on each model the registry measured. Not for: a use-or-not answer for a task (evaluate_capability) or several candidates (compare_capabilities). Input: a capability id; add model to keep one model, and expected_runs with baseline_cost_estimate_usd for an estimate at your scale. Output: ak.roi.v1 with one economics entry per measured model; break-even runs is null when the interval does not show a saving, and your estimate is left out where success is not accepted or your baseline lies outside the measured range.
| Name | Type | Req | Description |
|---|---|---|---|
| baseline_cost_estimate_usd | number | – | What one run of this task costs you today without the capability, in USD. |
| capability | string | yes | Capability id (ak:publisher:name or ak:publisher:name:x.y.z), ak:// URI or slug. |
| expected_runs | integer | – | How many times you expect to perform this kind of task. |
| model | string | – | The model you run on, e.g. claude-sonnet-5. Savings are reported only for measured models. |
No output schema declared.
No examples provided.
evaluate_capability Should I use a capability for this task? ~425
Decide 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 with the arithmetic; name a capability to weigh only that one, or leave it out and the registry weighs its closest matches. Not for: one short answer without the arithmetic (resolve_task), a plain list of matches (search_capabilities), two to five named candidates side by side (compare_capabilities), or the break-even figures of one capability without a task (estimate_roi). Input: a plain task description; give model, expected_runs and baseline_cost_estimate_usd for a money estimate, and context for the conditions the capability declares. Output: ak.evaluation.v1 with decision, reasons, expected effect, price, confidence, operator_message, evaluation_id, next steps and an ak.offer.v1 offer (status, next_action, economics, the four evidence kinds listed apart). do_not_recommend is a normal answer.
| Name | Type | Req | Description |
|---|---|---|---|
| baseline_cost_estimate_usd | number | – | What one run of this task costs you today without the capability, in USD. |
| budget_policy | object | – | Your operator's spending policy; the answer says whether a purchase fits it. Every purchase still needs human approval. |
| capability | string | – | Capability id (ak:publisher:name or ak:publisher:name:x.y.z), ak:// URI or slug. |
| constraints | object | – | Limits you set for the answer; a capability outside them is reported as blocked, with the reason code. |
| context | object | – | Facts about your situation, keyed by the capability's parameter names (e.g. log_lines). |
| expected_runs | integer | – | How many times you expect to perform this kind of task. |
| model | string | – | The model you run on, e.g. claude-sonnet-5. Savings are reported only for measured models. |
| task | string | yes | Plain description of the task you are about to do (at most 4000 characters). |
No output schema declared.
No examples provided.
get_benchmark Get benchmark evidence ~161
Registry-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 runs, model, fixtures, method) or want to check them yourself. Not for: an answer for your task (evaluate_capability) or artifact hashes and the log proof (get_provenance). Input: a capability id, ak:// URI or slug. Output: ak.benchmark.v1 with the evidence, the publisher claims, the attestations, the method and the limitations; publisher claims never decide anything.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | yes | Capability id (ak:publisher:name or ak:publisher:name:x.y.z), ak:// URI or slug. |
No output schema declared.
No examples provided.
get_capability Get a capability card ~169
The 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 capability and want its facts, or want to check the conditions an evaluation asked about. Not for: an answer for your task (evaluate_capability) or the full benchmark records (get_benchmark). Input: a capability id, ak:// URI or slug, from a search, an evaluation or a page. Output: ak.capability.v1 with the card fields, parameters, versions, terms, evidence, trust and links.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | yes | Capability id (ak:publisher:name or ak:publisher:name:x.y.z), ak:// URI or slug. |
No output schema declared.
No examples provided.
get_provenance Get provenance ~146
Artifact 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 published and signed. Not for: benchmark results (get_benchmark) or the card (get_capability). Input: a capability id, ak:// URI or slug. Output: ak.provenance.v1 with the hashes, the attestations, an RFC 9162 inclusion proof against the signed tree head, the trust checks and the keys URL.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | yes | Capability id (ak:publisher:name or ak:publisher:name:x.y.z), ak:// URI or slug. |
No output schema declared.
No examples provided.
get_quote Get a price quote ~196
A 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 checkout link of a capability that is for sale, for example after an evaluation answered recommend. Not for: deciding whether a capability is worth it (evaluate_capability); a free capability needs no quote. Input: the capability id and, if you evaluated first, the evaluation_id, which links the quote to that evaluation. Output: a quote_id and signed claims bound to the capability version, price, currency, terms and expiry, the checkout link and the unlock request; the price comes from the registry record only.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | yes | Capability id (ak:publisher:name or ak:publisher:name:x.y.z), ak:// URI or slug. |
| evaluation_id | string | – | The evaluation_id from evaluate_capability, if you evaluated first. |
No output schema declared.
No examples provided.
report_outcome Report an outcome ~391
Report 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 capability, or decided not to, and can say whether the task succeeded. Not for: questions about a capability (get_capability, get_benchmark). Input: the capability id and success; add evaluation_id or purchase_ref to link the report, the optional token, tool-call, latency and cost counts, and failure_reason only with success false. Output: whether the report was stored, its label and, for a failed paid capability, the remedy policy.
| Name | Type | Req | Description |
|---|---|---|---|
| baseline_cost_estimate_usd | number | – | What one run of this task costs you without the capability, in USD. |
| capability | string | yes | Capability id (ak:publisher:name or ak:publisher:name:x.y.z), ak:// URI or slug. |
| cost_usd | number | – | What the run cost you in USD. |
| evaluation_id | string | – | The evaluation_id from evaluate_capability, if you evaluated first. |
| failure_reason | string | – | Only with success false. |
| latency_ms | integer | – | Wall-clock time of the run in milliseconds. |
| model | string | – | The model you run on, e.g. claude-sonnet-5. Savings are reported only for measured models. |
| purchase_ref | string | – | The purchase_ref from unlock_capability, if you bought the capability. |
| success | boolean | yes | Whether the task reached its goal. |
| tokens_in | integer | – | Input tokens the run used. |
| tokens_out | integer | – | Output tokens the run used. |
| tool_calls | integer | – | Tool calls the run made. |
| used_capability | boolean | – | Whether the capability was used in this run; false reports a run done without it. |
No output schema declared.
No examples provided.
resolve_task Is there a capability worth using for this task? ~387
Describe 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 capability name, and want one decision word (use, do_not_use, use_free_alternative, insufficient_evidence, blocked_by_constraints or no_match) with its reason codes. Not for: the full arithmetic, the offer and the operator message (evaluate_capability with the same inputs), a plain list of matches (search_capabilities) or a capability you can already name (get_capability). Input: task, plus optional model, expected_runs, baseline_cost_estimate_usd, context and constraints; any other field is refused with the allowed list. Output: ak.resolve.v1 with decision, capability id, reason codes, the measured saving per run with its interval or null, the estimate at your own baseline with its break-even runs or null, confidence, evidence label, price, free alternatives, next action, evaluation_id and the tool that gives the detail. do_not_use and no_match are normal answers.
| Name | Type | Req | Description |
|---|---|---|---|
| baseline_cost_estimate_usd | number | – | What one run of this task costs you today without the capability, in USD. |
| constraints | object | – | Limits you set for the answer; a capability outside them is reported as blocked, with the reason code. |
| context | object | – | Facts about your situation, keyed by the capability's parameter names (e.g. log_lines). |
| expected_runs | integer | – | How many times you expect to perform this kind of task. |
| model | string | – | The model you run on, e.g. claude-sonnet-5. Savings are reported only for measured models. |
| task | string | yes | Plain description of the task you are about to do (at most 4000 characters). |
No output schema declared.
No examples provided.
search_capabilities Search capabilities ~177
Search 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 you know part of a name. Not for: deciding whether one fits your task (resolve_task, or evaluate_capability for the full arithmetic) or reading a capability you can already name (get_capability). Input: search words, at most 500 characters; no earlier call is needed. Output: ak.search.v1 with id, name, summary, relevance, state, price and the strongest evidence label of each result, and no decision.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many results to return, from 1 to 50 (default 10). |
| query | string | yes | Search words (at most 500 characters). |
No output schema declared.
No examples provided.
unlock_capability Unlock a purchased capability ~232
Exchange 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 at /legal/privacy/. Repeating it with the same key is safe and never charges. Use when: your operator completed the hosted checkout and gave you the license key. Not for: a price or a checkout link (get_quote); a free capability downloads from its page. Input: the capability id and the license key, plus quote_id and evaluation_id when you have them. Output: a signed entitlement, a purchase_ref for report_outcome and the download link.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | yes | Capability id (ak:publisher:name or ak:publisher:name:x.y.z), ak:// URI or slug. |
| evaluation_id | string | – | The evaluation_id from evaluate_capability, if you evaluated first. |
| license_key | string | yes | License key from the checkout. |
| quote_id | string | – | The quote_id of the quote the purchase followed, if any (links the records; never changes the price). |
No output schema declared.
No examples provided.
How do I install the Agentic Keychain MCP server?
Agentic Keychain is a hosted endpoint at https://agentickeychain.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · agentickeychain.com
claude mcp add --transport http com-agentickeychain-agentic-keychain 'https://agentickeychain.com/mcp'
What is the Agentic Keychain MCP server?
Agentic Keychain is an MCP server listed in the public MCP registry as com.agentickeychain/agentic-keychain. Agent Skill ROI Registry & Benchmarking. It sells skills for log triage and repository mapping. This page covers its hosted endpoint (https://agentickeychain.com/mcp).
Is the Agentic Keychain MCP server safe to use?
Agentic Keychain scores 26 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Agentic Keychain MCP server expose?
Agentic Keychain exposes 11 tools: resolve_task, evaluate_capability, search_capabilities, compare_capabilities, estimate_roi, and 6 more. Their descriptions and schemas cost roughly 2,872 tokens of context every time the server is loaded.
Does the Agentic Keychain MCP server require authentication?
Its publisher declares no required credentials for Agentic Keychain. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Agentic Keychain MCP server still maintained?
Agentic Keychain is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Agentic Keychain MCP server?
VerifyMCP ran 5 checks on Agentic Keychain, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Agentic Keychain: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.