Agent Hub - AI-operated public sandbox: demo data, simulated payments, no real bookings

REMOTE · HUB.VIDETION.COM · SCANNED AUG 20

Agent-to-business commerce sandbox: intents, offers, bookings. Demo data, ed25519-signed calls.

Available components

62 62 Trust /100

Trust breakdown (6 categories)

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 →

Endpoint Security57

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability64

AI-judged instruction clarity (excellent).Pass
Context-footprint check failed: tool/resource definitions use about 1943 tokens (~323/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management10

Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · hub.videtion.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http com-videtion-hub-agent-hub https://hub.videtion.com/mcp

# ~/.codex/config.toml

[mcp_servers.com-videtion-hub-agent-hub]
url = "https://hub.videtion.com/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-videtion-hub-agent-hub": {
      "type": "remote",
      "url": "https://hub.videtion.com/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add com-videtion-hub-agent-hub --url https://hub.videtion.com/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  com-videtion-hub-agent-hub:
    url: "https://hub.videtion.com/mcp"

// mcp.json

{
  "mcpServers": {
    "com-videtion-hub-agent-hub": {
      "type": "http",
      "url": "https://hub.videtion.com/mcp"
    }
  }
}

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

Changelog Show cosmetic changes

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.

19 Aug 26 +7
- Tool “approve_pending” rewrote its description, which is the text the model reads security
- Tool “confirm_booking” rewrote its description, which is the text the model reads security
- Tool “hold_slot” rewrote its description, which is the text the model reads security
- Tool “list_offers” rewrote its description, which is the text the model reads security
- Tool “register_agent” rewrote its description, which is the text the model reads security
- Tool “send_intent” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Schema quality: fair → excellent functional
- “approve_pending” reworded the description of “agent_id” cosmetic
- “approve_pending” reworded the description of “nonce” cosmetic
- “approve_pending” reworded the description of “payload” cosmetic
- “approve_pending” reworded the description of “signature” cosmetic
- “approve_pending” reworded the description of “timestamp” cosmetic
- “confirm_booking” reworded the description of “agent_id” cosmetic
- “confirm_booking” reworded the description of “nonce” cosmetic
- “confirm_booking” reworded the description of “payload” cosmetic
- “confirm_booking” reworded the description of “signature” cosmetic
- “confirm_booking” reworded the description of “timestamp” cosmetic
- “hold_slot” reworded the description of “agent_id” cosmetic
- “hold_slot” reworded the description of “nonce” cosmetic
- “hold_slot” reworded the description of “payload” cosmetic
- “hold_slot” reworded the description of “signature” cosmetic
- “hold_slot” reworded the description of “timestamp” cosmetic
- “list_offers” reworded the description of “agent_id” cosmetic
- “list_offers” reworded the description of “nonce” cosmetic
- “list_offers” reworded the description of “payload” cosmetic
- “list_offers” reworded the description of “signature” cosmetic
- “list_offers” reworded the description of “timestamp” cosmetic
- “register_agent” reworded the description of “agent_id” cosmetic
- “register_agent” reworded the description of “nonce” cosmetic
- “register_agent” reworded the description of “payload” cosmetic
- “register_agent” reworded the description of “signature” cosmetic
- “register_agent” reworded the description of “timestamp” cosmetic
- “send_intent” reworded the description of “agent_id” cosmetic
- “send_intent” reworded the description of “nonce” cosmetic
- “send_intent” reworded the description of “payload” cosmetic
- “send_intent” reworded the description of “signature” cosmetic
- “send_intent” reworded the description of “timestamp” cosmetic
18 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
17 Aug 26 55

First indexed and scored.

Show 2 earlier entries Hide earlier entries

Diagnostics

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 20 Aug 2026 · Probed https://hub.videtion.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=hub.videtion.com	CN=YR1,O=Let's Encrypt,C=US	13 Aug 2026	11 Nov 2026	RSA 4096	SHA256-RSA	50faf2ac1621a1b4601875cf49bae488292
SANs: hub.videtion.com
CN=YR1,O=Let's Encrypt,C=US (CA)	CN=Root YR,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	RSA 2048	SHA256-RSA	a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA)	CN=ISRG Root X1,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	RSA 4096	SHA256-RSA	f24b6d17f9d9ad7cb1c9fea78782699f

DNSSEC insecure

Validation of hub.videtion.com. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
com.	present	19718	13	Verified
videtion.com.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://hub.videtion.com/mcp	Verified	200
http (plaintext)	http://hub.videtion.com/mcp	HTTPS enforced	302	https://hub.videtion.com/mcp

MCP tools · 6 exposed · ~1,943 tokens

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.

Tool Tokens

approve_pending ~272

STEP 5b, only when confirm_booking answered PENDING_APPROVAL. Finalizes that approval once the seller side has decided. payload = { approval_id } (from the confirm_booking response). SIDE EFFECTS: settles the booking into its final state. Calling it before the decision exists is rejected — this tool does not grant the approval, it collects the outcome.

Input Output Examples

Name	Type	Req	Description
agent_id	string	yes	The agent_id returned by register_agent. Call that tool first; it is the only one needing no credentials.
nonce	string	yes	Single-use random string, 1..256 chars (32 hex recommended). A nonce this agent has used before is rejected as a replay (401).
payload	–	–	Tool-specific arguments — see this tool's description for the exact shape. Covered by the signature.
signature	string	yes	Hex-encoded ed25519 signature over the RFC 8785 (JCS) canonical JSON of exactly {payload, agent_id, nonce, timestamp} — the whole envelope minus this field. Sign with the private key matching the pub…
timestamp	number	yes	Epoch MILLISECONDS (Date.now()), not seconds. Must be within +/-60 s of server time, else 401 stale timestamp.

No output schema declared.

No examples provided.

confirm_booking ~315

STEP 5, the committing call — turns a hold into a booking. payload = { hold_id } (from hold_slot). Your envelope signature IS the buyer signature on the resulting booking, so this is a non-repudiable act: do not call it speculatively. SIDE EFFECTS: returns either a CONFIRMED booking, or PENDING_APPROVAL + { approval_id } when the seller policy demands a human — in that case finish with approve_pending. Requires the booking.confirm capability. Sandbox: bookings are against demo inventory and bind nobody in the real world.

Input Output Examples

Name	Type	Req	Description
agent_id	string	yes	The agent_id returned by register_agent. Call that tool first; it is the only one needing no credentials.
nonce	string	yes	Single-use random string, 1..256 chars (32 hex recommended). A nonce this agent has used before is rejected as a replay (401).
payload	–	–	Tool-specific arguments — see this tool's description for the exact shape. Covered by the signature.
signature	string	yes	Hex-encoded ed25519 signature over the RFC 8785 (JCS) canonical JSON of exactly {payload, agent_id, nonce, timestamp} — the whole envelope minus this field. Sign with the private key matching the pub…
timestamp	number	yes	Epoch MILLISECONDS (Date.now()), not seconds. Must be within +/-60 s of server time, else 401 stale timestamp.

No output schema declared.

No examples provided.

hold_slot ~295

STEP 4. Reserves the slot behind an offer so nobody else takes it while you decide. payload = { offer_id } (from list_offers). SIDE EFFECTS: takes exclusive, EXPIRING ownership of a real inventory slot — returns { hold_id } with an expires_at (epoch ms). Let it lapse and the slot returns to the pool; this is not yet a booking. Requires the slot.hold capability, which self-registered buyers get by default.

Input Output Examples

Name	Type	Req	Description
agent_id	string	yes	The agent_id returned by register_agent. Call that tool first; it is the only one needing no credentials.
nonce	string	yes	Single-use random string, 1..256 chars (32 hex recommended). A nonce this agent has used before is rejected as a replay (401).
payload	–	–	Tool-specific arguments — see this tool's description for the exact shape. Covered by the signature.
signature	string	yes	Hex-encoded ed25519 signature over the RFC 8785 (JCS) canonical JSON of exactly {payload, agent_id, nonce, timestamp} — the whole envelope minus this field. Sign with the private key matching the pub…
timestamp	number	yes	Epoch MILLISECONDS (Date.now()), not seconds. Must be within +/-60 s of server time, else 401 stale timestamp.

No output schema declared.

No examples provided.

list_offers ~285

STEP 3. Reads the offers sellers made against your own intent, cheapest first. payload = { intent_id } (the id returned by send_intent). Read-only, no side effects. You can only list offers on intents your own agent created. Each offer carries offer_id, price, currency, slot and expires_at (epoch ms) — expired offers cannot be held, so read the slot before calling hold_slot.

Input Output Examples

Name	Type	Req	Description
agent_id	string	yes	The agent_id returned by register_agent. Call that tool first; it is the only one needing no credentials.
nonce	string	yes	Single-use random string, 1..256 chars (32 hex recommended). A nonce this agent has used before is rejected as a replay (401).
payload	–	–	Tool-specific arguments — see this tool's description for the exact shape. Covered by the signature.
signature	string	yes	Hex-encoded ed25519 signature over the RFC 8785 (JCS) canonical JSON of exactly {payload, agent_id, nonce, timestamp} — the whole envelope minus this field. Sign with the private key matching the pub…
timestamp	number	yes	Epoch MILLISECONDS (Date.now()), not seconds. Must be within +/-60 s of server time, else 401 stale timestamp.

No output schema declared.

No examples provided.

register_agent ~387

STEP 1 of the buy flow, and the ONLY tool that needs no existing credentials — start here. Registers a new buyer agent by proof-of-possession: sign the envelope with the private key matching payload.public_key. payload = { public_key: <ed25519 public key, 64 hex chars>, principal?: { type?: "user", name?: string } }. SIDE EFFECTS: creates a persistent agent record and issues a passport valid 30 days; returns { ok: true, agent_id, passport }. Grants buyer capabilities only (catalog.read, slot.hold, booking.confirm) — business principals, business_id and seller capabilities are refused (403). Rate limit: 20 registrations/hour/IP. This is a public sandbox with demo inventory; nothing here is a real-world commitment. Protocol: https://hub.videtion.com/spec

Input Output Examples

Name	Type	Req	Description
agent_id	string	yes	You do not have an agent_id yet — pass your public_key here. The value is ignored by registration, but it must be non-empty and must be the exact string you included when signing.
nonce	string	yes	Single-use random string, 1..256 chars (32 hex recommended). A nonce this agent has used before is rejected as a replay (401).
payload	–	–	Tool-specific arguments — see this tool's description for the exact shape. Covered by the signature.
signature	string	yes	Hex-encoded ed25519 signature over the RFC 8785 (JCS) canonical JSON of exactly {payload, agent_id, nonce, timestamp} — the whole envelope minus this field. Sign with the private key matching the pub…
timestamp	number	yes	Epoch MILLISECONDS (Date.now()), not seconds. Must be within +/-60 s of server time, else 401 stale timestamp.

No output schema declared.

No examples provided.

send_intent ~389

STEP 2. States what you want to buy; sellers answer it with offers. Requires a registered agent_id. payload = a structured Intent: { type: string, location: string, product?: object, service?: string, availability?: { before?: string, after_time?: string }, budget?: { currency: <3-letter>, max: number } }. The demo inventory answers this exact one: { type: "car_tires", location: "Wroclaw", product: { width: 225, profile: 45, diameter: 18, season: "winter", quantity: 4 }, service: "installation", budget: { currency: "PLN", max: 3000 } }. SIDE EFFECTS: persists the intent and exposes it to seller agents for matching; returns { intent_id }. Default limit: 100 intents/hour/agent. Natural-language intents are REST-only — MCP takes structured payloads.

Input Output Examples

Name	Type	Req	Description
agent_id	string	yes	The agent_id returned by register_agent. Call that tool first; it is the only one needing no credentials.
nonce	string	yes	Single-use random string, 1..256 chars (32 hex recommended). A nonce this agent has used before is rejected as a replay (401).
payload	–	–	Tool-specific arguments — see this tool's description for the exact shape. Covered by the signature.
signature	string	yes	Hex-encoded ed25519 signature over the RFC 8785 (JCS) canonical JSON of exactly {payload, agent_id, nonce, timestamp} — the whole envelope minus this field. Sign with the private key matching the pub…
timestamp	number	yes	Epoch MILLISECONDS (Date.now()), not seconds. Must be within +/-60 s of server time, else 401 stale timestamp.

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

17 Aug 20 Aug