mcp server
factorguide
Send a coupling matrix, get zone classifications and optimal factorization strategy.
Description as published by the maintainer. Source
- version 1.2.1
- slowing
slowing — Most recent push to the repository was 2026-04-09.
What this server can do
7 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
factorguide_diagnose(i, j, variance_i, variance_j, sample_size, coupling_value)- 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. Required: i, j, coupling_value, sample_size.
factorguide_explain(prediction_hash)- 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. Required: prediction_hash.
factorguide_navigate(coupling, task_type, cost_model, model_class, sample_size, synergy_check, compute_budget, encoding_label, variable_names, accuracy_target, report_marginal_ic, distribution_diagnostics, report_sign_detectability)- 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. Required: coupling, sample_size.
factorguide_regime_detect- Detect coupling regime changes in time series via windowed IC. Specification pending — v1.1 target.
factorguide_report_outcome(ess_ratio, psis_khat, log_lik_gap, approach_taken, n_replications, prediction_hash, runtime_seconds, actual_mse_ratio)- 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. Required: prediction_hash, approach_taken.
factorguide_submit_payment(chain, tx_hash)- 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. Required: tx_hash, chain.
factorguide_synergy_detect(n_samples, n_variables, ic_matrix_ref, transform_method, walsh_coefficients)- 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.
Last successful function declaration observed on . Source: https://factorguide.io/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://factorguide.io/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 0 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-04-09 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 0 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 1.2.1 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-04-03 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-04-03 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub | |
| mcp tools declared | 7 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | factorguide.io | |
| mcp endpoint status | ok | The server listed 7 functions when asked. | as of probe | factorguide.io |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json