MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
Nothing to run from here
Governance Platform is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
37
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Pre-execution governance for AI agents. Deterministic PASS/FAIL/REVIEW verdicts, replayable proof.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http governance-platform-mcp https://app.geodesiclabs.ai/mcp
# 2 — ask your agent for something these tools do
# validate, validate_repair, create_blueprint and 34 more
Governance Platform costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
AGAll 1 server
app.geodesiclabs.ai1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http governance-platform-mcp https://app.geodesiclabs.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
37 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Validate structured data against a Blueprint's rules BEFORE the result is used. Returns PASS, FAIL, or REVIEW with plain-language findings, repair suggestions, a determinism hash, and a re-verifiable certificate. Same input + same rules = same verdict, every time.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| structured_data | object | yes | The document's extracted fields as key/value pairs. Keys are open by design - your Blueprint's rules define what is checked |
| blueprint | string | no | Blueprint name (workflow_name) to use |
| source_text | no | Optional. The text of the document the fields were extracted from. When the Blueprint has a source check, extracted values are compared against this text. It is used for the check only and is not stor |
Validate structured data against a Blueprint and, when it fails, include repair suggestions (corrected values with the rule each fix is based on) in the same call. Same verdicts as validate: PASS, FAIL, or REVIEW, with reasons and proof.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| structured_data | object | yes | The document's extracted fields as key/value pairs. Keys are open by design - your Blueprint's rules define what is checked |
| blueprint | string | no | Blueprint name (workflow_name) to use |
Create a Blueprint - the governance contract validation runs against. A Blueprint defines what correct means for your data: fields, the math that must hold between them, and acceptable ranges. Start from load_rule_pack or discover_patterns if you have no rules yet; invoke the blueprint_guide prompt for the full rule/constraint reference. Returns the new Blueprint's API key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| customer_name | string | yes | Organization or project name (also used for storage folder naming) |
| workflow_name | string | yes | Unique Blueprint identifier; the value passed as 'blueprint' in validate |
| mode | string | no | observe: platform checks the agent's work; enforce: platform computes derived fields itself |
| extracted_fields | array | no | Field names the agent extracts from source data, e.g. ['vendor','qty','unit_cost'] |
| derived_fields | array | no | Field names the platform computes from other fields, e.g. ['subtotal','total'] |
| derivation_rules | array | no | Math rules as objects. Types: add, subtract, multiply, divide, round, copy, sum (multi-operand), items_multiply, items_sum. Each needs 'type' plus its fields; see the blueprint_guide prompt |
| formal_constraints | array | no | Constraint objects. Types incl. magnitude_anchor {field,min,max}, relative_anchor {field,reference_field,ratio_min,ratio_max}, max_action_threshold {field,threshold,on_violation}, required_fields {fie |
| semantic_checks | array | no | Domain-specific semantic check objects |
| require_math | boolean | no | Validate mathematical relationships |
| require_consistency | boolean | no | Check internal field consistency |
| require_coherence | boolean | no | Check cross-field plausibility |
| require_provenance | boolean | no | Require extraction source locations for fields |
| require_high_assurance | boolean | no | Strictest mode: every check must pass |
| enable_anomaly_detection | boolean | no | Flag records that break no rules but do not fit the reference pattern |
| enable_drift_tracking | boolean | no | Track pattern stability across batches |
List the Blueprints on this account with field/rule/constraint counts and mode. Use the returned workflow_name as 'blueprint' in validate.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
One-shot repair: return corrected values that would make failing data valid under the Blueprint. Use repair_path to see the steps instead.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| structured_data | object | yes | The document's extracted fields as key/value pairs. Keys are open by design - your Blueprint's rules define what is checked |
| derivation_rules | array | no | Math rules as objects. Types: add, subtract, multiply, divide, round, copy, sum (multi-operand), items_multiply, items_sum. Each needs 'type' plus its fields; see the blueprint_guide prompt |
| formal_constraints | array | no | Constraint objects. Types incl. magnitude_anchor {field,min,max}, relative_anchor {field,reference_field,ratio_min,ratio_max}, max_action_threshold {field,threshold,on_violation}, required_fields {fie |
| blueprint | string | no | Blueprint name (workflow_name) to use |
Static pre-deploy analysis of a Blueprint's rule set. Returns a health verdict - healthy, acceptable, fragile, rigid, split, brittle_islands, or unsatisfiable - with advice, including joint conflicts pairwise checks miss.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| blueprint | string | no | Blueprint name (workflow_name) to use |
| config | object | no | Raw blueprint config with derivation_rules and formal_constraints (used when 'blueprint' is not given) |
Compare two payloads under the dual-hash design: content_hash is content_hash normalizes field order and numeric formatting. Semantic comparison preserves field roles; renaming requires an explicit bijection. With supplied rules, scalar types and whitespace remain significant. Structural similarity alone does not establish decision equivalence.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| payload_a | object | yes | First structured payload (arbitrary JSON object) |
| payload_b | object | yes | Second structured payload to compare against payload_a |
| field_mapping | object | no | Explicit one-to-one field renaming from A to B |
| rules_a | array | no | Derivation rules for A |
| rules_b | array | no | Derivation rules for B |
| constraints_a | array | no | Formal constraints for A |
| constraints_b | array | no | Formal constraints for B |
Quality-govern an in-progress AI generation step BEFORE its output is used (complements validate, which checks finished documents). Returns an action - STOP, CONTINUE, REPAIR_REGION, REUSE_MOTIF, REVIEW, ESCALATE - with a plain-language explanation. Structural scores do not establish task correctness. Check safe_to_finalize and acceptance coverage. Persistence success is report
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| task_type | string | yes | Kind of generation step being governed |
| payload | object | yes | Task-type payload: generative_text {text,...}; retrieval {query,candidates}; generic {features} |
| inference_id | string | yes | Caller-chosen ID grouping the steps of one generation |
| constraints | object | no | Optional governance constraint config object |
| source | string | no | Free-form caller label recorded for audit |
| step_index | integer | no | Step number within this generation (0-based) |
| blueprint | string | no | Owned Blueprint namespace for the trace |
Retrieve the durable audit trail for a governed generation: every recorded decision and its reasons.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| inference_id | string | yes | Caller-chosen ID grouping the steps of one generation |
| blueprint | string | no | Blueprint namespace used when recording the trace |
| blueprint_version | string | no | Optional historical blueprint_version hash returned by govern_inference |
Recent generation-governance decisions in this owner's Blueprint version.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| limit | integer | no | Maximum rows to return |
| action | string | no | Optional action filter (STOP, CONTINUE, REVIEW, ...) |
| blueprint | string | no | Blueprint namespace used when recording the trace |
| blueprint_version | string | no | Optional historical blueprint_version hash returned by govern_inference |
Independently re-verify a validation certificate. Integrity mode checks the hash chain; full mode (certificate + original data) recomputes every attested rule from scratch - trust nothing, recheck everything.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| certificate | object | yes | The certificate object from a prior validation response |
| data | object | no | Original payload for full re-verification; omit for integrity-only mode |
| derivation_rules | array | no | Rule list for independent attestation recomputation (optional) |
| formal_constraints | array | no | Optional constraints to match against the committed bundle |
Sweep the Blueprint's numeric constraint bounds and report verdict stability: the stable band, the scales where the verdict first flips, and advice. Use before deploying bound changes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| blueprint | string | no | Blueprint name (workflow_name) to use |
| config | object | no | Raw blueprint config to profile (used when 'blueprint' is not given) |
Deterministic forward reasoning: from the current data state, generate and rank the valid next states reachable under the Blueprint's rules.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| structured_data | object | yes | The document's extracted fields as key/value pairs. Keys are open by design - your Blueprint's rules define what is checked |
| blueprint | string | no | Blueprint name (workflow_name) to use |
| max_depth | integer | no | Search depth, 1-10 |
| max_branches | integer | no | Branches per step, 1-10 |
| rank_by | string | no | Ranking criterion for returned paths |
Learn candidate validation rules and structural document types from a batch of your records, deterministically - no Blueprint required. Promote results with approve_rule. Source data is not stored.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| documents | array | yes | List of structured records (objects) to analyze |
| blueprint | string | no | Blueprint name (workflow_name) to use |
Find the shortest sequence of field changes taking invalid data to a valid state, as an ordered path of intermediate states. Different from repair (one-shot nearest fix): use repair_path to explain or audit the fix, or compare alternative repairs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| structured_data | object | yes | The document's extracted fields as key/value pairs. Keys are open by design - your Blueprint's rules define what is checked |
| blueprint | string | no | Blueprint name (workflow_name) to use |
| max_depth | integer | no | Search depth, 1-10 |
| rank_by | string | no | Ranking criterion for returned paths |
Run the same data under two rule sets and compare which future states remain valid - what-if analysis for rule changes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| structured_data | object | yes | The document's extracted fields as key/value pairs. Keys are open by design - your Blueprint's rules define what is checked |
| blueprint | string | no | Blueprint name (workflow_name) to use |
| rules_b | array | no | Alternative derivation rules (rule set B) |
| constraints_b | array | no | Alternative constraints (rule set B) |
Explain whether a record fits the usual pattern for records like it, and which fields stand out. No Blueprint required.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| structured_data | object | yes | The document's extracted fields as key/value pairs. Keys are open by design - your Blueprint's rules define what is checked |
| blueprint | string | no | Discovery namespace used by discover_patterns |
Create a multi-agent sequential chain: stages validate in order against one Blueprint, repairs propagate forward, TTL bounds the run. Siblings: submit_chain_stage advances the chain; handoff_audit verifies a transition between stages. Returns chain_id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| blueprint | string | yes | Blueprint governing all stages of the chain |
| stages | array | yes | Stage definitions, e.g. [{'stage_name':'extract','agent_name':'PDF Agent'}]; minimum 2 |
| ttl | integer | no | Chain timeout in seconds; stages cannot advance after expiry |
Submit data for the chain's current stage; the platform validates it and advances the chain if it passes. Response includes next-stage info and accumulated repairs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| chain_id | string | yes | Chain identifier returned by create_chain |
| stage | string | yes | Stage name to submit for (must be the chain's current stage) |
| structured_data | object | yes | The document's extracted fields as key/value pairs. Keys are open by design - your Blueprint's rules define what is checked |
Audit a handoff between two chain stages: a context capsule of verified facts from the prior stage, and (if proposed_data is given) a compatibility verdict that catches fields mutated in transit. Siblings: create_chain, submit_chain_stage.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| chain_id | string | yes | Chain identifier returned by create_chain |
| from_stage | string | yes | Completed stage name (agent A) |
| to_stage | string | yes | Stage about to start (agent B) |
| proposed_data | object | no | Data agent B intends to submit; checked for mutation against agent A's verified fields |
Promote a rule discovered by discover_patterns into Blueprint-ready form.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| rule_id | string | yes | Discovered rule ID from discover_patterns |
| blueprint | string | no | Blueprint name (workflow_name) to use |
Reject a discovered candidate rule so it will not be promoted into a Blueprint. Pair with approve_rule after discover_patterns.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| rule_id | string | yes | Discovered rule ID from discover_patterns |
| blueprint | string | no | Blueprint name (workflow_name) to use |
Retrieve the document categories a discover_patterns session identified (counts, distinguishing fields, domain hints). Read-only; returns status=no_session if discovery has not run for this namespace.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| blueprint | string | no | Blueprint name (workflow_name) to use |
Measure the numeric difference between original and corrected values: how much lies along the supplied linear rule directions (projection) and how much lies outside them (residual), with per-field contributions. Diagnostic only: it does not establish a cause, and neither record is verified. Use with a known-correct version to diff against; use analyze_anomaly when you only have
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| original_values | object | yes | Original numeric field values as {field: number} |
| corrected_values | object | yes | Corrected/expected numeric field values as {field: number} |
| derivation_rules | array | no | Math rules as objects. Types: add, subtract, multiply, divide, round, copy, sum (multi-operand), items_multiply, items_sum. Each needs 'type' plus its fields; see the blueprint_guide prompt |
| formal_constraints | array | no | Constraint objects. Types incl. magnitude_anchor {field,min,max}, relative_anchor {field,reference_field,ratio_min,ratio_max}, max_action_threshold {field,threshold,on_violation}, required_fields {fie |
| blueprint | string | no | Load rules from this Blueprint instead of passing them inline |
Summarize an already-computed state_vector into a confidence level (high/medium/low) with a recommendation. Post-hoc digest - use analyze_anomaly or check_drift for fresh analysis of raw data.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| state_vector | object | yes | state_vector object from a prior validate or get_execution_trace result |
Structural realization analysis of a payload against the Blueprint's reference configuration (requires a 'realization' block; otherwise status=skipped). Diagnostics-tier tool; prefer validate or analyze_anomaly for standard checks.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| structured_data | object | yes | The document's extracted fields as key/value pairs. Keys are open by design - your Blueprint's rules define what is checked |
| blueprint | string | no | Blueprint name (workflow_name) to use |
Check whether recent submissions still match the established pattern for this Blueprint. Returns a stability verdict and observation count.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| structured_data | object | yes | The document's extracted fields as key/value pairs. Keys are open by design - your Blueprint's rules define what is checked |
| blueprint | string | no | Blueprint name (workflow_name) to use |
Go/no-go for a real-world action (payment, filing, API write): runs full validation, then the Blueprint's execution gate. authorized=true only on PASS; REVIEW means do not proceed automatically. Different from validate: validate asks is this data correct, authorize_execution asks should this action happen.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| structured_data | object | yes | The document's extracted fields as key/value pairs. Keys are open by design - your Blueprint's rules define what is checked |
| blueprint | string | yes | Blueprint name (workflow_name) to use |
Load a prebuilt Blueprint template (invoices, timecards, legal, POs, claims). Call without pack_id to list packs; then create_blueprint to save a customized copy.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| pack_id | string | no | Rule pack ID; omit to list available packs |
Run validation and return the per-node execution trace (node names, deterministic flags, timing) plus the verdict and determinism hash. Use validate for normal operation; this is for debugging and audit preparation.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| structured_data | object | yes | The document's extracted fields as key/value pairs. Keys are open by design - your Blueprint's rules define what is checked |
| blueprint | string | no | Blueprint name (workflow_name) to use |
Check replay commitment integrity and compare recorded execution components. Version 4 includes reference context and the final result/status. A match compares commitments; this tool does not rerun the workflow or reconstruct historical reference populations, and does not prove factual correctness.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| contract_a | object | yes | replay_contract object from one execution |
| contract_b | object | yes | replay_contract object to compare against contract_a |
This account's plan, key usage, Blueprint counts, and the deployed platform build fingerprint (version, build, deployed).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
Permanently delete a Blueprint and revoke its API keys. Irreversible; requires confirm=true. Account-level keys are unaffected.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| workflow_name | string | yes | Blueprint to delete; its API keys are revoked |
| confirm | boolean | no | Must be true to confirm this irreversible action |
Update an existing Blueprint in place. Only passed fields change; pass [] to clear a list. workflow_name cannot be renamed and existing API keys keep working. Different from create_blueprint: modifies an existing Blueprint, mints no new key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| workflow_name | string | yes | Unique Blueprint identifier; the value passed as 'blueprint' in validate |
| customer_name | string | no | Organization or project name (also used for storage folder naming) |
| mode | string | no | New mode: observe or enforce; omit to keep current |
| extracted_fields | array | no | Field names the agent extracts from source data, e.g. ['vendor','qty','unit_cost'] |
| derived_fields | array | no | Field names the platform computes from other fields, e.g. ['subtotal','total'] |
| derivation_rules | array | no | Math rules as objects. Types: add, subtract, multiply, divide, round, copy, sum (multi-operand), items_multiply, items_sum. Each needs 'type' plus its fields; see the blueprint_guide prompt |
| formal_constraints | array | no | Constraint objects. Types incl. magnitude_anchor {field,min,max}, relative_anchor {field,reference_field,ratio_min,ratio_max}, max_action_threshold {field,threshold,on_violation}, required_fields {fie |
| semantic_checks | array | no | Domain-specific semantic check objects |
| require_math | boolean | no | Validate mathematical relationships |
| require_consistency | boolean | no | Check internal field consistency |
| require_coherence | boolean | no | Check cross-field plausibility |
| require_provenance | boolean | no | Require extraction source locations for fields |
| require_high_assurance | boolean | no | Strictest mode: every check must pass |
| enable_anomaly_detection | boolean | no | Flag records that break no rules but do not fit the reference pattern |
| enable_drift_tracking | boolean | no | Track pattern stability across batches |
List this account's API keys (masked) with their Blueprint bindings.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
Replace an API key with a fresh one. The old key stops working immediately; the new key inherits its bindings.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| key_to_rotate | string | yes | The gai_ key to rotate; it stops working immediately |
Permanently delete one of the caller's API keys. DESTRUCTIVE — agents using the deleted key will receive auth errors immediately. The Blueprint a key was tied to (if any) is NOT affected; only the credential is revoked. To delete a Blueprint and all its keys, use delete_blueprint. The target key can be specified two ways: - As the full key string (gai_...). - As a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | GeodesicAI API key (gai_...) |
| key_to_delete | string | yes | The gai_ key to delete |
| confirm | boolean | no | Must be true to confirm this irreversible action |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Governance Platform or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.27.0.
1.27.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Governance Platform can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.