# socseal settlement door (mcpb · socseal-mcp.mcpb)

Read-only settlement proof for agents: prove a txid MINED, post-quantum signed. Fail-closed.

- Trust score: 41/100 (low)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- mcpb · `socseal-mcp.mcpb`: 41/100 (this document), [markdown](https://verifymcp.io/servers/xyz-socseal-socseal-mcp/socseal-mcp.md), [page](https://verifymcp.io/servers/xyz-socseal-socseal-mcp/socseal-mcp)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/Aeliana139/socseal-mcp/releases/download/v1.0.0/socseal-mcp.mcpb`
- Transport: `stdio`
- SHA-256: `ce820630632212d6b266f2b0ae0daeac339de9f2cd57496187e5d0c4c8e188f2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Supply Chain Security**: 0/100
  - 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.
  - 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).
  - Install-script risk not yet assessed.
  - 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).
- **Provenance & Transparency**: 6/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 14 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 82/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 268 tokens (~89/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### 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.

- Download bundle: `https://github.com/Aeliana139/socseal-mcp/releases/download/v1.0.0/socseal-mcp.mcpb`
- SHA-256: `ce820630632212d6b266f2b0ae0daeac339de9f2cd57496187e5d0c4c8e188f2`

### Verify on macOS / Linux

```bash
echo "ce820630632212d6b266f2b0ae0daeac339de9f2cd57496187e5d0c4c8e188f2  socseal-mcp.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\socseal-mcp.mcpb).Hash -eq "ce820630632212d6b266f2b0ae0daeac339de9f2cd57496187e5d0c4c8e188f2"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 41, +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.

### 2026-10-14 (score 40, +6)

- [functional improvement] Stability: unverified → 0.40

### 2026-10-02 (score 34)

First indexed and scored.

## MCP tools (3)

### `verify_settlement` (~97 tokens)

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.

Input parameters:

- `txid` (string, required): 64-hex transaction id

### `anchor_receipt` (~94 tokens)

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.

Input parameters:

- `txid` (string, required): 64-hex transaction id (e.g. a book anchor txid)

### `book_status` (~77 tokens)

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.

Input parameters:

- `day` (integer): book day number (1 = first day)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/xyz-socseal-socseal-mcp/socseal-mcp#diagnostics

## Score history

- 2026-10-17: 41
- 2026-10-16: 41
- 2026-10-15: 40
- 2026-10-14: 40
- 2026-10-13: 34
- 2026-10-12: 34
- 2026-10-10: 34
- 2026-10-07: 34
- 2026-10-04: 34
- 2026-10-03: 34
- 2026-10-02: 34

## Common questions

### 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.

## Links

- Changelog RSS feed: https://verifymcp.io/servers/xyz-socseal-socseal-mcp/socseal-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/xyz-socseal-socseal-mcp/socseal-mcp.json
- HTML version of this page: https://verifymcp.io/servers/xyz-socseal-socseal-mcp/socseal-mcp