Is the Factorguide MCP server down?

mcp-registry/io.factorguide/factorguide · v1.26.0

healthy
Last checked 2026-10-26 19:55 UTC · handshake 300ms

As of 2026-10-26 19:55 UTC, the Factorguide MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 3 minutes.

uptime (30d checks)
100%
checks observed
4,944
outages (90d)
1
tools
10

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

Point your MCP client at this streamable-http endpoint: https://factorguide.io/mcp

Agent-readiness: C (72/100)

C (72/100): 0 error(s), 3 warning(s) across 7 tool(s); ~2,204 tokens of tool definitions.
Scores higher than 7% of 15,761 MCP servers Glimind has audited.
Its tool list costs an agent ~2,204 tokens per session — lighter than 55% of servers.
70 → 72 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions50
Safety hints9
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (4)

7 of 7 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: factorguide_diagnose, factorguide_explain, factorguide_navigate, factorguide_regime_detect, factorguide_report_outcome and 2 more

29 parameter(s) across 4 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: factorguide_diagnose, factorguide_navigate, factorguide_report_outcome, factorguide_synergy_detect

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: factorguide_submit_payment

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 2 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.factorguide%2Ffactorguide/fixes

factorguide_explain 1 change
{
  "name": "factorguide_explain",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "prediction_hash"
    ],
    "properties": {
      "prediction_hash": {
        "type": "string",
        "description": "prediction_hash from a previous navigate response"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
factorguide_submit_payment 1 change
{
  "name": "factorguide_submit_payment",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "tx_hash",
      "chain"
    ],
    "properties": {
      "chain": {
        "type": "string",
        "description": "Chain identifier, e.g. 'eip155:8453' or 'tempo:4217'"
      },
      "tx_hash": {
        "type": "string",
        "description": "On-chain transaction hash"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.factorguide/factorguide"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.factorguide/factorguide"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.factorguide%2Ffactorguide.svg)](https://glimind.com/server/mcp-registry%2Fio.factorguide%2Ffactorguide?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.factorguide%2Ffactorguide?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.factorguide%2Ffactorguide.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.factorguide%2Ffactorguide.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.factorguide%2Ffactorguide?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:a324c53aacc99bfd…, first seen 2026-10-17, included at leaf 4877 of 75,142. Version history · verify what your client received.

Tools (10)

Compare: most reliable other servers · most reliable ml servers · most reliable knowledge servers · most reliable data servers · most reliable payments servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Factorguide MCP server down right now?

As of 2026-10-26 19:55 UTC, the Factorguide MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 3 minutes.

How many tools does Factorguide MCP server provide?

Factorguide MCP server advertises 10 tools, including diagnose, factorguide_diagnose, factorguide_explain, factorguide_navigate, factorguide_regime_detect.

How do I install Factorguide MCP server?

Point your MCP client at this streamable-http endpoint: https://factorguide.io/mcp

Is the Factorguide MCP server safe to connect to an AI agent?

Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Factorguide MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve