io.github.stillmarcus24/stillos-notary-mcp
REMOTE · STILLOS-NOTARY-MCP-EDGE.STILLOS.WORKERS.DEV · 2 COMPONENTS · SCANNED SEP 21
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 against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.stillmarcus24/stillos-notary-mcp server?
io.github.stillmarcus24/stillos-notary-mcp is a hosted endpoint at https://stillos-notary-mcp-edge.stillos.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · stillos-notary-mcp-edge.stillos.workers.dev
claude mcp add --transport http stillmarcus24-stillos-notary-mcp 'https://stillos-notary-mcp-edge.stillos.workers.dev/mcp'
{
"mcpServers": {
"stillmarcus24-stillos-notary-mcp": {
"url": "https://stillos-notary-mcp-edge.stillos.workers.dev/mcp"
}
}
} {
"servers": {
"stillmarcus24-stillos-notary-mcp": {
"type": "http",
"url": "https://stillos-notary-mcp-edge.stillos.workers.dev/mcp"
}
}
} [mcp_servers.stillmarcus24-stillos-notary-mcp] url = "https://stillos-notary-mcp-edge.stillos.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"stillmarcus24-stillos-notary-mcp": {
"type": "remote",
"url": "https://stillos-notary-mcp-edge.stillos.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add stillmarcus24-stillos-notary-mcp --url 'https://stillos-notary-mcp-edge.stillos.workers.dev/mcp' --transport streamable-http
mcp_servers:
stillmarcus24-stillos-notary-mcp:
url: "https://stillos-notary-mcp-edge.stillos.workers.dev/mcp" {
"McpServers": {
"stillmarcus24-stillos-notary-mcp": {
"Transport": "http",
"Url": "https://stillos-notary-mcp-edge.stillos.workers.dev/mcp"
}
}
} assistant mcp add stillmarcus24-stillos-notary-mcp -t streamable-http -u 'https://stillos-notary-mcp-edge.stillos.workers.dev/mcp'
{
"mcpServers": {
"stillmarcus24-stillos-notary-mcp": {
"type": "http",
"url": "https://stillos-notary-mcp-edge.stillos.workers.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 29 Aug 26 0
- Stability: 0.97 → pass security
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- 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 0
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 21 Sept 2026 · Probed https://stillos-notary-mcp-edge.stillos.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=stillos.workers.dev | CN=WE1,O=Google Trust Services,C=US | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 4fc1d98df85279190e79580c2de2484d |
| SANs: stillos.workers.dev, *.stillos.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of stillos-notary-mcp-edge.stillos.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://stillos-notary-mcp-edge.stillos.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://stillos-notary-mcp-edge.stillos.workers.dev/mcp | Inconclusive | 405 |
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 →
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.
What is the io.github.stillmarcus24/stillos-notary-mcp server?
io.github.stillmarcus24/stillos-notary-mcp is listed in the public MCP registry as io.github.stillmarcus24/stillos-notary-mcp. Ed25519-signed verdicts resolved against real ground truth. Free claim/verify; paid bonded dispute. This page covers its hosted endpoint (https://stillos-notary-mcp-edge.stillos.workers.dev/mcp).
Is the io.github.stillmarcus24/stillos-notary-mcp server safe to use?
io.github.stillmarcus24/stillos-notary-mcp scores 74 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 io.github.stillmarcus24/stillos-notary-mcp server expose?
io.github.stillmarcus24/stillos-notary-mcp exposes 5 tools: claim_verdict, verify_receipt, file_dispute, screen_entity, distress_score. Their descriptions and schemas cost roughly 608 tokens of context every time the server is loaded.
Does the io.github.stillmarcus24/stillos-notary-mcp server require authentication?
No. We connected to io.github.stillmarcus24/stillos-notary-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.stillmarcus24/stillos-notary-mcp server still maintained?
io.github.stillmarcus24/stillos-notary-mcp is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.