# io.factorguide/factorguide (remote · factorguide.io)

Send a coupling matrix, get zone classifications and optimal factorization strategy.

- Trust score: 58/100 (low)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `factorguide.io`: 58/100 (this document), [markdown](https://verifymcp.io/servers/io-factorguide-factorguide/factorguide.md), [page](https://verifymcp.io/servers/io-factorguide-factorguide/factorguide)

## Channel facts

- Endpoint: `https://factorguide.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 43/100
  - AI-judged instruction clarity (poor).
  - Tool/resource definitions use about 773 tokens (~110/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 72/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 17% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http io-factorguide-factorguide https://factorguide.io/mcp
```

### Codex

```toml
[mcp_servers.io-factorguide-factorguide]
url = "https://factorguide.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-factorguide-factorguide": {
      "type": "remote",
      "url": "https://factorguide.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-factorguide-factorguide --url https://factorguide.io/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-factorguide-factorguide:
    url: "https://factorguide.io/mcp"
```

### Other

```json
{
  "mcpServers": {
    "io-factorguide-factorguide": {
      "type": "http",
      "url": "https://factorguide.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 58, +1)

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

### 2026-08-01 (score 57, +1)

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

### 2026-07-31 (score 56, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 53, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 53, +1)

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

### 2026-07-28 (score 52, +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.

### 2026-07-27 (score 51, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 51)

First indexed and scored.

## MCP tools (7)

### `factorguide_navigate` (~218 tokens)

Map the factorization terrain of your model. Send coupling structure (precision matrix preferred for n>2; covariance matrix recommended if sign or CC information is needed) and receive a block-diagonal strategy with calibrated risk prediction. Answers: 'How should I factorize, and what will it cost me?' Optional: set report_sign_detectability=true to get sign(ρ) for high-leverage pairs at no additional cost when variance ratio > 20. Requires X-Wallet header with your EVM wallet address (0x...). First 5 queries are free trial.

Input parameters:

- `accuracy_target` (number)
- `compute_budget`
- `cost_model`
- `coupling` (required)
- `distribution_diagnostics`
- `encoding_label`
- `model_class`
- `report_marginal_ic` (boolean)
- `report_sign_detectability` (boolean)
- `sample_size` (integer, required)
- `synergy_check` (boolean)
- `task_type`
- `variable_names`

### `factorguide_diagnose` (~115 tokens)

Quick single-pair diagnostic. IC with risk prediction for both model classes. Include variances for sign detectability. Requires X-Wallet header with your EVM wallet address (0x...). First 5 queries are free trial.

Input parameters:

- `coupling_value` (number, required): IC or coupling value
- `i` (string, required): First variable name
- `j` (string, required): Second variable name
- `sample_size` (integer, required)
- `variance_i` (number)
- `variance_j` (number)

### `factorguide_submit_payment` (~91 tokens)

Submit payment proof after sending stablecoins to a FactorGuide wallet address. For x402: provide tx_hash and chain. For MPP: use in-band Authorization header instead — no separate submission needed.

Input parameters:

- `chain` (string, required): Chain identifier, e.g. 'eip155:8453' or 'tempo:4217'
- `tx_hash` (string, required): On-chain transaction hash

### `factorguide_report_outcome` (~119 tokens)

Complete the prediction loop — report inference diagnostics so future predictions improve. After running the approach FactorGuide recommended, return your ESS ratio, PSIS-khat, or log-likelihood gap. Zero additional computation required. Does not consume a query allocation.

Input parameters:

- `actual_mse_ratio`
- `approach_taken` (required)
- `ess_ratio`
- `log_lik_gap`
- `n_replications`
- `prediction_hash` (string, required)
- `psis_khat`
- `runtime_seconds`

### `factorguide_explain` (~97 tokens)

Plain-language explanation of a previous navigate response, including wave mechanics grounding for observational cost guidance. Requires a prediction_hash from a prior factorguide_navigate call. Consumes 1 query allocation. Available for starter and professional tiers. Requires X-Wallet header with your EVM wallet address (0x...). First 5 queries are free trial.

Input parameters:

- `prediction_hash` (string, required): prediction_hash from a previous navigate response

### `factorguide_regime_detect` (~34 tokens)

Detect coupling regime changes in time series via windowed IC. Specification pending — v1.1 target.

### `factorguide_synergy_detect` (~99 tokens)

Detect hidden synergistic structure via Walsh-Hadamard spectral analysis. Accepts pre-computed Walsh coefficients — agent performs the transform locally and sends only the spectral summary. Specification pending — v1.1 target.

Input parameters:

- `ic_matrix_ref` (string)
- `n_samples` (integer|null)
- `n_variables` (integer)
- `transform_method` (string)
- `walsh_coefficients` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-factorguide-factorguide/factorguide#diagnostics

## Score history

- 2026-08-03: 58
- 2026-08-02: 57
- 2026-08-01: 57
- 2026-07-31: 56
- 2026-07-30: 53
- 2026-07-29: 53
- 2026-07-28: 52
- 2026-07-27: 51
- 2026-07-26: 51

## Links

- Remote endpoint: https://factorguide.io/mcp
- Repository: https://github.com/Bwana7/factorguide
- Changelog RSS feed: https://verifymcp.io/servers/io-factorguide-factorguide/factorguide/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-factorguide-factorguide/factorguide/changelog.json
- HTML version of this page: https://verifymcp.io/servers/io-factorguide-factorguide/factorguide