MCP servers › pro.sebbi › governance

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

pro.sebbi/governance

Score, seal and prove AI decisions in Bitcoin, plus 739 compliance checks, free to verify. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-23Topic: security · AI-classifiedversion 1.1.2streamable HTTP26 tools

Summary

pro.sebbi/governance is a remote MCP server listed in the official MCP registry at version 1.1.2. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 26 tools, 0 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

met: Registry entry is active and says how to run it
not met: Source repository link opens
not applicable: Repository is not archived
not applicable: Code pushed to the repository in the 90 days before our check
not applicable: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Tools: 26
Described as changing data: 10 of 26 toolsAI-classified
Topic: securityAI-classified
Last tested: 2026-10-23

Add to your client

Observed fact

This server accepted a session without any credential and lists 1 tool whose name or declaration suggests it changes data (sebbi_create_account). That is our reading of the names; we did not call it. Source: our connection, 2026-10-23.

Worth knowing before you connect it

10 tools are described as changing something (sebbi_create_account, sebbi_test_decision, sebbi_gateway_setup, …): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-23

Mode

read-only (no tool calls)

Latest version

1.1.2, published 2026-10-20 (registry, as of the 2026-10-23 snapshot)

First listed version

2026-10-06 (earliest version still in the registry; older removed versions would be earlier)

Version history

4 versions listed, 2026-10-06 to 2026-10-20; 4 in the 90 days before the 2026-10-23 snapshot.

Most recent 4 versions

1.1.2 · 2026-10-20
1.1.1 · 2026-10-18
1.1.0 · 2026-10-18
1.0.0 · 2026-10-06

(versions still listed in the registry only)

Registry data

snapshot 2026-10-23

Package and repository

checked 2026-10-23

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.1.2 (published 2026-10-20).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

26tools

0resources

0prompts

10 of 26 tools are described as changing something (creating, editing, deleting, sending or running). For 1 the reading was uncertain, so no mark is shown.

sebbi_overviewreads or searches
“Start here.”
Publisher declares: read-only yes · destructive no · open-world yes
Takes no inputs.
sebbi_setup_advicereads or searches
“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.”
Publisher declares: read-only yes · destructive no · open-world yes
4 inputs, 1 required
- stackstringrequired“How they build or what they use, e.g.”
- goalstring“What they want, e.g.”
- devicestring“Where they are working from, e.g.”
- api_keystring
sebbi_termsreads or searches
“Returns the service terms and their version.”
Publisher declares: read-only yes · destructive no · open-world yes
Takes no inputs.
sebbi_create_accountcreates or changes datadescribed as changing data
“Opens a sebbi.pro account and returns the API key.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
7 inputs, 3 required
- namestring
- emailstringrequired
- companystring
- productstring
- devicesinteger“Estimated devices; billing uses the real count”
- terms_versionstringrequired“terms_version from sebbi_terms”
- customer_agreedbooleanrequired“true only if the customer read the terms and said yes”
sebbi_test_decisionruns code or commandsdescribed as changing data
“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.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
5 inputs, 1 required
- api_keystringrequired
- actionstring
- amountnumber
- countrystring
- user_idstring
sebbi_billing_linkreads or searches
“Returns a secure Stripe link where the person adds a card for the 50p per device per month subscription.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
3 inputs, 1 required
- emailstringrequired
- devicesinteger
- productstring
sebbi_gateway_setupcreates or changes datadescribed as changing data
“Returns a private gateway address for their API key and the exact one-line change for their stack.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
3 inputs, 1 required
- api_keystringrequired
- stackstring“e.g.”
- labelstring
sebbi_decision_reportreads or searches
“The machine-proof report for one decision their key sealed: what was decided, who sent it, where it came from, and the proof it has not changed since.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs, 2 required
- api_keystringrequired
- blockintegerrequired
sebbi_verify_chainreads or searches
“Re-checks every block in the sebbi.pro chain and returns its height, tip and whether it is intact.”
Publisher declares: read-only yes · destructive no · open-world yes
Takes no inputs.
sebbi_notarizedescribed as changing data
“Timestamps one or more SHA-256 fingerprints in Bitcoin through the free notary.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
3 inputs, 1 required
- digestsarrayrequired
- labelstring“Optional public label, up to 80 characters”
- api_keystring
sebbi_notary_receiptreads or searches
“Where a notary receipt (NT-XXXX-XXXX) or Human Keys code (HK-XXXX-XXXX) stands: queued, sent to Bitcoin, or confirmed in a block, with its Forever Proof link.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
1 input, 1 required
- codestringrequired
sebbi_forever_proofreads or searches
“A self-contained proof anyone can check against Bitcoin without sebbi.pro, for a notary receipt, a Human Keys code or any chain block.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
3 inputs
- codestring
- blockinteger
- api_keystring

Show 14 more tools

sebbi_check_human_proofreads or searches
“Looks up a Human Keys code (HK-XXXX-XXXX): whether a person typed the text live, and when.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- codestringrequired
sebbi_check_sourcereads or searches
“Garbage-in guard.”
Publisher declares: read-only yes
3 inputs, 1 required
- domainstringrequired“The source domain, e.g.”
- datastring“The input text to check”
- hashstring“Or the SHA-256 of the data, instead of the text”
sebbi_spend_policycreates or changes datadescribed as changing data
“Sets, or reads back, an AI agent's spending limits: the most it may pay in one go and per day, and optionally the only payees allowed.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
6 inputs, 4 required
- api_keystringrequired
- agentstringrequired
- per_txnumberrequired“Max per payment, in pounds”
- dailynumberrequired“Max per day, in pounds”
- currencystring
- payeesarray
sebbi_spend_requestdescribed as changing data
“Call before every payment an AI agent makes.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
6 inputs, 4 required
- api_keystringrequired
- agentstringrequired
- amountnumberrequired“Amount in pounds”
- payeestringrequired
- reasonstring
- currencystring
sebbi_spend_verifyreads or searches
“Checks a Spend Gate token's signature and whether it can still be spent.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- tokenstringrequired
sebbi_insurabilitycreates or changes datadescribed as changing data
“Rates an AI deployment against the Insurable AI Standard (I-0 Unrated to I-4 Pre-cleared) from controls it can prove, and seals an Insurability Certificate (IC-XXXX-XXXX) any insurer can verify.”
Publisher declares: read-only no · destructive no
7 inputs, 1 required
- domainstringrequired“The deployment's domain, e.g.”
- namestring“Display name (optional)”
- source_domainstring“A sebbi Verified-Source domain, to verify the 'Inputs sourced' pillar (optional)”
- mcp_codestring“An MCP-Shield code MS-XXXX-XXXX, to verify the 'Tools guarded' pillar (optional)”
- decisionsboolean“Attest: every AI decision is sealed (Art 12 logging)”
- humanboolean“Attest: a named human is accountable, actions carry a signed permission”
- preclearedboolean“Attest: no autonomous payment fires without a sealed sign-off (Witness-Proof)”
sebbi_verify_insurabilityreads or searches
“For insurers and auditors: checks an Insurability Certificate (IC-XXXX-XXXX) against the chain and returns its level, which controls are verified or declared, whether it is still current, and its Bit…”
Publisher declares: read-only yes
1 input, 1 required
- codestringrequired“The certificate code, IC-XXXX-XXXX”
sebbi_pack_referencereads or searches
“The reference for writing Signal Packs, custom decision rules on top of the engine: the signals, measurements, flags, operators and verdicts.”
Publisher declares: read-only yes · destructive no · open-world yes
Takes no inputs.
sebbi_check_packreads or searches
“Checks a Signal Pack with the engine's own validator without publishing it, and explains any problem.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- packobjectrequired
sebbi_publish_packcreates or changes datadescribed as changing data
“Publishes a Signal Pack to the open library, sealed, dated and credited to its author.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
1 input, 1 required
- packobjectrequired
sebbi_list_packsreads or searches
“Lists the published Signal Packs, optionally for one sector.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input
- verticalstring
sebbi_find_checksreads or searches
“Searches sebbi.pro's 739 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 Re…”
Publisher declares: read-only yes · destructive no · open-world no
3 inputs
- frameworkstring“Framework key, e.g.”
- searchstring“Words to look for in the check titles, e.g.”
- limitinteger“Most checks to return (default 40, max 200).”
sebbi_run_checkruns code or commandsdescribed as changing data
“Runs one sebbi.pro compliance check by its id (from sebbi_find_checks, e.g.”
Publisher declares: read-only yes · destructive no · open-world no
5 inputs, 1 required
- checkstringrequired“The check id, e.g.”
- recordobject“The governance or decision record (framework checks).”
- input_payloadobject“What went into the AI step (agent-output gates).”
- output_payloadobject“What the AI step produced (agent-output gates).”
- reasonstring“Optional note on why the check is being run.”
sebbi_run_frameworkruns code or commandsdescribed as changing data
“Runs every check in one framework against a single record and returns a scorecard: how many passed and failed, each failing control with its reason, and a receipt for every result.”
Publisher declares: read-only yes · destructive no · open-world no
4 inputs, 1 required
- frameworkstringrequired“Framework key from sebbi_find_checks, e.g.”
- recordobject“The governance or decision record (framework checks).”
- input_payloadobject“For agent-output gate frameworks.”
- output_payloadobject“For agent-output gate frameworks.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 26 tools
Says what it returns: 100% of 26 tools
States limits, defaults or errors: 4% of 25 tools
Says when to use it: 100% of 26 tools
Items covered per tool: 3.1 of 4 on average

Counted from the listing

Parameters with a description: 48% of 71
Tools with a description: 100% of 26
Typical description length: 204 characters

The tool set

Counted from the listing

Tools: 26
Size of the list: about 4,166 tokens for an agent to load (characters ÷ 4)
Naming: 26 of 26 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 26 of 26 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://sebbi.pro/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "governance": {
      "url": "https://sebbi.pro/mcp"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "governance": {
      "type": "http",
      "url": "https://sebbi.pro/mcp"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"governance","type":"http","url":"https://sebbi.pro/mcp"}'

Claude Code

claude mcp add --transport http governance https://sebbi.pro/mcp

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://sebbi.pro/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint sebbi.pro/mcp	Session opened	matches	our test · 2026-10-23
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-23

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
Not metSource repository link opensThe registry entry gives no repository link.
Does not applyRepository is not archivedNo public GitHub repository to read.
Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about pro.sebbi/governance

Answered from the data above

Is pro.sebbi/governance safe to install?

We do not rate servers as safe or unsafe. 1 of its 2 applicable record checks are met (facts from public records, each listed on this page). What the records show: 10 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does pro.sebbi/governance need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has pro.sebbi/governance been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

What can pro.sebbi/governance do?

It lists 26 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data and run code or commands. We did not call any tool, so this describes the text, not the behaviour.

Can pro.sebbi/governance change or delete data?

10 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

io.github.arthurpanhku/dvalincodealso has tools that creates or changes data, runs code or commands, reads or searchescompare with this one
io.github.Servosity/blumira-mcpBlumira MCPalso has tools that creates or changes data, runs code or commands, reads or searchescompare with this one
io.github.ashlrai/phantom-secrets-mcpPhantom Secretsalso has tools that creates or changes data, runs code or commands, reads or searchescompare with this one
io.github.vaaraio/vaara-serverVaara MCP Serveralso has tools that creates or changes data, runs code or commands, reads or searchescompare with this one
io.github.OrygnsCode/opa-mcpOPA MCPalso has tools that creates or changes data, runs code or commands, reads or searchescompare with this one
io.github.maximilianfeix/hexverohexveroalso has tools that creates or changes data, runs code or commands, reads or searchescompare with this one

Active servers whose topic is also “security” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised

Not run, with the reason · 12

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 4

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
843 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 26 tools, 0 resources, 0 prompts.
3,579 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

security

AI-classified · 2026-10-23

Pricing modelAI-classified

no value

No value: the AI answer was held back because the quoted text did not clearly support it.

Programming language

does not apply

no existing GitHub repository (server declares no repository link, so there is nothing to fetch)

Hosting type

remote (hosted by the publisher)

registry · 2026-10-23

MCP capability

tools

our test · 2026-10-23

Transport

streamable HTTP

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

not stated

no readable GitHub owner to describe

Maintenance

does not apply

server declares no repository link, so there is nothing to fetch

Environment

the publisher's infrastructure

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “pro.sebbi/governance: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/pro.sebbi/governance

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/pro.sebbi/governance)](https://protocolprobe.com/mcp/servers/pro.sebbi/governance)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology