factorguide
Server Details
Send a coupling matrix, get zone classifications and optimal factorization strategy.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- Bwana7/factorguide
- GitHub Stars
- 0
- Server Listing
- FactorGuide
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.8/5 across 7 of 7 tools scored. Lowest: 2.9/5.
Each tool targets a distinct operation: diagnostic, navigation, explanation, regime detection, outcome reporting, payment, and synergy detection. No overlapping purposes; even the two 'detect' tools are clearly separated by domain (regime vs. synergy).
Tool names are prefixed with 'factorguide_' but use a mix of single verbs (diagnose, explain, navigate) and noun_verb (regime_detect, synergy_detect) or verb_noun patterns (report_outcome, submit_payment). No consistent verb_noun or noun_verb pattern across the set.
With 7 tools, the server covers a well-scoped set of operations for factor analysis guidance. The count is neither too small to be useful nor too large to be unwieldy.
The core workflow (navigate, diagnose, explain, report_outcome, submit_payment) forms a coherent loop for factorization guidance and feedback. Two pending tools (regime_detect, synergy_detect) indicate planned expansion but do not create critical gaps.
Available Tools
7 toolsfactorguide_diagnoseInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| i | Yes | First variable name | |
| j | Yes | Second variable name | |
| variance_i | No | ||
| variance_j | No | ||
| sample_size | Yes | ||
| coupling_value | Yes | IC or coupling value |
factorguide_explainInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| prediction_hash | Yes | prediction_hash from a previous navigate response |
factorguide_regime_detectInspect
Detect coupling regime changes in time series via windowed IC. Specification pending — v1.1 target.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
factorguide_report_outcomeInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| ess_ratio | No | ||
| psis_khat | No | ||
| log_lik_gap | No | ||
| approach_taken | Yes | ||
| n_replications | No | ||
| prediction_hash | Yes | ||
| runtime_seconds | No | ||
| actual_mse_ratio | No |
factorguide_submit_paymentInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| chain | Yes | Chain identifier, e.g. 'eip155:8453' or 'tempo:4217' | |
| tx_hash | Yes | On-chain transaction hash |
factorguide_synergy_detectInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| n_samples | No | ||
| n_variables | No | ||
| ic_matrix_ref | No | ||
| transform_method | No | ||
| walsh_coefficients | No |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Your Connectors
Sign in to create a connector for this server.