OT Intel API

Submit OT Sighting

submitSighting

Submit an anonymized IOC/TTP sighting observed in the caller's own OT environment. Feeds the correlation corpus without storing an org identifier. Written to a separate sightings store, not intel.db. Price: $0.05 USDC per call via x402 on Base mainnet. An unpaid call returns an x402 PaymentRequired challenge; retry the identical call with the signed payload in _meta["x402/payment"].

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ioc_or_ttp_id": "<ioc_or_ttp_id>",
      "sector": "<sector>",
      "region": "<region>"
    },
    "name": "submitSighting"
  }
}

Input Schema

Name	Required	Description
`region`	Yes	Region where this was observed e.g. KSA, UAE
`sector`	Yes	Sector where this was observed e.g. energy, water
`actor_name`	No	Optional actor name if the sighting is attributed
`observed_at`	No	Optional ISO 8601 timestamp of observation
`ioc_or_ttp_id`	Yes	CVE ID, MITRE ATT&CK-for-ICS technique ID, or sha256 hash

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A4.5/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds substantial behavior beyond what readOnlyHint=false and openWorldHint=true convey: anonymization (no org identifier stored), the destination store ('not intel.db'), a per-call price, and the full x402 failure/retry protocol including the _meta['x402/payment'] payload location. This is exactly the kind of non-obvious operational detail annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads purpose, then anonymity/storage behavior, then the cost and retry protocol. Four sentences, each adding distinct actionable information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no output schema, it covers the write target, the privacy guarantee, the cost, and the payment round-trip including the retry requirement. Nothing an agent needs to invoke it successfully is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all five parameters are already documented in the schema, and the description adds no parameter-level syntax or format detail beyond what is there. Baseline 3 applies when the schema carries the semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Submit an anonymized IOC/TTP sighting'), scopes it to the caller's own OT environment, and distinguishes itself from the entirely read-oriented get* sibling set. An agent can tell this is the sole write/contribution path without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear context on when to use it (sightings the caller directly observed in their own OT environment, to feed the correlation corpus) and a concrete operating procedure for the payment flow. It does not name explicit exclusions or alternatives, but no sibling competes with it since all are read tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All OT Intel API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?