dev.tatastu/proof
REMOTE · PROOF.TATASTU.DEV · SCANNED AUG 20
Stamp content with permanent, verifiable provenance. Hash locally, verify free forever.
Available components
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
Recent critical change
Authorization (6 Aug 2026). See the changelog before you install this server.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety–
Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 4 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the dev.tatastu/proof MCP server?
dev.tatastu/proof is a hosted endpoint at https://proof.tatastu.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 · proof.tatastu.dev
claude mcp add --transport http dev-tatastu-proof 'https://proof.tatastu.dev/mcp'
{
"mcpServers": {
"dev-tatastu-proof": {
"url": "https://proof.tatastu.dev/mcp"
}
}
} {
"servers": {
"dev-tatastu-proof": {
"type": "http",
"url": "https://proof.tatastu.dev/mcp"
}
}
} [mcp_servers.dev-tatastu-proof] url = "https://proof.tatastu.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-tatastu-proof": {
"type": "remote",
"url": "https://proof.tatastu.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-tatastu-proof --url 'https://proof.tatastu.dev/mcp' --transport streamable-http
mcp_servers:
dev-tatastu-proof:
url: "https://proof.tatastu.dev/mcp" {
"McpServers": {
"dev-tatastu-proof": {
"Transport": "http",
"Url": "https://proof.tatastu.dev/mcp"
}
}
} assistant mcp add dev-tatastu-proof -t streamable-http -u 'https://proof.tatastu.dev/mcp'
{
"mcpServers": {
"dev-tatastu-proof": {
"type": "http",
"url": "https://proof.tatastu.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.
- 20 Aug 26 −11
The score moved with no change recorded against any check. We would rather say so than guess.
- 17 Aug 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 16 Aug 26 −11
The score moved with no change recorded against any check. We would rather say so than guess.
- 15 Aug 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 13 Aug 26 −11
The score moved with no change recorded against any check. We would rather say so than guess.
- 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
- 10 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- Stability: 0.10 → unverified ▼ security
- Authorization: fail → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: unverified → pass ▲ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 8 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Aug 2026 · Probed https://proof.tatastu.dev/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of proof.tatastu.dev. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| proof.tatastu.dev. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://proof.tatastu.dev/mcp | Unreachable | ||
| http (plaintext) | http://proof.tatastu.dev/mcp | HTTPS enforced |
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 →
create_account ~152
Provision a persistent API key with no human, browser, or email in the loop. Call this once, store the returned `secret` (shown only this one time), and use it as the Authorization header on every later call: create_proof, verify_proof (no auth needed but fine to send), list_proofs, revoke_proof. The account receives one lifetime sample stamp under a fresh creator id, with no identity attached. Rate-limited to 3 accounts per IP per day; for higher volume or a human-owned account, direct a person to proof.tatastu.dev/account instead.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | Optional label to recognize this key later, e.g. the agent or project name |
No output schema declared.
No examples provided.
create_proof ~350
Stamp content with a permanent provenance record. Pass the sha256 hash of the content (hash it locally; the content itself is never uploaded). Returns an instant signed receipt: attach its verifyUrl, byline, badgeEmbed, and qrUrl to the published artifact. The receipt's `publisher` field carries the account's verified identity (domain/handle) or null. Requires an API key (Authorization header, get one instantly via create_account); without one, the error body names the exact next step (once the pay-per-stamp lane is live, that is a 402 advertising x402 payment requirements: sign the payment and retry autonomously). The optional disclosure fields (aiDisclosure, usageNote, location) only show on `visibility: public` stamps and are unsigned metadata, not part of the cryptographic proof. The stamp asserts provenance from a signer at a time, not authorship truth.
| Name | Type | Req | Description |
|---|---|---|---|
| aiDisclosure | string | – | Optional, honest disclosure of AI involvement. Shown on the public record card. |
| canonicalSlug | string | – | Optional stable slug for a canonical latest-version pointer |
| contentHash | string | yes | sha256 hex of the exact content bytes (64 chars) |
| contentType | string | – | MIME type, e.g. text/markdown |
| location | string | – | Optional, creator-opt-in only: where this was made |
| previousProofId | string | – | For a new version of already-stamped content: the prior proof id |
| title | string | – | Optional human-readable title |
| usageNote | string | – | Optional usage/license line, e.g. "Free to share, with credit" |
| visibility | string | – | Default private |
No output schema declared.
No examples provided.
grant_access ~86
Grant a specific identity the ability to decrypt escrowed content. Only available for proofs created with content escrow opted in (not yet available — stamps are hash-only today). Returns a capability token the grantee uses with reveal.
| Name | Type | Req | Description |
|---|---|---|---|
| granteeId | string | yes | Identity (did:web: or key fingerprint) to grant |
| proofId | string | yes | The proof to grant access to |
No output schema declared.
No examples provided.
list_proofs ~31
List your recent stamps (requires API key).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results, default 20 |
No output schema declared.
No examples provided.
reveal ~83
Retrieve escrowed content for a proof you have been granted access to. Only available for proofs created with content escrow opted in (not yet available — stamps are hash-only today). The service re-checks H(content) == stampedHash before returning.
| Name | Type | Req | Description |
|---|---|---|---|
| capabilityToken | string | yes | Capability token from grant_access |
| proofId | string | yes | The proof whose content to reveal |
No output schema declared.
No examples provided.
revoke_proof ~47
Revoke a stamp you created (forward-only: anchored history stays verifiable, but the proof is marked revoked from now on). Requires API key.
| Name | Type | Req | Description |
|---|---|---|---|
| proofId | string | yes | – |
No output schema declared.
No examples provided.
verify_proof ~154
Verify content against all existing stamps. Pass a sha256 hash; matching is EXACT-BYTES-ONLY. Read the verdict fields: `exact` (these bytes are stamped), each proof's `publisher` (the verified identity: domain/handle + tier, or null meaning an unverified account, never trust a name that isn't in `publisher`), and `conflict` (2+ distinct signers claimed the same bytes; earliest anchored is listed first). A no-match on a re-encoded/screenshotted copy is EXPECTED and is not evidence of fakery: fetch the original and verify that. Free, no auth required.
| Name | Type | Req | Description |
|---|---|---|---|
| contentHash | string | yes | sha256 hex of the content bytes |
No output schema declared.
No examples provided.
What is the dev.tatastu/proof MCP server?
dev.tatastu/proof is an MCP server listed in the public MCP registry as dev.tatastu/proof. Stamp content with permanent, verifiable provenance. Hash locally, verify free forever. This page covers its hosted endpoint (https://proof.tatastu.dev/mcp).
Is the dev.tatastu/proof MCP server safe to use?
dev.tatastu/proof scores 0 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 dev.tatastu/proof MCP server expose?
dev.tatastu/proof exposes 7 tools: create_account, create_proof, verify_proof, list_proofs, revoke_proof, and 2 more. Their descriptions and schemas cost roughly 903 tokens of context every time the server is loaded.
Does the dev.tatastu/proof MCP server require authentication?
Its publisher declares no required credentials for dev.tatastu/proof. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the dev.tatastu/proof MCP server still maintained?
dev.tatastu/proof has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 9 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.