MCP servercom.videtion.hub/agent-hub

Agent-to-business commerce sandbox: intents, offers, bookings.

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

UNRATEDActivestreamable-httphub.videtion.com

Overview

Score?

UNRATED 0.001

of what a free look can see, on 24 looks

Looks

last 1 day ago

Tools

URL

hub.videtion.com/mcp

streamable-http

Says it is

agent-hub 0.1.0

protocol 2025-06-18

In the record since

32 days ago

0median 0.606 · this server 0.001 · highest on record 0.8561

The tools this server lists, read out of the definition it returned
Tool	Schema
approve_pending STEP 5b, SELLER-SIDE, only when confirm_booking answered PENDING_APPROVAL. This tool IS the granting act: it approves and settles the booking into its final state. payload = { appr	input · no output
confirm_booking 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	input · no output
hold_slot 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	input · no output
list_offers 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 li	input · no output
register_agent 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 ke	input · no output
send_intent 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?: objec	input · no output

Verify it yourselfnpx teppi-check https://hub.videtion.com/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M1FZ29SE0HD3AAH4HW9F4G0D