io.github.stillmarcus24/stillos-notary-mcp
NPM · STILLOS-NOTARY-MCP · 2 COMPONENTS · SCANNED AUG 3
Ed25519-signed verdicts resolved against real ground truth. Free claim/verify; paid bonded dispute.
Available components
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 →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- 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 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 608 tokens (~121/item across 5 items; 5 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 Management23
- Stability observed for 7 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
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · stillos-notary-mcp
claude mcp add stillmarcus24-stillos-notary-mcp -- npx -y stillos-notary-mcp
codex mcp add stillmarcus24-stillos-notary-mcp -- npx -y stillos-notary-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"stillmarcus24-stillos-notary-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"stillos-notary-mcp"
],
"enabled": true
}
}
} openclaw mcp add stillmarcus24-stillos-notary-mcp --command npx --arg -y --arg stillos-notary-mcp
mcp_servers:
stillmarcus24-stillos-notary-mcp:
command: "npx"
args: ["-y", "stillos-notary-mcp"] {
"mcpServers": {
"stillmarcus24-stillos-notary-mcp": {
"command": "npx",
"args": [
"-y",
"stillos-notary-mcp"
]
}
}
} 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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +22
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −48
- Malware scan: pass → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Package version: 1.0.0 → 1.2.0 functional
- 27 Jul 26 +30
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: fair functional
- First check of Tool coverage: 100 functional
- 26 Jul 26 47
First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 0 packages
0 packages in the resolved dependency tree.
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.
claim_verdict ~143
Submits a claim and returns a signed verdict: settled against real external ground truth (GitHub PR, on-chain tx, HTTP status, JSON field, Kalshi market, or multi-exchange price consensus), Ed25519-signed, hash-chained. Free tier — no account, no card. Returns CONFIRMED, REFUTED, or ERROR — never a forced guess.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | who is asking (shown on the public reputation ledger) |
| claim | string | yes | the claim in plain language, e.g. "PR #42 on owner/repo is merged" |
| resolver | object | yes | which external source resolves this claim |
No output schema declared.
No examples provided.
distress_score ~133
Validated corporate distress-foresight score for a single equity ticker: Altman Z-score computed from live SEC XBRL filings, backtested 71% sensitivity / 100% specificity with a ~109-day median lead time, Ed25519-signed. Paid: $0.15 USDC (Base) via x402 — no free tier. A call without an attached x402 payment returns the payment requirement, not a verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | who is asking (shown on the public reputation ledger) |
| ticker | string | yes | equity ticker to score, e.g. "AAPL" |
No output schema declared.
No examples provided.
file_dispute ~154
Files a bonded dispute against a verdict receipt: the disputed verdict is re-resolved immediately against the identical resolver specification that produced it — independent re-run, not a re-vote. An upheld dispute overturns the verdict and queues a slashable payout against the notary's on-chain correctness bond. Paid: $1.00 USDC (Base) via x402 — no free tier. A call without an attached x402 payment returns the payment requirement (price, payTo, asset), not a verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | who is filing the dispute (shown on the public reputation ledger) |
| receipt_hash | string | yes | the receipt_hash of the verdict being disputed — must be under 48 hours old |
No output schema declared.
No examples provided.
screen_entity ~116
OFAC SDN sanctions name screen: matches a legal name against the OFAC Specially Designated Nationals list, with a source_as_of freshness timestamp, Ed25519-signed. Paid: $0.001 USDC (Base) via x402 — no free tier. A call without an attached x402 payment returns the payment requirement, not a verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | who is asking (shown on the public reputation ledger) |
| entity | string | yes | legal name to screen against the OFAC SDN list |
No output schema declared.
No examples provided.
verify_receipt ~62
Independently verifies any StillOS notary receipt by its hash: confirms the hash chain is intact and the Ed25519 signature is valid. Read-only, free, no auth.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | the receipt_hash returned by claim_verdict or commit |
No output schema declared.
No examples provided.