# Salesforce AgentForce CKG (remote · ckg-agentforce.onrender.com)

Salesforce AgentForce knowledge graph — 40 nodes, Einstein Trust Layer, 11x fewer tokens than RAG.

- Trust score: 59/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `ckg-agentforce.onrender.com`: 59/100 (this document), [markdown](https://verifymcp.io/servers/yarmoluk-ckg-agentforce/ckg-agentforce-2.md), [page](https://verifymcp.io/servers/yarmoluk-ckg-agentforce/ckg-agentforce-2)
- pypi · `ckg-agentforce`: 19/100, [markdown](https://verifymcp.io/servers/yarmoluk-ckg-agentforce/ckg-agentforce.md), [page](https://verifymcp.io/servers/yarmoluk-ckg-agentforce/ckg-agentforce)

## Channel facts

- Endpoint: `https://ckg-agentforce.onrender.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.10.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (poor).
  - Context-footprint check failed: tool/resource definitions use about 1591 tokens (~132/item across 12 items; 10 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http yarmoluk-ckg-agentforce https://ckg-agentforce.onrender.com/mcp
```

### Codex

```toml
[mcp_servers.yarmoluk-ckg-agentforce]
url = "https://ckg-agentforce.onrender.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "yarmoluk-ckg-agentforce": {
      "type": "remote",
      "url": "https://ckg-agentforce.onrender.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add yarmoluk-ckg-agentforce --url https://ckg-agentforce.onrender.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  yarmoluk-ckg-agentforce:
    url: "https://ckg-agentforce.onrender.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "yarmoluk-ckg-agentforce": {
      "type": "http",
      "url": "https://ckg-agentforce.onrender.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 59, 0)

- [functional regression] Schema quality: 111 → 132
- [functional] New tool “query_intersect”

### 2026-08-01 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 58, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 56, +42)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 14)

First indexed and scored.

## MCP tools (10)

### `list_concepts` (~21 tokens)

List all 40 AgentForce concepts in this knowledge graph.

Output parameters:

- `result` (string)

### `search_concepts` (~51 tokens)

Find AgentForce concepts by keyword.

Args:
    query: Search term — e.g. 'resolution', 'trust', 'grounding', 'action', 'NIM'.

Input parameters:

- `query` (string, required)

Output parameters:

- `result` (string)

### `query_ckg` (~112 tokens)

Traverse the AgentForce knowledge graph from any concept.

Returns prerequisites (what this concept needs) and dependents (what it enables).
Every relationship traces to an authoritative Salesforce doc URL.

Args:
    concept: Concept name — e.g. 'Autonomous Resolution', 'Einstein Trust Layer',
             'Service Agent', 'Grounding', 'NVIDIA NIM'.
    depth:   Traversal depth 1–5 (default 3).

Input parameters:

- `concept` (string, required)
- `depth` (integer)

Output parameters:

- `result` (string)

### `get_prerequisites` (~72 tokens)

Return the full ordered prerequisite chain for an AgentForce concept.

Shows everything the concept depends on — the complete upstream path.

Args:
    concept: Target concept — e.g. 'Autonomous Resolution', 'Multi-LoRA Serving',
             'Custom Actions', 'Semantic Retrieval'.

Input parameters:

- `concept` (string, required)

Output parameters:

- `result` (string)

### `resolution_path` (~47 tokens)

Trace the exact path that determines an AgentForce autonomous resolution event.

This is the $2/resolution billing path — what the agent must traverse correctly
to resolve autonomously without human handoff.

Output parameters:

- `result` (string)

### `route_query` (~182 tokens)

Route an AgentForce question to the optimal model and reasoning approach via graph depth.

The CKG graph IS the router. AgentForce dependency chains (e.g. Einstein Trust Layer →
Data Cloud → NVIDIA NIM → Resolution Criteria) have typed hops that signal reasoning
complexity deterministically. No heuristic: the graph decides.

Routing table:
  hop_depth 1  → haiku  · direct        (simple concept lookup)
  hop_depth 2  → sonnet · generic_cot   (moderate chain)
  hop_depth 3+ → opus   · sparql_cot    (deep dependency, structured reasoning)

Args:
    question: Concept name or natural language question about Salesforce AgentForce.

Returns:
    model_tier + reasoning_approach + why + context subgraph to inject before LLM call.

Input parameters:

- `question` (string, required)

Output parameters:

- `result` (string)

### `verify_source` (~139 tokens)

Return the source URL and content hash for an AgentForce concept node.

Audit chain:
    edge answer → graph commit → source_hash → source_url (fetch hint)

Verification:
    curl -s <source_url> | sha256sum
    # compare output to source_hash

Args:
    concept: Concept label (partial match supported).
    receipt: If True, also return a signed BoundaryAttest receipt envelope
             (experimental-interop-v0.1) binding concept_label + source_url
             + source_hash + timestamp to this server's ed25519 session key.

Input parameters:

- `concept` (string, required)
- `receipt` (boolean)

Output parameters:

- `result` (string)

### `export_benchmark_receipt` (~119 tokens)

Generate a signed BoundaryAttest receipt for the agentforce CKG benchmark result.

Produces a `ckg.benchmark_result.exported` claim signed with this server's Ed25519
session key. Any party holding the public key can verify the signature over the canonical
JSON claim. Implements GuardrailDecisionV1 · experimental-interop-v0.1.

Result: F1 0.471 over 30 queries · ckg-benchmark v0.6.2 · 4× over RAG baseline (0.123).

Output parameters:

- `result` (string)

### `evaluate_trust_chain` (~205 tokens)

Return a machine-readable JSON trust chain + ROI analysis + payment recommendation.

Designed for autonomous agent consumption. The agent reads the JSON, evaluates the
ROI gate, selects the cheapest positive-ROI payment option, and purchases autonomously
if budget is pre-authorized.

Trust chain closes the audit gap that RAG cannot:
  source_hashes  → SHA-256 of source docs (what was known at extraction time)
  graph_hash     → SHA-256 of the installed graph file (what is declared now)
  signer_key_id  → Ed25519 public key fingerprint (who is attesting)
  benchmark_receipt → BoundaryAttest-signed F1 claim (cryptographic performance proof)
  scitt_status   → SCITT ledger submission status (public audit anchor)

ROI gate: if total_value_per_call_usd > payment_option.price_per_call_usd → autonomous_pay = true.

Returns: JSON string (schema: ckg-trust-chain-v1).

Output parameters:

- `result` (string)

### `query_intersect` (~367 tokens)

Answer a conjunctive query: concepts reachable from EVERY anchor at once (A AND B).

query_ckg walks outward from one concept. This intersects the reachable sets of two or
more, which is the shape of most real questions — "the component that satisfies A AND
applies to B". Neither anchor alone answers it; the answer lives in the overlap.

Every branch is an exact set of declared edges, so the intersection is exact. A concept
appears only if a declared path reaches it from each anchor. A relation missing from the
graph produces an empty result, never a guess.

Args:
    branches: Two or more branches. Either a bare anchor ("TensorRT-LLM"), which takes
        everything within `depth` hops, or an anchor plus an explicit relation path using
        '>' ("TensorRT-LLM > REQUIRES > ENABLES"), where each relation replaces the
        frontier. '*' matches any relation. Mix both forms freely.
    depth: Hops for bare-anchor branches, 1-5 (default 2). Ignored for explicit paths.
    direction: 'out' follows dependencies, 'in' follows them backwards, 'both' (default).
    mode: 'AND' (default) intersects branches; 'OR' unions them.
    limit: Max concepts listed, 1-200 (default 40). The true count is always shown.

Returns:
    Markdown with the query plan and its per-step set sizes, then the answer set with
    taxonomy tags. Reports which branch was empty when the intersection is empty.

Input parameters:

- `branches` (array, required)
- `depth` (integer)
- `direction` (string)
- `limit` (integer)
- `mode` (string)

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/yarmoluk-ckg-agentforce/ckg-agentforce-2#diagnostics

## Score history

- 2026-08-03: 59
- 2026-08-02: 59
- 2026-08-01: 59
- 2026-07-31: 58
- 2026-07-30: 56
- 2026-07-29: 14

## Links

- Remote endpoint: https://ckg-agentforce.onrender.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/yarmoluk-ckg-agentforce/ckg-agentforce-2/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/yarmoluk-ckg-agentforce/ckg-agentforce-2/changelog.json
- HTML version of this page: https://verifymcp.io/servers/yarmoluk-ckg-agentforce/ckg-agentforce-2