OzarkSecurity Labs

Glimmer.

Threat intelligence
for MCP and x402.

Our first product is a commercial threat-intelligence publisher. Glimmer owns the Decoys; customers receive corroborated Indicators through signed Feeds and lookup APIs.

See what you get

Pre-launch. Public access pending clearance.

Corroboration, made visible.

Glimmer's evidence-correlation modelIllustrative example, not a captured incident. Observations at two separate Glimmer Decoys share a TLS fingerprint. Corroborated observations form an Anonymous Cluster, never a named actor.Observation AMCP DecoyObservation Bx402 DecoyShared TLSfingerprintAnonymousClustercorroborate

Publication requires at least two independent observations by default. Correlation groups observations; it does not establish a named identity.

Illustrative example Not a captured incident

What you
get.

Shared threat intelligence from Glimmer-owned collection.

Glimmer is a commercial threat-intelligence publisher. The customer object is an Indicator, not a log line. Public access is not yet available.

Signed Feeds
A Snapshot of current Indicators and Anonymous Clusters, plus cursor Deltas.
Lookup APIs
For Organizations, and a public x402-paid Lookup Tier for autonomous agents.
First published objects
After corroboration: IP, TLS fingerprint, and wallet.

Each Indicator carries verdict, confidence, reason codes, and a provenance-safe Evidence Summary. It does not carry precise observation times, Decoy IDs, discovery locations, or Raw Telemetry.

What Glimmer does—and does not—collect
  • Not a customer-side MCP wrap or reverse-proxy on someone else's host.
  • Not an investigation workspace.
  • Not a customer-telemetry ingest.
  • Not named attribution. Related observations publish as an Anonymous Cluster.
  • Not a claim that a Decoy settled a payment. The x402 Decoy simulates validation and never moves value.

Glimmer is not what remains of a customer's interaction. It is a shared intelligence corpus collected from our Decoys and sold without exposing how we saw it.

Shared intelligence.
Traceable delivery.

The confirmed MVP delivery model provides common intelligence through signed Feeds—Snapshot and cursor-based Delta—and lookup APIs. Organizations receive Indicators and Anonymous Clusters, not Raw Telemetry or a customer investigation workspace.

A public, x402-paid Lookup Tier is designed to extend access to autonomous agents directly, alongside self-serve Organization accounts.

Not yet publicly available. Public Decoy deployment and customer Feeds remain pending legal and hosting-provider clearance.

Five paths.
One evidence standard.

What triggers an observation, what is captured, and how it connects.

Every derived result retains its processor, rule-set, and model version, anchored to an immutable event identifier. Two paths are design targets and are labeled Planned.

Implemented describes engineering status, not a publicly deployed Decoy. Where we are today.

Decoy → Raw Telemetry → normalization → deterministic rules → candidate observables → correlation and session grouping → corroboration → versioned Indicator or Anonymous Cluster.

MCP protocol probing and misuse

Implemented
Trigger
Invalid methods, malformed or oversized requests, calls against synthetic MCP tools.
Captured evidence
Protocol/transport metadata per exchange, timestamped, tied to the originating Decoy.
Correlation & outcome
Joined by source and timing proximity; repeated patterns across Decoys become a behavior pattern or Anonymous Cluster.

MCP tool-poisoning / prompt-injection probes

Planned
Trigger
A tool call or discovery interaction matches a known injection/poisoning pattern.
Captured evidence
Would match normalized content against a versioned rule set — matched-rule reference and confidence only, never the raw payload.
Correlation & outcome
Would correlate matching patterns across Decoys to identify campaigns that adapt over time.

x402 malformed-payment and protocol abuse

Implemented
Trigger
Missing header prompts a challenge; malformed or synthetically-rejected header captured as an attempt.
Captured evidence
Transport/protocol metadata per attempt, plus a cryptographic fingerprint of the payment artifact.
Correlation & outcome
Matching fingerprint flags replay across sources and time — distinguishes a one-off client from scanning infrastructure.

Payment identity and wallet correlation

Planned
Trigger
Would derive a candidate wallet from structurally valid, cryptographically verifiable payment material.
Captured evidence
Candidate wallet identifier, same provenance and confidence model as any observable. Credentials or private material never enter Indicators.
Correlation & outcome
High-value link across observations — a narrowly allowed cryptographically-gated exception to the two-observation corroboration threshold.

Shared infrastructure and campaign correlation

Implementedat the graph layer
Trigger
Any suspicious event repeats an observable already seen elsewhere.
Captured evidence
Network- and protocol-level fingerprints observed across Decoys, timestamped and linked by session.
Correlation & outcome
Linked in a relationship graph, clustered only as an Anonymous Cluster — never named attribution from one shared signal.

Words with
specific meaning.

Precise language keeps observation, inference, and uncertainty distinct. These are the terms behind Glimmer’s intelligence.

Decoy
A controlled synthetic MCP or x402 endpoint used to observe hostile interaction without executing attacker input or moving value.
Raw Telemetry
The unmodified, immutable event record captured from a Decoy before normalization.
Indicator
A customer-visible, versioned intelligence assertion about an observable — a wallet, TLS fingerprint, IP, domain, or fingerprint.
Anonymous Cluster
A provisional grouping of related observations that does not assert a named real-world actor.
Evidence Summary
A provenance-safe explanation of an Indicator, safe to disclose without revealing collection sources or exact observation details.
Feed
The signed channel (Snapshot plus cursor-based Delta) through which corroborated Indicators and Anonymous Clusters reach customers.
Snapshot
A full-state Feed delivery: the complete current set of published Indicators and Anonymous Clusters.
Delta
A cursor-based incremental Feed update, published between Snapshots.
Entitlement
What a given Organization is authorized to access, tied to its usage.
Public Lookup Tier
An x402-paid lookup API open to autonomous agents directly, alongside self-serve Organization accounts.
Organization
A customer account on Glimmer, created by self-serve signup.

Let’s examine
what comes next.

Questions, partnership inquiries, or a conversation about machine-actor security.

Get in touch