A2 — the cross-lens join. Fuse TunnelMind's two lenses (Scry attacker
intelligence + Sigil supply graph) into ONE verdict on a single node key.
This is the moat: no siloed competitor owns both halves of the graph, so
the fused `cross_lens` block carries information neither lens can supply
alone.
Us
sigil_verify_supply_path
The core pre-bid check. Verify the trustworthiness of one programmatic ad
supply path and get back a composite trust verdict plus a signed proof token.
Sigil composes ads.txt authorization, datacenter-IP classification, Scry
fraud-corpus lookup, and app-bundle checks into one score.
Use this tool w
sigil_verify_ads_txt
Check whether an exchange/SSP is authorized to sell a publisher's inventory,
per the publisher's ads.txt file. Fast cached lookup against Sigil's daily
crawl of the top ~10k publisher domains.
Use this tool when:
- You need a single, narrow authorization check (not a full supply-path score).
- You
sigil_verify_ip_type
Classify an IPv4 address as datacenter, residential, mobile, or unknown.
Detects datacenter traffic posing as real user devices. Stateless — the IP
is never logged or stored.
Use this tool when:
- You need to know whether bid-request traffic originates from a datacenter.
Inputs:
- `ip` (required):
sigil_verify_app_bundle
Verify that a mobile/CTV app bundle ID actually exists in its app store and,
optionally, that the listed developer matches. Detects bundle-ID spoofing in
bid requests.
Use this tool when:
- A bid request names an app bundle and you must confirm the app is real.
Inputs:
- `bundle_id` (required), `p
sigil_verify_supply_chain
Verify a full OpenRTB SupplyChain (schain) object — every node, end to end.
Per node Sigil checks the seller against the exchange sellers.json and the
origin ads.txt, then returns a per-node and aggregate verdict plus a signed
token.
Use this tool when:
- A bid request carries an OpenRTB `schain` a
sigil_traverse_supply_chain
Walk the supply graph for a publisher domain and get back the ITEMIZED
sell paths — distinct from sigil_verify_supply_chain (which verifies a
schain you BRING) and from the dark-pool-risk signal (which only returns
counts). Here Sigil reconstructs the paths from its own crawl: every SSP
the publishe
sigil_score_entity
Get the pre-computed trust score for one supply-chain entity (a publisher or
an SSP). Scores are recomputed daily from ads.txt health, supply-chain
directness, reach, and stability — deterministic, no ML black box.
Use this tool when:
- You want a fast standing trust signal for an entity without ru
sigil_score_batch
Pre-computed trust scores for up to 200 entities in one call — built for an
agent evaluating many supply sources during campaign setup.
Use this tool when:
- You have a list of publishers/SSPs to grade at once.
Inputs:
- `entity_ids` (required): array of `{type}:{domain}` ids, up to 200.
- `weight
sigil_atap_register_ait
Register an ATAP v0.1 Agent Identity Token for a media-buying agent. Sigil
validates the capabilities + constraints against the `sigil:media_buyer:v1`
profile, signs the AIT as the witness, and returns it. Do this once per agent
campaign before witnessing any events.
Inputs:
- `profile` (required):
sigil_atap_witness
Witness one agent-reported bid or budget event into an AIT's hash-chained
attestation log. Sigil validates the payload (rejecting any PII), classifies
the evidence tier — `anchored` if a bid cites a valid Sigil token, else
`asserted` — derives constraint violations, and signs the event.
Use this to
sigil_generate_receipt
Generate the ATAP v0.1 compliance Receipt for an AIT — the portable, signed
artifact a media buyer hands its principal. The receipt grades every event
witnessed / anchored / asserted and is verifiable offline with the bundled
verify.sh.
Use this tool when:
- A reporting period closes and you need a
Endpoint
https://mcp.sigil.tunnelmind.ai/mcp Category: Other · Last checked: 2026-08-15T08:51:53Z
Monitor your own MCP server
Get alerted the moment yours goes down, a tool schema drifts, or an upstream silently breaks.
What this means. This server responded to the MCP handshake and listed its tools without authentication. The schema fingerprint lets us flag if tool signatures silently change (schema drift) between checks.