POPCORN MCP
REMOTE · 767-2676.COM · 2 COMPONENTS
Witness layer for agents: signed receipts binding a fingerprint to a witnessed time. $0.001.
Available components
Last scanned (5 hours ago)
Scores higher than 44% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
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 Security49
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (popcorn_time). See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 620 tokens (~88/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage70
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 10% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 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.
- 29 Oct 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.
- 26 Oct 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.
- 25 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 24 Oct 26 57
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 5 Nov 2026 · Probed https://767-2676.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=767-2676.com | CN=WE1,O=Google Trust Services,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | eb28cd349ae6072a130980e83db64565 |
| SANs: 767-2676.com, *.767-2676.com | ||||||
| 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 secure
Validation of 767-2676.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| 767-2676.com. | present | 2371 | 13 | Verified |
| 767-2676.com. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://767-2676.com/mcp | Verified | 200 | |
| http (plaintext) | http://767-2676.com/mcp | Inconclusive | 404 |
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 →
popcorn_catalog ~25
Read the live catalog, offer, and published verification keys. Free; no payment.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
popcorn_hash ~54
Hash public bytes on this remote server. Submitted text reaches the server: hash private work locally instead. Free; no onward request or payment.
| Name | Type | Req | Description |
|---|---|---|---|
| payload_base64url | string | – | – |
| payload_text | string | – | – |
No output schema declared.
No examples provided.
popcorn_sample Verify a real receipt for free ~58
Check the public October 14 TAIN 2.0 receipt and a changed-digest control. No inputs, wallet, payment, or outbound request. Historical evidence, not a fresh clock. Bundled sample keys do not independently establish issuer identity.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
popcorn_time ~128
Request signed current-time evidence. Defaults to a free unpaid 402 challenge. A fresh receipt costs exactly $0.001 USDC on Base. Payment requires owner approval, approve_payment:true, and a caller-signed payment_signature. No server wallet or private key. No automatic retry. Verify evidence and account for client round-trip time before a deadline decision.
| Name | Type | Req | Description |
|---|---|---|---|
| approve_payment | boolean | – | – |
| freshness_ms | integer | – | – |
| payment_signature | string | – | Caller-signed x402 PAYMENT-SIGNATURE. Never send a wallet private key. Requires approve_payment:true for this single call. |
No output schema declared.
No examples provided.
popcorn_verify ~81
Verify a time or witness receipt using caller-trusted JWKS and expected values. Digest-only for witness payloads. No outbound request or payment. Caller keys do not establish issuer identity; a signature grants no authority.
| Name | Type | Req | Description |
|---|---|---|---|
| jwks | object | yes | – |
| receipt_type | string | yes | – |
| response | object | yes | – |
| verification | object | yes | – |
No output schema declared.
No examples provided.
popcorn_verify_v2 ~128
Verify TAIN 2.0 evidence against keys fetched from the fixed POPCORN issuer URL. Caller jwks is replaced with published keys, including predecessors. Send a digest, never private work. Free; does not grant authority, establish current time, or verify settlement on chain.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_node_id | string | – | – |
| expected_nonce | string | yes | – |
| expected_payload_digest | string | yes | – |
| jwks | object | yes | – |
| max_clock_accuracy_radius_ms | integer | – | – |
| previous_receipt | object | – | – |
| response | object | yes | – |
No output schema declared.
No examples provided.
popcorn_witness ~146
Witness a SHA-256 digest and fresh caller nonce at a time. Defaults to a free unpaid 402 challenge. One fresh receipt costs exactly $0.001 USDC on Base; requires owner approval, approve_payment:true, and caller-signed payment_signature. Keep work and wallet keys local. No automatic retry. Evidence does not authorize or prove execution of an action.
| Name | Type | Req | Description |
|---|---|---|---|
| approve_payment | boolean | – | – |
| digest | string | yes | – |
| nonce | string | yes | – |
| payment_signature | string | – | Caller-signed x402 PAYMENT-SIGNATURE. Never send a wallet private key. Requires approve_payment:true for this single call. |
| previous_attestation_digest | – | – | – |
No output schema declared.
No examples provided.
How do I install the POPCORN MCP server?
POPCORN MCP is a hosted endpoint at https://767-2676.com/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 · 767-2676.com
claude mcp add --transport http violetclaire-popcorn-mcp 'https://767-2676.com/mcp'
What is the POPCORN MCP server?
POPCORN MCP is listed in the public MCP registry as io.github.violetclaire/popcorn-mcp. Witness layer for agents: signed receipts binding a fingerprint to a witnessed time. $0.001. This page covers its hosted endpoint (https://767-2676.com/mcp).
Is the POPCORN MCP server safe to use?
POPCORN MCP scores 62 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 POPCORN MCP server expose?
POPCORN MCP exposes 7 tools: popcorn_sample, popcorn_catalog, popcorn_hash, popcorn_verify, popcorn_verify_v2, and 2 more. Their descriptions and schemas cost roughly 620 tokens of context every time the server is loaded.
Does the POPCORN MCP server require authentication?
No. We connected to POPCORN MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the POPCORN MCP server still maintained?
POPCORN MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.