Elliot
MCPB · ELLIOT-MCP-0.6.0.MCPB
Independent verifier for AI agents: checks agent claims and doc promises against the code.
Available components
Last scanned (9 hours ago)
Scores higher than 76% of MCPB servers
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security23
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs were checked across the 92 of 92 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 11 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2125 tokens (~151/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 27 Oct 26 +1
- Security disclosure: fail → pass ▲ functional
- 24 Oct 26 45
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed mcpb/https://github.com/EmanueleCell4/elliot-mcp/releases/download/v0.6.0/elliot-mcp-0.6.0.mcpb@0.6.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
elliot_audit_finish Finish the audit and write the report ~96
Close the audit and write report.html, report.md and claims.json into elliot-report/<date>-<commit>/ at the repository root.
| Name | Type | Req | Description |
|---|---|---|---|
| audit_id | string | yes | – |
| out_dir | string | – | Override the output folder (relative to the repository root). |
| skipped | array | – | Risk-sweep items you looked at and decided need no claim, each with a reason. They are listed in the report. |
No output schema declared.
No examples provided.
elliot_audit_start Start a claim audit ~109
Start auditing whether this repository does what its README, docs and security/pricing pages say. Pins the commit, lists the files that make claims, and returns the protocol to follow.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Any path inside the repository (default: the server's working directory). |
| sources | array | – | Audit only the claims made in these repo-relative files, e.g. a pull request description saved as .elliot-pr/PR.md. Turns off the repo-wide risk sweep. |
No output schema declared.
No examples provided.
elliot_record_behavior Record undisclosed risky behavior ~185
Record something risky the code does that the docs never mention (for example, it sends usage events, stores a key in plain text, or skips permission prompts) and no doc sentence promises otherwise. If a doc sentence does promise otherwise, use elliot_record_claim on that sentence instead. Never attach this to an unrelated sentence.
| Name | Type | Req | Description |
|---|---|---|---|
| audit_id | string | yes | – |
| behavior | string | yes | What the code does, plainly, e.g. 'Sends the user email to PostHog on login'. |
| docs_searched | string | yes | Where you looked in the docs and found nothing about it. |
| evidence | array | yes | Code that does it. |
| severity | string | yes | – |
| signal | string | – | The code signal id from the risk sweep that led here, if any. |
| user_impact | string | yes | Who is affected and how. |
No output schema declared.
No examples provided.
elliot_record_claim Record one audited claim ~314
Submit one claim with its verdict and evidence. Elliot checks that the claim's source quote is really in the docs at those lines, that every evidence quote is really in the code at those lines, and runs every 'absent' search itself. If anything does not check out the claim is rejected: fix the citation and submit again.
| Name | Type | Req | Description |
|---|---|---|---|
| audit_id | string | yes | – |
| claim | string | yes | The claim, quoted or tightly paraphrased, as a user would read it. |
| evidence | array | yes | Code that implements or contradicts the claim. Use type 'absent' when the claimed thing does not exist in code. |
| explanation | string | yes | One or two plain sentences: what the code actually does. |
| note | string | – | For VERIFIED: a minor gap worth mentioning that misleads nobody. |
| severity | string | – | Required for PARTIAL and FALSE: how much a user relying on the claim is hurt. |
| source | object | yes | Where the project makes the claim. |
| user_impact | string | – | Required for PARTIAL and FALSE: what a user who relies on this sentence would get wrong, concretely. If there is no real consequence, use VERIFIED with a note. |
| verdict | string | yes | VERIFIED: the code implements it. PARTIAL: implemented with a material gap or narrower than claimed. FALSE: the code contradicts it or the feature does not exist. UNVERIFIABLE: depends on a deploymen… |
No output schema declared.
No examples provided.
elliot_record_review Record an independent review decision ~201
For the reviewer process: confirm, downgrade or reject one finding. In isolated mode provide the audit-scoped reviewer_token from the evidence packet. Confirm needs evidence you checked yourself (a code quote or an absent search); reject needs a code quote showing the claim holds. All evidence is checked against the files.
| Name | Type | Req | Description |
|---|---|---|---|
| audit_id | string | yes | – |
| evidence | array | – | – |
| finding | string | yes | The finding id, e.g. 3 or b1. |
| outcome | string | yes | confirm: real and material (pass severity to change it, e.g. low). downgrade: the mismatch is real but immaterial and becomes a note; do not pass a severity. reject: the claim actually holds. |
| reason | string | yes | – |
| reviewer_token | string | – | Per-audit capability included in the evidence packet when isolated review is enabled. |
| severity | string | – | Corrected severity, when the auditor's is wrong. |
No output schema declared.
No examples provided.
elliot_report Honesty report ~55
Summarise recent receipts: how many claims were checked and how many held up. Show this to the user when they ask what the agent really did.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many recent receipts (default 50). |
No output schema declared.
No examples provided.
elliot_review_packet Get the independent review packet ~70
Returns only findings and checked evidence for review. Give it to a fresh reviewer process. With ELLIOT_REVIEW_TOKEN configured, the auditor endpoint cannot record review decisions; connect the reviewer only to a separate ELLIOT_ROLE=reviewer server.
| Name | Type | Req | Description |
|---|---|---|---|
| audit_id | string | yes | – |
No output schema declared.
No examples provided.
elliot_snapshot Snapshot the working tree ~56
Fingerprint every tracked and untracked file in the git repository before starting a task, so verify_changes can later prove what really changed.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Any path inside the repository (default: the server's working directory). |
No output schema declared.
No examples provided.
verify_attestation Verify a signed receipt ~87
Verify an Ed25519-signed Elliot receipt and its digest. Returns valid=true only when the signature passes and an explicitly supplied public key matches; without one it reports cryptographic validity but marks signer identity untrusted.
| Name | Type | Req | Description |
|---|---|---|---|
| public_key | string | – | Public key independently trusted by the verifier. Omit to check only mathematical signature validity; valid remains false. |
| receipt | object | yes | – |
No output schema declared.
No examples provided.
verify_changes Verify files actually changed ~116
Check whether files really changed, compared with a snapshot taken before the task (or with HEAD if no snapshot is given). Use before claiming code was fixed, cleaned, refactored or written.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | – | The claim being checked, in the agent's own words, e.g. 'Deployed the landing page'. |
| path | string | – | Any path inside the repository. |
| paths | array | – | Only count changes under these repo-relative paths. |
| snapshot_id | string | – | Id returned by elliot_snapshot. |
No output schema declared.
No examples provided.
verify_github Verify a GitHub claim ~116
Check what GitHub actually says: whether a PR is merged, whether CI checks passed on a PR or commit, or whether a commit/branch was really pushed. Set GITHUB_TOKEN for private repos.
| Name | Type | Req | Description |
|---|---|---|---|
| check | string | yes | – |
| claim | string | – | The claim being checked, in the agent's own words, e.g. 'Deployed the landing page'. |
| pr | integer | – | Pull request number. |
| ref | string | – | Commit sha or branch name. |
| repo | string | yes | owner/name |
No output schema declared.
No examples provided.
verify_npm Verify an npm package was published ~119
Check the npm registry for a package and version. Use before claiming a package or release was published.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | – | The claim being checked, in the agent's own words, e.g. 'Deployed the landing page'. |
| name | string | yes | Package name, e.g. 'zod' or '@scope/pkg'. |
| published_after | string | – | ISO time the version must have been published after (proves it is a new publish). |
| version | string | – | Exact version; defaults to the latest dist-tag. |
No output schema declared.
No examples provided.
verify_outcome Run a functional check in isolation ~218
Run a command and arguments in a disposable repository copy under the host OS sandbox. Writes stay in the copy, network is blocked, and VERIFIED requires exit code zero. For a shell pipeline use command bash with args ["-c", "..."]; Elliot adds set -o pipefail so a failing step is not hidden by the last one. Put every file the check needs in the repository: files elsewhere (such as /tmp scripts) do not exist inside the sandbox. If the OS sandbox cannot start, returns INCONCLUSIVE without running the command.
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | – | Executable arguments, e.g. ["test"] for npm test. |
| claim | string | – | The claim being checked, in the agent's own words, e.g. 'Deployed the landing page'. |
| command | string | yes | Executable, for example npm, node or pytest. No shell is used. |
| path | string | – | Repository path (default: server working directory). |
| timeout_ms | integer | – | Timeout, default 120000ms. |
No output schema declared.
No examples provided.
verify_url Verify a URL is live ~126
Check that a URL (a deploy, a preview, a page) actually responds with the expected status and, optionally, contains expected text. Use before claiming something is deployed or live.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | – | The claim being checked, in the agent's own words, e.g. 'Deployed the landing page'. |
| expect_status | integer | – | Expected HTTP status (default 200). |
| expect_text | string | – | Text that must appear in the response body, e.g. a headline you just shipped. |
| url | string | yes | The URL that should be live. |
No output schema declared.
No examples provided.
How do I install the Elliot MCP server?
Elliot ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, a56fcfb4947b80854173b4df3bdcaaf7cbcc6d049917615c73783c39ce7be2eb; the commands to do that are on this page. If it does not match, do not open it.
mcpb · elliot-mcp-0.6.0.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
a56fcfb4947b80854173b4df3bdcaaf7cbcc6d049917615c73783c39ce7be2eb
macOS / Linux
echo "a56fcfb4947b80854173b4df3bdcaaf7cbcc6d049917615c73783c39ce7be2eb elliot-mcp-0.6.0.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\elliot-mcp-0.6.0.mcpb).Hash -eq "a56fcfb4947b80854173b4df3bdcaaf7cbcc6d049917615c73783c39ce7be2eb"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the Elliot MCP server?
Elliot is an MCP server listed in the public MCP registry as io.github.EmanueleCell4/elliot-mcp. Independent verifier for AI agents: checks agent claims and doc promises against the code. This page covers its MCPB bundle (https://github.com/EmanueleCell4/elliot-mcp/releases/download/v0.6.0/elliot-mcp-0.6.0.mcpb).
Is the Elliot MCP server safe to use?
Elliot scores 46 out of 100 on VerifyMCP. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Elliot MCP server expose?
Elliot exposes 14 tools: verify_url, verify_outcome, verify_attestation, verify_github, verify_npm, and 9 more. Their descriptions and schemas cost roughly 1,868 tokens of context every time the server is loaded.
What licence is the Elliot MCP server under?
Elliot declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.