MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
Nothing to run from here
Plumbline — a trust layer for LLM answers 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.
18
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Every figure re-checked against SQL-computed facts; unsupported questions refused with the reason.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http plumbline-a-trust-layer-for-llm-answers-mcp https://plumbline.lattice-sys.com/mcp/demo
# 2 — ask your agent for something these tools do
# ask_prepare, ask_result, ask_submit_draft and 15 more
Plumbline — a trust layer for LLM answers costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
LSAll 1 server
lattice-sys1 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 plumbline-a-trust-layer-for-llm-answers-mcp https://plumbline.lattice-sys.com/mcp/demoReconnect, 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
18 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.
BYO step 1 of 2: run the server-side trust plane for a business question (plan, SQL-verified facts, evidence retrieval, answerability gate, prompt composition) and return the composed prompt plus a single-use prepare_key (a signed handoff token; echo it back VERBATIM and in full, or use the short ask_id alias; in prose always say the ask_id, never the token). Read-only: prepare holds no server sta
| Parameter | Type | Required | Notes |
|---|---|---|---|
| history | null/array | no | optional prior conversation turns (role user|assistant) to thread into the composed prompt for follow-up questions |
| original_question | string | no | REQUIRED IF question is not the user's exact wording: the user's original question, verbatim, so the panel can display your revision as a revision. Omit when question is verbatim |
| question | string | yes | the business question to ground, in the USER'S OWN WORDS, verbatim; do not expand, narrow, or reword it — the server plans coverage itself. The server plans, computes SQL facts, retrieves evidence, ga |
Fetch the published verdict for an ask_prepare session (status: pending, published, or unknown). This is the app panel's polling surface, so the verified answer renders inside the panel that prepared the question. As the connected model you normally never need it: write your draft and call ask_submit_draft. Exception: if you are asked to submit for a session whose composed prompt is no longer in y
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include_prompt | boolean | no | set true to receive the pending session's composed prompt messages again, e.g. when the ask_prepare result is no longer in your context; the same caller already received this prompt at prepare time |
| prepare_key | string | yes | the session_id value returned by the prepare tool |
BYO step 2 of 2: verify the draft you wrote for an ask_prepare prompt. The server runs the SAME post-answer guards the strict path uses (facts presence, tagged claims, concept binding, earner-name grounding) against its own SQL facts and publishes the trust envelope; a draft that fails any guard is refused. Pass the prepare_key token back VERBATIM and in full. Handoffs are single-use per verdict a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| decline_reason | string | no | use INSTEAD of raw_answer when you are choosing not to submit a draft: state plainly why, in one or two sentences addressed to the user. The reason is shown to them in the panel, the handoff stays ope |
| model | string | no | optional: the model that wrote the draft, recorded in the trace |
| prepare_key | string | yes | the session_id value returned by the prepare tool |
| raw_answer | string | no | your COMPLETE raw draft answer to the composed prompt (including any structured answer/claims JSON the prompt's contract asked for). Omit ONLY when you are declining, in which case decline_reason is r |
Compare two departments by headcount and compensation. NOTE: internal drafting is disabled on this deployment. If your client supports MCP sampling, this tool asks YOUR model to draft in the same call (verified server-side); otherwise it returns an explicit refusal, and you should use ask_prepare then ask_submit_draft to draft with your own model.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| a | string | yes | the first department |
| b | string | yes | the second department |
Corroborate a figure you obtained (e.g. from run_sql) against the verified fact store: it re-derives the named value_key from the same SQL the verified pipeline uses and compares. AGREE lifts an otherwise-unverified session to 'corroborated'; DISAGREE marks a CONFLICT (worse than unverified). This is the only way a raw figure earns trust back, and it can only ever agree with a number the fact stor
| Parameter | Type | Required | Notes |
|---|---|---|---|
| value | string | yes | the figure you obtained (e.g. from run_sql) to corroborate against the verified fact store |
| value_key | string | yes | the claimable fact key naming the verified concept to re-derive, e.g. people, indexed_active_people, median_income_cents, or a per-department growth key like indexed_people.engineering (the keys a ver |
List safe metadata for the registered fact queries available on the server-pinned dataset: IDs, labels, parameters, and result shapes, never SQL. Use this when a question appears relevant but a selected route produced no facts; a route miss is not evidence that the underlying records are absent.
No parameter schema on file.
Surface payroll and deduction anomalies in the latest snapshot. NOTE: internal drafting is disabled on this deployment. If your client supports MCP sampling, this tool asks YOUR model to draft in the same call (verified server-side); otherwise it returns an explicit refusal, and you should use ask_prepare then ask_submit_draft to draft with your own model.
No parameter schema on file.
Return the Art. 13 transparency descriptor: intended purpose, capabilities, limitations, human oversight, logging mechanism, and article mapping.
No parameter schema on file.
Show the SQL behind one answer you already received, addressed by its correlation_id. Returns only the recorded fact queries (id, version, label, SQL, parameters, result schema, dataset version) for that answer: no rows, no evidence text, no answer text, no envelope, and no way to list the catalog. Recorded SQL has its arguments inlined as literals, so a query that filters on a specific value disc
| Parameter | Type | Required | Notes |
|---|---|---|---|
| correlation_id | string | yes | the correlation_id published on the answer whose queries you want to see; obtained from that answer, never guessed |
Show ONE retrieved evidence document behind an answer you already received, addressed by that answer's correlation_id plus a document_id from its evidence_documents references. Returns the full stored document (title, body, metadata, embedding_text) with the retrieval rank and scores the answer recorded; never the raw embedding vector. Only documents the addressed answer actually recorded resolve:
| Parameter | Type | Required | Notes |
|---|---|---|---|
| correlation_id | string | yes | the correlation_id published on the answer whose evidence you want to inspect; obtained from that answer, never guessed |
| document_id | integer | yes | the document_id of one entry in that answer's evidence_documents references |
Return the management/reporting chain for an employee. NOTE: internal drafting is disabled on this deployment. If your client supports MCP sampling, this tool asks YOUR model to draft in the same call (verified server-side); otherwise it returns an explicit refusal, and you should use ask_prepare then ask_submit_draft to draft with your own model.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| employee | string | yes | the employee whose management chain to return |
Execute a registered, versioned read-only fact query against the server-pinned dataset. Provide query_id and version only: SQL is approved by the domain pack, never caller-supplied. Returns normalized rows plus a reproducible trust receipt containing the dataset and query versions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| parameters | object | no | optional typed values for parameters declared by the registered query |
| query_id | string | yes | registered fact-query id; SQL is resolved by the server and must not be supplied here |
| version | string | yes | immutable registered query version |
Run YOUR OWN JavaScript in the in-tenant coderunner sandbox with the read-only, snapshot-scoped plumb.query() SDK. No filesystem, environment, or general network access. Read plumbline://sandbox-api.d.ts before writing code. The raw-SQL server opt-in is enabled, but results still bypass the trust path and are UNVERIFIED. Returns stdout/stderr plus metadata-only host-call trace evidence.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| acknowledge_unverified | boolean | no | set true to confirm you understand results BYPASS the trust plane and are UNVERIFIED, and that you will label them so to the user. On deployments with the acknowledgment gate the FIRST raw call of a s |
| code | string | yes | JavaScript source to execute in the in-tenant coderunner sandbox. No filesystem, environment, or general network access. When the server explicitly enables raw SQL and uses the local grant-capable run |
| concepts | null/array | no | optional: the fact concepts this code computes, as claimable fact keys (e.g. median_income_cents) or free-form names. The server reports per concept whether a registered seed exists (cross_check can c |
Run YOUR OWN single read-only SELECT/WITH over the virtual snapshot_* relations. The query is statically verified against an allowlist, rewritten to the active snapshot, and run read-only. This BYPASSES the planner, grounding gate, and answer-facts reconciliation, so results are UNVERIFIED and labelled as such. Deployments may refuse the FIRST raw call of a session pending acknowledge_unverified:
| Parameter | Type | Required | Notes |
|---|---|---|---|
| acknowledge_unverified | boolean | no | set true to confirm you understand results BYPASS the trust plane and are UNVERIFIED, and that you will label them so to the user. On deployments with the acknowledgment gate the FIRST raw call of a s |
| concepts | null/array | no | optional: the fact concepts this query computes, as claimable fact keys (e.g. median_income_cents) or free-form names. The server reports per concept whether a registered seed exists (cross_check can |
| sql | string | yes | a single read-only SELECT/WITH over the VIRTUAL snapshot_* relations (e.g. snapshot_employees, snapshot_pay_statements, snapshot_departments). Bare physical table names are rejected. Discover the colu |
Search Plumbline's own product and architecture documentation (how the verification, refusal, and trust layer itself works). Returns ranked, citable doc passages; does NOT touch employment data, and returns an empty result set honestly when nothing matches.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | max passages to return (default 5, capped at 10) |
| query | string | yes | a how-does-this-work question about Plumbline itself, e.g. the verification gate, snapshots and temporal drift, or the cross-provider corpus |
Search the employment fact store for a person and return a grounded, verified answer. NOTE: internal drafting is disabled on this deployment. If your client supports MCP sampling, this tool asks YOUR model to draft in the same call (verified server-side); otherwise it returns an explicit refusal, and you should use ask_prepare then ask_submit_draft to draft with your own model.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | the employee name or search terms |
Summarize benefit enrollments, optionally scoped (e.g. a department or plan). NOTE: internal drafting is disabled on this deployment. If your client supports MCP sampling, this tool asks YOUR model to draft in the same call (verified server-side); otherwise it returns an explicit refusal, and you should use ask_prepare then ask_submit_draft to draft with your own model.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scope | string | no | optional scope such as a department or benefit plan |
Return the session's graded trust verdict: the tier (verified / registered-query / generated-sql / corroborated / unverified / conflict / refused), which trusted steps were skipped across the session, the deterministic confidence (k of n figures store-verified, weakest figure tier, conflicts), the per-figure provenance, the per-call ledger, and the at-your-own-risk disclaimer.
No parameter schema on file.
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 Plumbline — a trust layer for LLM answers 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 0.1.0.
0.1.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 Plumbline — a trust layer for LLM answers 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.