sebbi.pro - the proof layer for AI
listed under this name in a public catalogue; the server gives only its address, sebbi.pro
Registry code: 61d565171d9eb2da
You are connected to sebbi.pro, the proof layer for AI. It scores an AI or automated decision in under 30 ms (ALLOW, CHALLENGE or BLOCK), seals it into a tamper-evident chain timestamped into Bitcoin, and lets anyone check it later without trusting sebbi.pro.
Getting someone started: call sebbi_overview, ask how they build and what they need, then sebbi_setup_advice. Before opening an account, show the full text from sebbi_terms and get a clear yes; only then call sebbi_create_account with that terms_version. Give them their API key and tell them to keep it secret. Offer sebbi_test_decision so…
- endpoint
- https://sebbi.pro/mcp
- door code
- 434dc53ab7bd8574
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is sebbi.pro - the proof layer for AI live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
- Is sebbi.pro - the proof layer for AI free to use?
- Partly — some of its tools are open, others need a key or payment.
- What tools does sebbi.pro - the proof layer for AI have?
- 20 tools: sebbi_billing_link, sebbi_jugular_check, sebbi_spend_request, sebbi_setup_advice, sebbi_create_account, sebbi_test_decision, sebbi_notarize, sebbi_run_everything, ….
- Is sebbi.pro - the proof layer for AI safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.3%· all time 100%
last good check
of 20 tools
- degraded → live
- live → degraded· HTTP 502
- degraded → live
- live → degraded· HTTP 502
- degraded → live
- used for
- seal and score an ai decision for later proof
- timestamp a file hash in bitcoin
- approve an agent payment against spend limits
- verify a spend gate token
- check whether a human typed a text
- takes → gives
- text → data
- tools
- 4 reads5 changes data
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
sebbi_terms reads open 9h ago
Returns the service terms and their version. Show the full text to the person and get a clear yes before calling sebbi_create_account. Read-only.
{ "type": "object", "properties": {} }arguments 4 linessebbi_tools open 1h ago
sebbi.pro has more tools than are listed up front: banking and fraud cases, human oversight, law lookups and Law Lock, insurability, Signal Packs, answer receipts, the Examiner, readiness reports, incidents, energy, Bot School and more. This returns each one's name, what it does and its inputs. Pass search to filter (for example 'banking' or 'oversight'). Call any of them with sebbi_tool. Read-only, free.
{ "type": "object", "properties": { "search": { "type": "string", "description": "Words to filter by, e.g. banking" } } }arguments 9 linessebbi_find_checks open 1h ago
Searches sebbi.pro's 755 compliance checks across 32 frameworks (EU AI Act, GDPR, DORA, ISO/IEC 42001 and 27001, NIST AI RMF, UK Online Safety Act, EU DSA, SOC 2, PCI DSS, HIPAA, CCPA, NIS2, Cyber Resilience Act, ICO Children's Code, US state AI laws, model risk, and agent-output gates). Filter by framework and/or words; returns each check's id, title, what it needs and the framework list. Then run one with sebbi_run_check or a whole framework with sebbi_run_framework. Read-only.
{ "type": "object", "properties": { "limit": { "type": "integer", "description": "Most checks to return (default 40, max 200)." }, "search": { "type": "string", "description": "Words to look for in the check titles, e.g. 'human oversight' or 'retention'." }, "framework": { "type": "string", "description": "Framework key, e.g. euaiact, gdpr, dora, iso42001. Leave out to list frameworks." } } }arguments 17 linessebbi_court_pack open 23h ago
Produces a printable Court Pack for a sebbi fact (any record code, chain block number or notarised SHA-256): the fact, the sealed record, the step-by-step proof to Bitcoin, a method statement, and draft declarations for England and Wales (witness statement), US Federal Rules of Evidence 902(13)/902(14), Vermont 12 V.S.A. 1913 and an eIDAS note. Returns the link. Read-only.
{ "type": "object", "required": [ "ref" ], "properties": { "ref": { "type": "string" } } }arguments 11 linessebbi_overview reads open 1h ago
Start here. Lists every sebbi.pro product with what it does, who it is for, its page and its price. Read-only, no account needed.
{ "type": "object", "properties": {} }arguments 4 linessebbi_verify_chain reads open 9h ago
Re-checks every block in the sebbi.pro chain and returns its height, tip and whether it is intact. Anyone can run it; no account needed. Read-only.
{ "type": "object", "properties": {} }arguments 4 linessebbi_insurer_level auth-required 9h ago
The customer's live Insurability Level (I-0 to I-4) worked out from their sealed AI behaviour over the last 30 days: records verify and no receipts missing (I-1), humans review flags with real reading time (I-2), an armed enforcement loop and kill switch (I-3), agent payments need approval (I-4). Shows what is holding them back and how to fix it, and which insurers they share it with. Read-only.
{ "type": "object", "required": [ "api_key" ], "properties": { "api_key": { "type": "string" } } }arguments 11 linessebbi_billing_link changes data unknown never probed
Returns a secure Stripe link where the person adds a card for the 50p per device per month subscription. Nothing is charged until they complete it.
{ "type": "object", "required": [ "email" ], "properties": { "email": { "type": "string" }, "devices": { "type": "integer" }, "product": { "type": "string" } } }arguments 17 linessebbi_jugular_check unknown 23h ago
Call before taking any action for a system that has a Jugular (a human-held kill switch, id JG-XXXX-XXXX). Returns live true or false. If live is false, or the check fails, do not act: the human holding the switch has stopped this system (EU AI Act Article 14(4)(e) stop button). Read-only.
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string" } } }arguments 11 linessebbi_spend_request changes data unknown never probed
Call before every payment an AI agent makes. Returns a signed APPROVED or DENIED token checked against the agent's limits. Release the money only if it is APPROVED and spendable. sebbi.pro never holds or moves money.
{ "type": "object", "required": [ "api_key", "agent", "amount", "payee" ], "properties": { "agent": { "type": "string" }, "payee": { "type": "string" }, "amount": { "type": "number", "description": "Amount in pounds" }, "reason": { "type": "string" }, "api_key": { "type": "string" }, "currency": { "type": "string" } } }arguments 30 linessebbi_setup_advice reads unknown never probed
Recommends the right sebbi.pro products for how someone builds (Python, Node, Lovable, Zapier, a website, a phone app...) and gives step-by-step setup with working code or a ready-made prompt. Pass their stack and what they want to achieve. Read-only.
{ "type": "object", "required": [ "stack" ], "properties": { "goal": { "type": "string", "description": "What they want, e.g. 'prove our loan AI is compliant', 'cut our OpenAI bill'" }, "stack": { "type": "string", "description": "How they build or what they use, e.g. 'Lovable website', 'Python on AWS', 'Zapier'" }, "device": { "type": "string", "description": "Where they are working from, e.g. 'Android phone', 'Mac'" }, "api_key": { "type": "string" } } }arguments 23 linessebbi_create_account changes data unknown never probed
Opens a sebbi.pro account and returns the API key. Only call after showing sebbi_terms and the person agreeing; pass the terms_version they agreed to and customer_agreed=true. The agreement is sealed into the chain. Free for 7 days.
{ "type": "object", "required": [ "email", "terms_version", "customer_agreed" ], "properties": { "name": { "type": "string" }, "email": { "type": "string" }, "company": { "type": "string" }, "devices": { "type": "integer", "description": "Estimated devices; billing uses the real count" }, "product": { "enum": [ "aileash", "sentinel", "sonicboom", "guardian", "tokensaver" ], "type": "string" }, "terms_version": { "type": "string", "description": "terms_version from sebbi_terms" }, "customer_agreed": { "type": "boolean", "description": "true only if the customer read the terms and said yes" } } }arguments 41 linessebbi_test_decision changes data unknown never probed
Sends one decision through the live engine with their API key and returns the verdict (ALLOW, CHALLENGE or BLOCK), the reasons and the sealed block number, so they see it working end to end. Writes one record to the chain.
{ "type": "object", "required": [ "api_key" ], "properties": { "action": { "type": "string" }, "amount": { "type": "number" }, "api_key": { "type": "string" }, "country": { "type": "string" }, "user_id": { "type": "string" } } }arguments 23 linessebbi_notarize changes data unknown never probed
Timestamps one or more SHA-256 fingerprints in Bitcoin through the free notary. Hash the file or text yourself and send only the 64-character fingerprint; the content never leaves. Returns a receipt code and link for each.
{ "type": "object", "required": [ "digests" ], "properties": { "label": { "type": "string", "description": "Optional public label, up to 80 characters" }, "api_key": { "type": "string" }, "digests": { "type": "array", "items": { "type": "string" } } } }arguments 21 linessebbi_run_everything unknown never probed
Runs all 755 compliance checks (or the frameworks named) on one governance record in a single call. Returns the overall score, a score for every framework, and the fixes that unlock the most checks first. By default seals the scorecard into Bitcoin with its own page and code (SC-XXXX-XXXX) to send to an auditor or insurer; send seal=false to just look. Agent-output gates run too when input_payload/output_payload are given. Only a fingerprint of the record is kept.
{ "type": "object", "properties": { "org": { "type": "string", "description": "Organisation or system name shown on the scorecard." }, "seal": { "type": "boolean", "description": "Seal into Bitcoin with a public scorecard page (default true)." }, "detail": { "type": "boolean", "description": "Also list every failing check by framework." }, "record": { "type": "object", "description": "The governance record (fields from sebbi_record_template)." }, "frameworks": { "type": [ "array", "string" ], "items": { "type": "string" }, "description": "Framework keys (e.g. euaiact, gdpr, dora, iso42001) as a list or comma-separated; leave out for all." }, "input_payload": { "type": "object", "description": "For agent-output gates: what went into the AI step." }, "output_payload": { "type": "object", "description": "For agent-output gates: what the AI step produced." } } }arguments 39 linessebbi_banking_pay_check unknown never probed
Call before releasing ANY payment, whether an AI agent or a payment system is sending it. One call checks the agent's authority (Mandate Chain, Agent Passport or Spend Gate token), the payee's sealed bank details (Payment Notary), the human kill switch (Jugular) and every FCA-named fraud indicator, then answers RELEASE, HOLD or STOP with the reasons, sealed. Release money only on RELEASE. The answer lists the next tools to call. Needs api_key; never send names or account numbers.
{ "type": "object", "required": [ "api_key", "amount" ], "properties": { "payee": { "type": "string", "description": "who is being paid (your reference)" }, "amount": { "type": "number" }, "api_key": { "type": "string" }, "mandate": { "type": "string", "description": "Mandate Chain token when an AI agent started the payment" }, "audience": { "type": "string", "description": "the site an Agent Passport is presented at" }, "passport": { "type": "string", "description": "Agent Passport token when an AI agent started the payment" }, "direction": { "type": "string" }, "payee_new": { "type": "boolean" }, "payee_ref": { "type": "string" }, "payer_ref": { "type": "string", "description": "who is paying (your reference); defaults to agent-payments" }, "cop_result": { "type": "string" }, "jugular_id": { "type": "string", "description": "the Jugular kill switch held over this fraud engine" }, "lineage_id": { "type": "string", "description": "Model Lineage code of the scoring model setup" }, "new_device": { "type": "boolean" }, "vulnerable": { "type": "boolean" }, "spend_token": { "type": "string", "description": "Spend Gate token when an AI agent started the payment" }, "customer_ref": { "type": "string" }, "remote_access": { "type": "boolean" }, "account_opened": { "type": "string" }, "customer_on_call": { "type": "boolean" }, "payee_fingerprint": { "type": "string", "description": "sha256 hex of payment:v1|<business name, trimmed, lower case>|<sort code digits>|<account digits>, checked against the Payment Notary" }, "crypto_or_investment": { "type": "boolean" }, "expected_max_payment": { "type": "number" }, "expected_monthly_turnover": { "type": "number" } } }arguments 90 linessebbi_enforce_create unknown never probed
Automated Enforcement Loop: when the customer's sealed decisions cross a threshold, sebbi.pro acts at once. It contains the AI (every further decision on the key is a sealed BLOCK, so the sebbi.pro Gateway stops calling the model), pulls their Jugular switches, fires a signed webhook into their own infrastructure, and emails them. Every trip and release is sealed. trigger: {count, window_seconds, verdicts ([BLOCK, CHALLENGE, ALLOW]), reasons_any (words to find in the decision's reasons, e.g. prompt_injection or a risk signal name), min_score, field {field, op (eq, ne, gt, gte, lt, lte, in, not_in, contains, exists), value}, distinct_field (count different values of this field, e.g. model)}. actions: {contain_minutes (-1 = until released, 0 = no), jugular_ids, webhook_url (https), email_owner}. mode: armed or watch. Run sebbi_enforce_backtest first.
{ "type": "object", "required": [ "api_key", "trigger" ], "properties": { "mode": { "enum": [ "armed", "watch" ], "type": "string" }, "name": { "type": "string" }, "actions": { "type": "object" }, "api_key": { "type": "string" }, "trigger": { "type": "object" }, "cooldown_seconds": { "type": "integer" } } }arguments 31 linessebbi_forensic_replay unknown never probed
Forensic Replay Sandbox. Replays every AI decision sealed with the customer's API key under a new rule set and returns which verdicts would change, which way, by month, the money behind them and the rule that caused each. Rule set: allow_below and block_from (verdict boundaries, today 0.35 and 0.70), factors (history, amount, device_risk, anomaly, unsafe_country as multipliers, 1 = unchanged), high_risk_countries and safe_countries (country codes), signal_weights for the customer's own risk signals, and rules: [{name, field, op (eq, ne, gt, gte, lt, lte, in, not_in, contains, exists), value, then (CHALLENGE or BLOCK)}] on any field they send. Records are verified untouched first and only exactly reproducible decisions are counted. The run is sealed into the chain and gets a shareable report link.
{ "type": "object", "required": [ "api_key" ], "properties": { "to": { "type": "string", "description": "Last day, YYYY-MM-DD (optional)" }, "from": { "type": "string", "description": "First day, YYYY-MM-DD (optional)" }, "name": { "type": "string", "description": "A name for the rule change, e.g. 'Human review over 10,000'" }, "api_key": { "type": "string" }, "ruleset": { "type": "object", "description": "The new rules, as described above" } } }arguments 27 linessebbi_ask_why unknown never probed
For a person who was turned down by a computer (credit, a job, insurance, an account, benefits, housing). Writes their legal request under UK GDPR Articles 22A-22D and 15 or EU GDPR Articles 22 and 15 (and AI Act Article 86 where it applies), seals it with a timestamp so the one-month deadline is provable, and returns the letter, where to send it, a private tracking link and a reply link the organisation answers through. Give the person the letter and the tracking link, and tell them to keep the tracking link private. Use only the person's real details; ask for what you don't know. Personal details are not stored: only the letter's fingerprint.
{ "type": "object", "required": [ "company", "what_happened", "your_name" ], "properties": { "company": { "type": "string" }, "your_name": { "type": "string" }, "account_ref": { "type": "string" }, "jurisdiction": { "enum": [ "UK", "EU" ], "type": "string" }, "your_contact": { "type": "string" }, "decision_date": { "type": "string", "description": "YYYY-MM-DD, roughly" }, "decision_type": { "enum": [ "credit", "job", "insurance", "account", "benefits", "housing", "education", "price", "moderation", "other" ], "type": "string" }, "what_happened": { "type": "string" }, "company_domain": { "type": "string" }, "representations": { "type": "string" } } }arguments 57 linessebbi_tool unknown never probed
Calls any sebbi.pro tool by its name with its arguments, including the ones not listed up front (see sebbi_tools). Use it when an answer's next_tools names a tool you do not see in your list. Same result as calling the tool directly.
{ "type": "object", "required": [ "name" ], "properties": { "name": { "type": "string", "description": "The tool name, e.g. sebbi_banking_case" }, "arguments": { "type": "object", "description": "That tool's arguments" } } }arguments 16 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id61d565171d9eb2da.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/61d565171d9eb2da/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/61d565171d9eb2da?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.