com.shpbl/repository-audit-and-repair

Est-ce que com.shpbl/repository-audit-and-repair est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.shpbl/repository-audit-and-repair » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 17 outils

• build_intent≈ 4414 tokens

  The gate between discovery and creation, and the human checkpoint in front of it. Register one Build Intent — what you found in the host, what SHPBL already possesses, what new software becomes possible, why neither parent does it alone, and the tests that would prove it — and this returns the mechanical verdict: the invariants it passed, whether it rests on SHPBL's licensed reusable capability, whether this caller may execute the foundry, the terminal state to report, and where an authorised artifact may come to rest. THE CHECKPOINT BLOCKS: without `human_decision` carrying an attributed decision from the person, this returns the proposal in the words to say to them and nothing else — no verdict, no read, no record — and you end your turn and wait. No answer yet is NOT_YET_ASKED, never DECLINED. A decision attributed to you, to a model, to a policy or to a default is refused where the server can recognise it as such; any other name is recorded and attributed, not verified, and the authorization says which — `account` when the name matches the key's account holder, `attested` otherwise. DECLINED and NEEDS_EXPLANATION are successful outcomes: record them, build the approved siblings, and do not report a declined proposal as a failed step. Free to call at every level. Every COMPOSE, SPECIALIZE and CREATE must pass through this before any source is written; never assume authority and never write a refused artifact yourself.

  Paramètres, retour & exemple (7)

  Paramètres

  • key · string · optionnel
    Your SHPBL Practitioner key (shpbl_mcp_…). Optional if your client sends it as the `Authorization: Bearer …` header.
  • intent · object · requis
    The Build Intent record; every field it asks for is part of the evidence, and each field carries its own description in this schema. Required: `build_intent_id`, `proposed_artifact_id`, `proposed_name`, `display_name`, `what_it_gives_you`, `why_this_repo`, `proposed_type`, `host_repository`, `host_source_paths`, `host_behavior`, `host_problem`, `new_behavior`, `novelty_statement`, `planned_interface`. `display_name`, `what_it_gives_you` and `why_this_repo` are quality gates, not presentation: if you cannot name the software and say what new ability it gives this repository and why this repository, the proposal is refused. Tests are mandatory in effect: at least one entry across `planned_unit_tests`, `planned_behavior_tests` and `planned_integration_tests` (the aliases `planned_tests`, `unit_tests`, `behavior_tests` and `integration_tests` are folded into those three). Every path in `host_source_paths` is resolved against the real tree before anything is authorised — a path that is not there refuses the intent.
  • cml_license · string · optionnel
    The licence key from a purchased Complete Master Library. Perpetual rights to that release count as execution authority on their own — no subscription needed.
  • github_token · string · optionnel
    Optional GitHub token (Contents: read) so the gate can read the host tree and prove the cited paths exist. Not needed if you pass `host_source_manifest`.
  • governor_key · string · optionnel
    Governor authority. Only a Governor-resolved call may stage an artifact for SHPBL's global corpus.
  • human_decision · object · optionnel
    The person's decision on this proposal. Step 9 is a blocking checkpoint: without an attributed human decision this tool returns the words to say and nothing else, and you end your turn there. Do not send a decision the person did not make.
  • host_source_manifest · ? · optionnel
    The `HOST-SOURCE-MANIFEST.json` from `pin_source` or `tools/source-manifest.mjs`, as JSON text or an object. Offline runs must send this: the gate recomputes its digest and resolves every cited path against its entries. An edited or invented digest is refused.

  Exemple d'appel

  {"name": "build_intent", "arguments": {"intent": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• compose_capability≈ 552 tokens

  The harvest lane: read what a repository can already do, then offer codeless capability nominations that fuse those affordances with owned SHPBL primitive capabilities — DREAM, EVOLUTION, MEMORY, DEFENSE, BRAIN and the rest of the canonical forty, plus the S-Tier artifacts. Each nomination names host evidence, proposed capability bodies, Capability Contract slots, a test plan, and honest limits. It contains no implementation; approved materialization belongs to `harvest_repo`. Free calls return host affordances, then stop before library correlation; nominations require a Practitioner key (7-day free trial).

  Paramètres, retour & exemple (7)

  Paramètres

  • key · string · optionnel
    Your SHPBL Practitioner subscription key (shpbl_mcp_…). Optional if your client sends it as the `Authorization: Bearer …` request header.
  • repo · string · requis
    A GitHub repository: `owner/repo` or a URL.
  • pages · number · optionnel
    How many source pages to read for affordance evidence, 1 to 12 (about 90,000 characters each). More pages means more of the tree is read; the grants are cut from whatever was read.
  • grants · number · optionnel
    How many codeless capability nominations to return, 1 to 200. Ranked by measured fit and capability standing.
  • include · string · optionnel
    Optional path filter — only paths containing this text are read for affordances.
  • github_token · string · optionnel
    Optional GitHub token (Contents: read) for a private repository.
  • per_affordance · number · optionnel
    How many nominations one affordance may produce, 1 to 200. Raise it to see alternative leads for the same host capability.

  Exemple d'appel

  {"name": "compose_capability", "arguments": {"repo": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• evaluate_repo≈ 1098 tokens

  Audit any GitHub repository and get back one complete result: a report (inventory, languages, spine files, risk signals), the capabilities found in it (name, signature, file and line, stated contract, dependencies), and how it stands against SHPBL's anonymous corpus of audited repositories. Works with no key: every caller gets the whole diagnosis of their own repository. A free run stops at the composition boundary — neither library is searched, so no library rows, candidates, parents or proposed architecture are returned — and nothing is retained (no pull request, no export, no recorded run). A Practitioner key (7-day free trial) continues past that boundary: both libraries searched, candidates identified and composed, and the result written back to your own repository. Whatever a run finds is yours. Follow with `fix_repo` for verbatim source and diffs, `harvest_repo` for the whole tree.

  Paramètres, retour & exemple (8)

  Paramètres

  • key · string · optionnel
    Your SHPBL key (shpbl_mcp_…), if you have one. Optional — without it the audit runs at the free depth. Also read from the `Authorization: Bearer …` header.
  • repo · string · requis
    A GitHub repository: `owner/repo`, a github.com URL, or `owner/repo#branch`.
  • brief · boolean · optionnel
    Default true: keep the audit compact and do not include the full method protocol. Set false to include the protocol block.
  • as_free · boolean · optionnel
    Run at the free depth even when the key carries a paid tier, so you can see exactly what a caller without a subscription is handed. Costs no allowance and changes nothing else about the audit.
  • sections · array · optionnel
    Which sections to print, when you only need some of them. Omit it and the whole audit comes back, which is the right default on a first call. On a follow-up — re-reading the capability list after a repair, or checking the benchmark alone — name just what you need (for example `["capabilities"]`) rather than re-sending the whole audit into the conversation. Nothing is computed differently and nothing costs less; only the printed result is narrower, and the machine-readable payload is unchanged.
  • own_library · array · optionnel
    Your own previously harvested capabilities, read out of your repository's `.shpbl/` library and passed back in. Optional. When present, this run checks your concerns against your own library first and tells you which ones you already solved. It is held in memory for this call only — never stored, never added to SHPBL's library.
  • github_token · string · optionnel
    Optional GitHub token (Contents: read) for a private repository. Not needed if the owner connected the SHPBL GitHub App to this key at https://shpbl.com/mcp-access.
  • protocol_ack · boolean · optionnel
    Set true to say you already hold the SHPBL protocol. The discipline, the ten meta capabilities, the hands-off list and the return shape are then not reprinted even when `brief: false` — they are unchanged and they still bind the run.

  Exemple d'appel

  {"name": "evaluate_repo", "arguments": {"repo": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• fix_repo≈ 905 tokens

  The repair: verbatim source of the files you name — or the repository's spine when you name none — paginated for your context window, with the remediation protocol your model writes the diffs against. Free to run with no key: every file you name, paginated, plus the ordered remediation protocol — repair of what is already there. A free repair stops before either library is searched, so it proposes no composed capability, no candidates and no reuse. A Practitioner key (7-day free trial) crosses that boundary and makes the repair persist — `write_to_repo` opens the branch and the pull request.

  Paramètres, retour & exemple (8)

  Paramètres

  • key · string · optionnel
    Your SHPBL key (shpbl_mcp_…), if you have one. Optional — without it the repair returns one file at the free depth. Also read from the `Authorization: Bearer …` header.
  • part · integer · optionnel
    Which page of source to return. Page 1 reports the total and carries the protocol.
  • repo · string · requis
    A GitHub repository: `owner/repo` or a URL.
  • brief · boolean · optionnel
    Skip the remediation protocol preamble and return source with a one-line reminder instead. Use it once you already hold the method — `method_protocol` (free) returns it whenever you need it again.
  • paths · array · optionnel
    Paths to read, from the evaluation. Omit to read the repository's spine.
  • own_library · array · optionnel
    Your own previously harvested capabilities, read out of your repository's `.shpbl/` library and passed back in. Optional. When present, this run checks your concerns against your own library first and tells you which ones you already solved. It is held in memory for this call only — never stored, never added to SHPBL's library.
  • github_token · string · optionnel
    Optional GitHub token (Contents: read) for a private repository. Not needed if the SHPBL GitHub App is connected to this key.
  • protocol_ack · boolean · optionnel
    Set true to say you already hold the SHPBL protocol — the discipline, the ten meta capabilities, the hands-off list and the return shape are then not reprinted on page 1. Same effect as `brief` for the preamble, and the honest default for a session that has already called `method_protocol` or run an earlier stage.

  Exemple d'appel

  {"name": "fix_repo", "arguments": {"repo": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• harvest_repo≈ 1941 tokens

  The harvest shortcut: point it at a repository you hold a licence to reuse — one you do not own and will never open a pull request against — and it goes straight to the capabilities. It reads what that repository can already do, fuses those affordances with the owned SHPBL capability library, ranks and names the results as proposals a person can read, stops for your decision on each one, and then emits the seed modules for exactly the ones you approved into your own `.shpbl/` library. That is the gauntlet's steps 8, 9 and 10 without the audit, the repair plan or the pull request. It never writes to the target repository. Pass `approve` with `approved_by` and `host_license` to collect the approved grants; pass `mode: "walk"` for the older batched ledger walk of the whole tree (`estimate`, `part`, `ledger_digest`, `budget` belong to that mode). Free calls report what the repository can do and what is offerable against it, then stop at the composition boundary; grants need a Practitioner key (7-day free trial).

  Paramètres, retour & exemple (26)

  Paramètres

  • key · string · optionnel
    Your SHPBL Practitioner subscription key (shpbl_mcp_…). Optional if your client sends it as the `Authorization: Bearer …` request header.
  • mode · string · optionnel · harvest | walk
    `harvest` (the default when nothing else in the call implies a walk) is the shortcut: proposals, your decision, then the seed modules for what you approved. `walk` is the older batched ledger walk of the whole tree, which reads and classifies but composes nothing. Send it explicitly whenever you also send `part`, `ledger_digest`, `budget` or `brief`.
  • part · number · optionnel
    Walk mode only: which batch to return, 1 to 2000. Batch 1 carries the protocol and the manifest; walk them all in order.
  • repo · string · requis
    A GitHub repository: `owner/repo` or a URL.
  • brief · boolean · optionnel
    Walk mode only: skip the harvest protocol preamble on batch 1 and spend the payload on source. Use it once you already hold the method — `method_protocol` (free) returns it verbatim.
  • pages · number · optionnel
    Harvest mode: how many source pages to read for evidence, 1 to 12 (about 90,000 characters each). Proposals are cut only from what was actually read.
  • budget · number · optionnel
    Characters per batch — a whole number from 10,000 to 120,000. Defaults to 90000; lower it for a smaller context window, raise it only if the client can carry it. Out-of-range values are refused in plain words, not silently clamped.
  • grants · number · optionnel
    Harvest mode: how many capability proposals to rank, 1 to 200. There is no fixed shallow ceiling any more — a sophisticated repository can support far more than a couple of dozen higher-order compositions, and the safeguard against a weak proposal is the approval and the Capability Contract, not a small number here.
  • approve · array · optionnel
    Harvest mode: the grant ids the person approved. Only these are emitted. Omit it on the first call — the proposals have to be put to them first. An id nobody proposed refuses the whole set rather than emitting the rest.
  • decline · array · optionnel
    Harvest mode: the grant ids the person explicitly said no to. Only these are recorded as declined; anything they were not asked about stays open and is re-offered, never written down as a refusal.
  • include · string · optionnel
    Optional path filter — only paths containing this text are harvested.
  • estimate · boolean · optionnel
    Return the size of the walk only — batch count, total characters, largest batch, split files — with no source.
  • approved_by · string · optionnel
    The name of the person who approved them. Required with `approve`. An agent, a model, a vendor, a policy or a default is refused, not recorded.
  • cml_license · string · optionnel
    Your perpetual copy's licence key, if you hold one. It changes retention, never depth.
  • github_token · string · optionnel
    Optional GitHub token (Contents: read) for a private repository. Not needed if the SHPBL GitHub App is connected to this key.
  • governor_key · string · optionnel
    Operator passphrase for SHPBL's own copy. Resolved by the server; it changes only where the harvest is staged, never what is proposed.
  • host_license · string · optionnel
    What the target repository's licence permits for this reuse, and any obligation it attaches — for example `MIT, attribution required`. Required with `approve`; SHPBL records your declaration and does not verify it.
  • ledger_digest · string · optionnel
    The ledger folded so far, handed back by a previous session so this batch continues the same run instead of starting over.
  • quality_floor · number · optionnel
    Harvest mode: drop proposals scoring below this, 0 to 1. The score is a discovery aid for ordering what to read first — it is never evidence that a capability deserves to exist.
  • per_affordance · number · optionnel
    Harvest mode: how many proposals one host affordance may produce, 1 to 200.
  • reuse_permitted · boolean · optionnel
    Required with `approve`: the person's explicit statement that reuse of this upstream project is permitted for this composition. Absence is never a yes, and SHPBL does not infer permission from a detected licence file. Recording your declaration is not legal verification and nothing here is legal advice.
  • upstream_project · string · optionnel
    The upstream project the reuse is declared against. Defaults to the repository being harvested.
  • novelty_threshold · number · optionnel
    Harvest mode: how different a proposal must be from the higher-ranked ones already chosen, 0 to 1, measured on bound capabilities and title vocabulary. 0 suppresses only exact duplicates; 0.4 is firm de-duplication of near-identical variants.
  • reuse_obligations · array · optionnel
    The obligations the licence attaches that must be preserved in the artifact — attribution, notice retention, share-alike, and so on. Recorded against every emitted artifact and carried into its manifest.
  • carry_notice_files · array · optionnel
    Licence or notice files from the host that must be copied into the artifact. Detected candidates are reported to you if you omit this.
  • suppress_duplicates · boolean · optionnel
    Harvest mode: drop proposals whose proposed composition is identical to a higher-ranked one. Default true.

  Exemple d'appel

  {"name": "harvest_repo", "arguments": {"repo": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• library_document≈ 362 tokens

  Read one long SHPBL document, paged for a context window: `volume` (the complete text of a volume of The Strategic Master Library), `catalog_outline` (the Collective catalog's parts, component classes, agent-kit steps and verification axes), `report_template` (the branded audit report HTML to fill in), or `standing_order` (the prompt that governs a run). Requires a Practitioner key.

  Paramètres, retour & exemple (5)

  Paramètres

  • key · string · optionnel
    Your SHPBL subscription key (shpbl_mcp_…). Optional if your client sends it as the `Authorization: Bearer …` request header.
  • part · number · optionnel
    1-based page of the document, up to 60.
  • volume · string · optionnel
    Required for `document: volume` — the volume slug or its number, 1 through 7.
  • section · string · optionnel
    For `document: catalog_outline` — only parts or sections whose name contains this text.
  • document · string · requis · volume | catalog_outline | report_template | standing_order
    Which document to read.

  Exemple d'appel

  {"name": "library_document", "arguments": {"document": "volume"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• library_index≈ 389 tokens

  Everything published on shpbl.com in one read: the editions and their prices and licences, the seven volumes of The Strategic Master Library with their seals and read links, the public downloads with byte sizes, and the case studies of real audit runs with each verdict, and `pools` — the canonical reconciliation of every count this server quotes, so two totals are never mistaken for a contradiction and never added together. Scope it with `sections`, or pass `volume` (slug or 1-7) or `case_study` (slug) for one record in full. Free — no key, no allowance.

  Paramètres, retour & exemple (3)

  Paramètres

  • volume · string · optionnel
    One volume in full, by slug or by number 1-7. Its complete text is a `library_document` call.
  • sections · array · optionnel
    Which sections to return. Omit for all of them: facts, volumes, editions, downloads, case_studies, pools. `pools` is the canonical reconciliation of every count this server quotes — read it before comparing two totals.
  • case_study · string · optionnel
    One case study in full, by slug — what the run got right and what it learned.

  Exemple d'appel

  {"name": "library_index", "arguments": {"volume": "texte", "sections": [], "case_study": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• library_search≈ 764 tokens

  Search the Collective Master Library for a capability in plain words, before writing new code. `scope: "catalog"` (Practitioner) searches the engineered components — class, what each does, API surface, line counts, verification marks. `scope: "composites"` searches capabilities earlier runs invented for one host by fusing library parts, each citing its sealed report. Pass `ids` for whole rows by component ID, with siblings and declared twins. Multi-word queries match term by term and rank; with no exact hit you get the closest rows, labelled as such.

  Paramètres, retour & exemple (11)

  Paramètres

  • ids · array · optionnel
    Up to 20 component IDs (e.g. `STIER-S-84`, `BLD-ENG-303`) returned in full instead of a search.
  • key · string · optionnel
    Your SHPBL subscription key (shpbl_mcp_…). Optional if your client sends it as the `Authorization: Bearer …` request header.
  • pack · string · optionnel
    Vault only: restrict to one vertical pack, e.g. `fintech-v1`. Substring match.
  • page · number · optionnel
    1-based page of results. A page past the end is refused, never returned empty.
  • limit · number · optionnel
    Alias for `page_size`, 1 to 50. Given both, `page_size` wins.
  • query · string · optionnel
    Plain-words capability, name, ID or API symbol. Omit to page the whole pool.
  • scope · string · optionnel · catalog | vault | crown-jewels | composites
    `catalog` — engineered components (Practitioner). `crown-jewels` — the S-Tier Vault of standalone lab-curated artifacts. `composites` — capabilities past runs invented for one host. (`vault` is no longer available; asking for it returns a pointer to these scopes.)
  • page_size · number · optionnel
    Rows per page, 1 to 50. Defaults to 20.
  • certified_only · boolean · optionnel
    Crown jewels only: return only rows whose body the certification harness executed and read clean (CERTIFIED or PROVISIONAL). This withholds the INCONCLUSIVE rows — bodies the harness could not exercise, which still exist and still ship. Leave this off (the default) to see them too; the withheld figure is reported as `certification.withheldInconclusive`.
  • component_class · string · optionnel
    Catalog only: restrict to one component class, e.g. `CrownJewel/S-Tier`, `Block/Engine`. Substring match.
  • include_siblings · boolean · optionnel
    With `ids`: also list up to 12 other component IDs in the same class, for comparison.

  Exemple d'appel

  {"name": "library_search", "arguments": {"ids": [], "key": "texte", "pack": "texte", "page": 1, "limit": 1, "query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_repos≈ 476 tokens

  Lists real repository names so a run never starts on a guessed one, and answers whether a repository can be written to. Pass `github_token` to see everything that token can see, or `owner` to list a public account's repositories; with neither, it lists the repositories the SHPBL GitHub App is installed on for this key — the same ones a pull request can be opened on. Pass `repo: "owner/name"` to ask about one target instead of reading the whole list. Free — costs no allowance.

  Paramètres, retour & exemple (6)

  Paramètres

  • key · string · optionnel
    Your SHPBL key (shpbl_mcp_…), only needed to list App-connected repositories. Optional if sent as the Authorization header.
  • page · integer · optionnel
    Which page of the connected-repository list to return, 1-based. Use this rather than a higher `limit` past 100; the response names the next page when there is one.
  • repo · string · optionnel
    Ask about one target, `owner/repo`: whether this key may open a pull request on it. Call this before offering to write.
  • limit · integer · optionnel
    How many repositories to return (default 30, max 100).
  • owner · string · optionnel
    A GitHub user or organisation to list the public repositories of, when no token is available.
  • github_token · string · optionnel
    A GitHub token (PAT or fine-grained) to list with. Never stored, never logged — used for this call only.

  Exemple d'appel

  {"name": "list_repos", "arguments": {"key": "texte", "page": 1, "repo": "texte", "limit": 1, "owner": "texte", "github_token": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• method_protocol≈ 191 tokens

  Return the SHPBL disciplines verbatim — evaluation, remediation and harvest — plus the component classes' verification axes and the reporting style. Free and unmetered. Fetch it once, then call `fix_repo` or `harvest_repo` with `brief: true` so their payload is source rather than repeated instructions.

  Paramètres, retour & exemple (1)

  Paramètres

  • stage · string · optionnel · evaluate | fix | harvest
    One stage only: `evaluate`, `fix` or `harvest`. Omit for all three.

  Exemple d'appel

  {"name": "method_protocol", "arguments": {"stage": "evaluate"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pin_source≈ 401 tokens

  Build `HOST-SOURCE-MANIFEST.json` for canonical step 1 from a GitHub repository, online, with no clone and no download: every file's Git blob identity, the byte length, the head commit, and the `SHPBL-SOURCE-DIGEST/1` digest over the pinned tree. Write the returned JSON to your run folder as `HOST-SOURCE-MANIFEST.json` and step 1 passes the gate. Free and unmetered. If the run is offline instead, do not call this — run `node tools/source-manifest.mjs <repo-dir|repo.zip>` from the edition, which produces the same manifest from a directory or straight out of the repository ZIP. Never invent the digest or the commit.

  Paramètres, retour & exemple (4)

  Paramètres

  • key · string · optionnel
    Your SHPBL key, if you have one. Optional — this tool is free; a key only helps reach a private repository through a connected GitHub App install.
  • repo · string · requis
    A GitHub repository: `owner/repo`, a github.com URL, or `owner/repo#branch`.
  • label · string · optionnel
    What to call the target in the manifest. Defaults to `owner/repo@branch`.
  • github_token · string · optionnel
    Optional GitHub token (Contents: read) for a private repository.

  Exemple d'appel

  {"name": "pin_source", "arguments": {"repo": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• run_contract≈ 504 tokens

  Read the canonical twelve-step run contract, or check a run bundle against it. Call it with no `files` to get the contract itself: every step's id, the artifacts it must produce, the exact condition that closes it, the terminal word to report when it does not, the instruction-precedence order, the retention rule and the two legal ends of step 12. Call it with `files` — a map of run-folder paths to their text — to get the machine verdict: which step blocked, which predicate refused and why. This is the identical implementation the offline `tools/run-gate.mjs` in every edition is bundled from, so the two cannot disagree about whether a bundle satisfies the contract. What they do not share is evidence: the offline gate checks the bundle you hand it, while a connected run can also confirm against the real repository tree that the files cited exist and say what the bundle claims. Same rules, one with a witness. Free, unmetered, read-only, stateless. Never infer a step, reorder one, or declare a run finished on your own reading — run the gate and report its word.

  Paramètres, retour & exemple (2)

  Paramètres

  • files · object · optionnel
    The run bundle as `path: text`, relative to the run folder (for example `STEP-LEDGER.json`). Send the canonical outputs you have; the gate says what is missing. Bounded: at most 400 entries and 8 MB of text in one call, and identical diagnostics are collapsed to one line with a count rather than repeated per entry. Omit this to read the contract without evaluating anything.
  • through_step · integer · optionnel
    Evaluate gates through this step only. Defaults to 12.

  Exemple d'appel

  {"name": "run_contract", "arguments": {"files": {}, "through_step": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• run_gauntlet≈ 1632 tokens

  One runner for an entire SHPBL repository audit and repair: survey, opening library comparison, evaluation, repair, the batched harvest, closing library comparison, the branded HTML report, and the write-back path. STRICT SEQUENCE: call it once with no `step` for the run card, then `step: 1`, `step: 2`, one step per turn, in order. Do the returned step, report one line to the person, then call the next. Never call two steps in one turn, never attempt the whole run at once, and never infer a finding you were not handed. From `step: 2` on you must pass `ledger_digest`; every 3 steps (adjustable with `checkpoint_interval`, max 10, only when the person asks for fewer pauses) the run pauses and you must ask the person before continuing, then pass `continue_ack: "continue"`. The final step hands over the report template and the write-back path. Your own model does all reading and writing. This full conductor requires a Practitioner key (7-day free trial). The free lane provides repository evaluation, not a partial or full gauntlet.

  Paramètres, retour & exemple (13)

  Paramètres

  • key · string · optionnel
    Your SHPBL Practitioner subscription key (shpbl_mcp_…). Optional if your client sends it as the `Authorization: Bearer …` request header.
  • repo · string · requis
    A GitHub repository: `owner/repo`, a URL, or `owner/repo#branch`.
  • step · number · optionnel
    0 to 2000. 0 (default) returns the run card and the plan with no source. 1…N walk the harvest batches, one per turn and in order. N+1 closes the run with the report template and the write-back path. Do not skip ahead.
  • budget · number · optionnel
    Characters per harvest step — a whole number from 10,000 to 120,000. Defaults to a moderate 45,000 so each step stays readable and cheap; raise it toward 90,000 only if the person asks for fewer, heavier steps.
  • include · string · optionnel
    Optional path filter — only paths containing this text are in scope for the whole run.
  • fold_token · string · optionnel
    The `fold_token` returned by the previous step, passed back verbatim. Required from `step: 2` onward: it is signed by this server and carries the previous step's number and the hash of the ledger you held then, so a step cannot be skipped and a ledger cannot be truncated or replaced. Never edit it, never write one yourself.
  • own_library · array · optionnel
    Your own previously harvested capabilities, read out of your repository's `.shpbl/` library and passed back in. Optional. When present, this run checks your concerns against your own library first and tells you which ones you already solved. It is held in memory for this call only — never stored, never added to SHPBL's library.
  • personality · string · optionnel
    How the person wants to be spoken to for this run: technical, professional, friendly, light, coach, deadpan. Ask them once before step 0 and pass what they choose; it rides the run and changes wording only, never a finding, a state or a gate. Defaults to professional when they have no preference. Pass `none` to switch the voice off entirely — bare wording, no openers, no asides — which is the right setting for an automated reviewer reading the run as evidence.
  • continue_ack · string · optionnel
    The person's approval to continue past a checkpoint. Every 3 harvest steps this run pauses: report to the person, ask whether to continue, and only when they say yes call the next step with `continue_ack: "continue"`. Never send it without asking.
  • github_token · string · optionnel
    Optional GitHub token (Contents: read) for a private repository. Not needed if the SHPBL GitHub App is connected to this key.
  • protocol_ack · boolean · optionnel
    Set true to say this session already holds the SHPBL protocol. The discipline, the ten meta capabilities, the hands-off list and the return shapes are then not printed on step 0 or step 1 — they are unchanged and they still bind the run. Use it when you have already called `method_protocol` or run a staged tool in this session; it saves tens of thousands of characters of repetition.
  • ledger_digest · string · optionnel
    The ledger folded so far, one line per capability, **each line carrying the file path it came from** (for example `src/lib/queue.ts — retry with backoff`). Required from `step: 2` onward — it is the proof that you actually folded the previous step — and required on the closing step so the closing library comparison runs against what you harvested. The server checks shape as well as length: a ledger that names no paths, or is padded out around one, is refused (and not charged).
  • checkpoint_interval · number · optionnel
    How many harvest steps between check-ins with the person. Defaults to 3; raise it (up to 10) only when the person has asked for fewer pauses. Never set it silently — the check-ins are how the person stays in the loop. Once set it rides inside the run's `fold_token`, so passing it again on later steps is not required; if you ever start a fresh chain, set it again or the run returns to 3.

  Exemple d'appel

  {"name": "run_gauntlet", "arguments": {"repo": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• selfcheck_mcp≈ 248 tokens

  Runs SHPBL's own audit against the running server and returns one pass/fail/unavailable line per verification axis: the registered tool surface against the priced tier table, version agreement across the published files, subscription-register reachability, catalog reachability, repository-write authority, and billing wiring. Free, unmetered, read-only — nothing is written and no model is called. Use it to prove the server is live and consistent before starting a run, or when a tool answered in a way that looks wrong.

  Paramètres, retour & exemple (1)

  Paramètres

  • verbose · boolean · optionnel
    Include the full tool-to-tier table and the axis definitions in the answer.

  Exemple d'appel

  {"name": "selfcheck_mcp", "arguments": {"verbose": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• subscription_status≈ 177 tokens

  Report the tiers of this MCP server and — from the `key` argument or the same `Authorization` header the gated tools read — that key's tier, status and month-to-date usage. This is the authoritative answer to "am I connected, and what do I have".

  Paramètres, retour & exemple (1)

  Paramètres

  • key · string · optionnel
    Optional SHPBL subscription key. Omit it if your client sends the key as a request header.

  Exemple d'appel

  {"name": "subscription_status", "arguments": {"key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• welcome≈ 203 tokens

  Call this first, once, when a person connects. Returns the welcome, the full tool menu with one line per tool, the exact sentences a person can say to start a run, the support address, and the link to the user's manual. Free, unmetered, no key. Read it to the person in your own words — warmly and briefly — then ask what they would like to point it at.

  Paramètres, retour & exemple (1)

  Paramètres

  • name · string · optionnel
    The person's first name, if you know it, so the greeting can use it.

  Exemple d'appel

  {"name": "welcome", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• write_to_repo≈ 1512 tokens

  Land finished work in a repository as a pull request: pass the files you wrote (full new contents, not diffs) and this opens a branch and a PR for the human to review and merge. Nothing is ever pushed to the default branch. Requires a SHPBL Practitioner key and the SHPBL GitHub App installed on that repository (or a one-off `github_token`). The caller chooses the repository — ask which one, or call `list_repos` first; never assume. Where things go: Harvest output belongs under `.shpbl/` in **the caller's own repository** — the person who asked for the run — and never in the repository that was harvested. Those are frequently not the same repository: a run may read a public open-source project, or a repository the caller merely has access to, and writing a harvest back into a source repository would be putting our output into somebody else's software. Sources a run may read: public repositories that carry a proper open-source license, the caller's own repositories, or private repositories the caller has access to. The server never reads a repository the caller has no right to read, and it never absorbs customer harvests back into the public library. - `.shpbl/README.md` — the index of their capability library (this tool scaffolds it when it is absent). - `.shpbl/<run-seal>/LEDGER.md` — the folded ledger for one run. - `.shpbl/<run-seal>/REPORT.html` — the branded report, if one was produced. - `.shpbl/<capability-name>/` — a capability kept as source, one folder each. - `.shpbl/COMPOSITES.md` — your own composites: capabilities this run invented for your repository by fusing parts that did nothing alone. Record each as `- <name> — <what it fuses> — <why neither part sufficed>`. These are yours and stay private; SHPBL's global composites ledger is fed only by Governor-keyed published runs, so never send yours anywhere and never expect them to appear there. If the harvested repository is not the caller's own, the harvest still lands in the caller's `.shpbl/` and the source is named in provenance. Ask the person which of their repositories is the home for their library if it is not obvious, and stop for that answer rather than guessing. Give each kept capability a one-line contract in `.shpbl/README.md`, in the form `- <name> — <path> — <contract>`. That index is what makes the library reusable: on the next run, read it and pass those entries as `own_library` to `evaluate_repo`, `fix_repo` or `run_gauntlet`, and the run will tell you which concerns you already solved before citing anything new. Those entries stay yours — they are held for the call and never stored by SHPBL. Repairs are the exception: write the repaired file at its own path, never under `.shpbl/`.

  Paramètres, retour & exemple (11)

  Paramètres

  • key · string · optionnel
    Your SHPBL subscription key (shpbl_mcp_…). Optional if your client sends it as the `Authorization: Bearer …` request header.
  • kind · string · optionnel · harvest | repair | foundry
    What this pull request lands. `harvest` means kept capabilities and a ledger: write them under `.shpbl/` and this scaffolds `.shpbl/README.md` as the index of their own capability library when it is missing. `foundry` means built software and its tests, landing under `.shpbl/` beside the index the same way a harvest does — only ever an artifact whose Build Intent `build_intent` authorised. `repair` means fixed files at their own paths, and nothing is scaffolded.
  • repo · string · requis
    The GitHub repository to write to: `owner/repo` or a URL.
  • files · array · requis
    Complete file contents to commit. For a repair, the whole fixed file — not a diff.
  • title · string · requis
    Pull request title — say what the change does.
  • branch · string · optionnel
    Branch to write on. Defaults to one derived from `run_id`, or `shpbl/<date>-<n>`; reusing a name appends to that PR.
  • run_id · string · optionnel
    A stable id for this piece of work (a harvest run seal, a repair order id). Retrying with the same run_id lands on the same branch and updates the same pull request instead of opening a second one. Prefer this over `branch`.
  • summary · string · requis
    Pull request body: the repair order, or the run seal and coverage of a harvest. Markdown.
  • base_ref · string · optionnel
    Branch to open against. Defaults to the repository's default branch.
  • github_token · string · optionnel
    One-off GitHub token with Contents and Pull requests write. Used for this call only and never stored. Omit it if the SHPBL GitHub App is installed.
  • build_authorization · array · optionnel
    The signed build authorizations `build_intent` returned, one per artifact this pull request lands. Required when `kind` is `foundry`: the server verifies each against its own Build Intent ledger and refuses to land an artifact it never gated.

  Exemple d'appel

  {"name": "write_to_repo", "arguments": {"repo": "texte", "files": [], "title": "texte", "summary": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://shpbl.com/api/public/mcp