socseal settlement door
MCPB · SOCSEAL-MCP.MCPB
Read-only settlement proof for agents: prove a txid MINED, post-quantum signed. Fail-closed.
Available components
Last scanned (7 hours ago)
Scores higher than 76% of MCPB servers
Category Crypto and Web3
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 Security0
- 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 could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 14 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 268 tokens (~89/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +6
- Stability: unverified → 0.40 ▲ functional
- 2 Oct 26 34
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 17 Oct 2026 · Analysed mcpb/https://github.com/Aeliana139/socseal-mcp/releases/download/v1.0.0/socseal-mcp.mcpb
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 →
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 →
anchor_receipt ~94
Confirm an anchor stamp is on-chain: given a txid, report SEPTA mined status (height>0, out of mempool) from the keeper, and if that txid is a known settlement-book anchor, return its full record (block, atoms, sealed text, verify status). Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| txid | string | yes | 64-hex transaction id (e.g. a book anchor txid) |
No output schema declared.
No examples provided.
book_status ~77
Read the public settlement book for a day: day number, status, merkle roots (root_open/root_close), clearing summary and the on-chain anchor (block, txid, verify status). Read-only public mirror. Use this to audit the venue's market history.
| Name | Type | Req | Description |
|---|---|---|---|
| day | integer | – | book day number (1 = first day) |
No output schema declared.
No examples provided.
verify_settlement ~97
Prove a transaction id actually MINED on-chain (SEPTA: height>0 and out of mempool). Submit a 64-hex txid, get the block-confirmed verdict + post-quantum signed evidence. Fail-closed: unknown/never-mined ids return a clean negative, never a fake success. Read-only; does not pay.
| Name | Type | Req | Description |
|---|---|---|---|
| txid | string | yes | 64-hex transaction id |
No output schema declared.
No examples provided.
How do I install the socseal settlement door MCP server?
socseal settlement door 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, ce820630632212d6b266f2b0ae0daeac339de9f2cd57496187e5d0c4c8e188f2; the commands to do that are on this page. If it does not match, do not open it.
mcpb · socseal-mcp.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
ce820630632212d6b266f2b0ae0daeac339de9f2cd57496187e5d0c4c8e188f2
macOS / Linux
echo "ce820630632212d6b266f2b0ae0daeac339de9f2cd57496187e5d0c4c8e188f2 socseal-mcp.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\socseal-mcp.mcpb).Hash -eq "ce820630632212d6b266f2b0ae0daeac339de9f2cd57496187e5d0c4c8e188f2"
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 socseal settlement door MCP server?
socseal settlement door is an MCP server listed in the public MCP registry as xyz.socseal/socseal-mcp. Read-only settlement proof for agents: prove a txid MINED, post-quantum signed. Fail-closed. This page covers its MCPB bundle (https://github.com/Aeliana139/socseal-mcp/releases/download/v1.0.0/socseal-mcp.mcpb).
Is the socseal settlement door MCP server safe to use?
socseal settlement door scores 41 out of 100 on VerifyMCP. 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 socseal settlement door MCP server expose?
socseal settlement door exposes 3 tools: verify_settlement, anchor_receipt, book_status. Their descriptions and schemas cost roughly 268 tokens of context every time the server is loaded.