Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Genome Industrial Intelligence

REMOTE · GENOME-API.CIVOPS.IO · 2 COMPONENTS

Industrial intelligence for AI agents. Conviction scores and diligence for 10,000+ industrials.

67 Trust /100

Last scanned (14 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security71
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1390 tokens (~77/item across 18 items; 18 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 66% of tool parameters carry a description.Partial
  • Structured output schemas are declared (50% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 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.

  • 17 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 16 Nov 26 65

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://genome-api.civops.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=civops.io CN=YE2,O=Let's Encrypt,C=US 21 Nov 2026 19 Feb 2027 ECDSA 256 ECDSA-SHA384 5ccea4fff4207454603d468a4dda7a80d57
SANs: *.civops.io, civops.io
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of genome-api.civops.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
civops.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

Protected resource metadata

Retrieved No
Problem No resource metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://genome-api.civops.io/mcp Verified 200
http (plaintext) http://genome-api.civops.io/mcp Inconclusive 405
MCP tools · 18 exposed · ~1,390 tokens

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 →

Tool Tokens
ask_genome ~83

Ask a natural-language question answered from live Genome data, e.g. 'Which of these companies are most likely to report a sharp earnings drop next quarter?' or 'Which manufacturers just changed CFO?'. Not investment advice.

NameTypeReqDescription
context_tickersarray–Optional list of tickers to include as context
questionstringyesYour question in plain English
NameTypeReqDescription
answerstringyes–
sourcesarray––
tickers_referencedarray––

No examples provided.

get_archetype_candidates ~95

Fingerprint-era view. Descriptive only: the behavioral fingerprint (archetype, trajectory, conviction) was retired as a predictive signal after four out-of-sample tests found no edge. For whether a company is about to get worse, use get_event_risk and get_causal_windows.

NameTypeReqDescription
daysinteger–Lookback window, default 30.
statusstring–Filter by candidate status.

No output schema declared.

No examples provided.

get_architecture_debt ~80

Fingerprint-era view. Descriptive only: the behavioral fingerprint (archetype, trajectory, conviction) was retired as a predictive signal after four out-of-sample tests found no edge. For whether a company is about to get worse, use get_event_risk and get_causal_windows.

NameTypeReqDescription
tickerstringyesTicker symbol.

No output schema declared.

No examples provided.

get_causal_windows ~110

Filing windows: companies whose recent SEC filing (officer change, acquisition, activist stake, material agreement) historically raises the odds of a follow-on event, with the filing, the elevated and matched rates, timing and the help companies in that spot tend to need. Pass ticker for one company, or consequence (executive_change | late_filing | restatement | bankruptcy) for a list.

NameTypeReqDescription
consequencestring––
limitinteger––
tickerstring––

No output schema declared.

No examples provided.

get_diligence ~114

The company report (v2), billed per call on a paid key: a verdict, the graded forecasts, the open filing windows with their SEC filings, leadership on file, the OSHA/EPA/hiring record and questions for management. format='json_compact' drops the evidence chains.

NameTypeReqDescription
formatstring–Output format: 'full' (default) or 'json_compact' for token-efficient agent use
tickerstringyesStock ticker (e.g. HON, CAT, ROK)
NameTypeReqDescription
diligence_questionsarray––
filing_windowsarray––
forecastsobject––
report_versionstringyes–
tickerstringyes–
verdictarrayyes–

No examples provided.

get_ecl ~45

Macro environmental pressure scores for an industry from live FRED data. Descriptive context, not a forecast.

NameTypeReqDescription
industrystring–Optional industry for sector-specific ECL weights
NameTypeReqDescription
regimestringyes–
scoresobjectyes–

No examples provided.

get_event_book ~52

Every scored company ranked for one forecast, riskiest first: head = bankruptcy | earnings_deterioration | credit_deterioration.

NameTypeReqDescription
headstring––
limitinteger––

No output schema declared.

No examples provided.

get_event_ledger ~44

The graded record of every forecast: Brier score, AUC and reliability by decile, live and retrospective. Cite it when stating how much to trust a forecast.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_event_risk ~77

Graded forecasts for a company: the chance of a sharp earnings drop in 90 days (calibrated, with the factors that move it), and its bankruptcy and credit-stress percentile ranks. Read score_kind and calibrated before treating a number as a probability; graded on get_event_ledger.

NameTypeReqDescription
tickerstringyes–

No output schema declared.

No examples provided.

get_event_window ~43

The open event window for a ticker — which events are still in play and how much of the expected response period remains.

NameTypeReqDescription
tickerstringyesTicker symbol.

No output schema declared.

No examples provided.

get_horizons ~78

Fingerprint-era view. Descriptive only: the behavioral fingerprint (archetype, trajectory, conviction) was retired as a predictive signal after four out-of-sample tests found no edge. For whether a company is about to get worse, use get_event_risk and get_causal_windows.

NameTypeReqDescription
tickerstringyesStock ticker
NameTypeReqDescription
divergencestring––
horizonsobjectyes–
tickerstringyes–

No examples provided.

get_pfsl ~56

Pre-financial readings from SEC EDGAR filings (operational stress, demand velocity, capex intensity). Descriptive, not a forecast.

NameTypeReqDescription
industrystring–Optional industry hint
tickerstringyesStock ticker
NameTypeReqDescription
capex_intensitynumber––
compositenumber––
demand_velocitynumber––
labor_talentnumber––
narrative_shiftnumber––
operational_stressnumber––
tickerstringyes–

No examples provided.

get_regime ~68

Fingerprint-era view. Descriptive only: the behavioral fingerprint (archetype, trajectory, conviction) was retired as a predictive signal after four out-of-sample tests found no edge. For whether a company is about to get worse, use get_event_risk and get_causal_windows.

Input schema present but exposes no named parameters.

NameTypeReqDescription
descriptionstring––
key_driversarray––
regimestringyes–
roc_multipliernumber––

No examples provided.

get_screener ~157

Fingerprint-era view. Descriptive only: the behavioral fingerprint (archetype, trajectory, conviction) was retired as a predictive signal after four out-of-sample tests found no edge. For whether a company is about to get worse, use get_event_risk and get_causal_windows.

NameTypeReqDescription
archetypestring–Filter by archetype: constrained, oscillatory, fragile, resilient, saturated, decoupled
limitinteger–Max results (default 20)
min_convictionnumber–Minimum conviction threshold (default 0.25)
signalstring–Filter by signal: STRONG_BUY, BUY, WATCH, NEUTRAL, SELL, STRONG_SELL
NameTypeReqDescription
countinteger––
regimestring––
signalsarrayyes–

No examples provided.

get_shock_backtest ~59

How each archetype has historically responded to a class of shock: sample size, mean response, hit rate. This is the archetype x shock event study.

NameTypeReqDescription
archetypestring––
event_typestring––

No output schema declared.

No examples provided.

get_shocks ~80

Recent detected shocks — the external events the model saw land, by date, ticker, type, and magnitude.

NameTypeReqDescription
daysinteger–Lookback window, default 30.
event_typestring––
limitinteger–Max rows, default 25.
signaturestring––
tickerstring––

No output schema declared.

No examples provided.

get_signal ~107

Fingerprint-era view. Descriptive only: the behavioral fingerprint (archetype, trajectory, conviction) was retired as a predictive signal after four out-of-sample tests found no edge. For whether a company is about to get worse, use get_event_risk and get_causal_windows.

NameTypeReqDescription
industrystring–Optional industry hint (e.g. hvac, auto, aerospace_defense)
tickerstringyesStock ticker (e.g. HON, CAT, GE)
NameTypeReqDescription
archetypestring––
convictionnumberyesConviction score from -1.0 to +1.0
eclobject–External Constraint Layer macro scores
options_structurestring––
signalstringyes–
tickerstringyes–
trajectorystring––

No examples provided.

get_supply_chain ~42

Get upstream supply chain risk for a ticker — which upstream industries are stressed and how much that drags the conviction score.

NameTypeReqDescription
tickerstringyesStock ticker
NameTypeReqDescription
signalsarray––
stressed_inputsarray––
supply_chain_dragnumber––
tickerstringyes–

No examples provided.

Install

How do I install the Genome Industrial Intelligence MCP server?

Genome Industrial Intelligence is a hosted endpoint at https://genome-api.civops.io/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 · genome-api.civops.io

# add to Claude Code
claude mcp add --transport http rdcahalane-genome-industrial-intelligence 'https://genome-api.civops.io/mcp'
Common questions

What is the Genome Industrial Intelligence MCP server?

Genome Industrial Intelligence is an MCP server listed in the public MCP registry as io.github.rdcahalane/genome-industrial-intelligence. Industrial intelligence for AI agents. Conviction scores and diligence for 10,000+ industrials. This page covers its hosted endpoint (https://genome-api.civops.io/mcp).

Is the Genome Industrial Intelligence MCP server safe to use?

Genome Industrial Intelligence scores 67 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 Genome Industrial Intelligence MCP server expose?

Genome Industrial Intelligence exposes 18 tools: get_event_risk, get_event_book, get_event_ledger, get_causal_windows, get_architecture_debt, and 13 more. Their descriptions and schemas cost roughly 1,390 tokens of context every time the server is loaded.

Does the Genome Industrial Intelligence MCP server require authentication?

Yes. Genome Industrial Intelligence asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Genome Industrial Intelligence MCP server still maintained?

Genome Industrial Intelligence is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Genome Industrial Intelligence MCP server?

VerifyMCP ran 12 checks on Genome Industrial Intelligence, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Genome Industrial Intelligence: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.