io.github.Kromatic-Innovation/fermi
REMOTE · FERMI.KROBAR.AI · SCANNED SEP 20
Calibrated probability distributions from natural-language questions via REST and MCP.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability52
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 976 tokens (~325/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.Kromatic-Innovation/fermi MCP server?
io.github.Kromatic-Innovation/fermi is a hosted endpoint at https://fermi.krobar.ai/mcp/sse/, 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 · fermi.krobar.ai
claude mcp add --transport http kromatic-innovation-fermi 'https://fermi.krobar.ai/mcp/sse/'
{
"mcpServers": {
"kromatic-innovation-fermi": {
"url": "https://fermi.krobar.ai/mcp/sse/"
}
}
} {
"servers": {
"kromatic-innovation-fermi": {
"type": "http",
"url": "https://fermi.krobar.ai/mcp/sse/"
}
}
} [mcp_servers.kromatic-innovation-fermi] url = "https://fermi.krobar.ai/mcp/sse/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kromatic-innovation-fermi": {
"type": "remote",
"url": "https://fermi.krobar.ai/mcp/sse/",
"enabled": true
}
}
} openclaw mcp add kromatic-innovation-fermi --url 'https://fermi.krobar.ai/mcp/sse/' --transport streamable-http
mcp_servers:
kromatic-innovation-fermi:
url: "https://fermi.krobar.ai/mcp/sse/" {
"McpServers": {
"kromatic-innovation-fermi": {
"Transport": "http",
"Url": "https://fermi.krobar.ai/mcp/sse/"
}
}
} assistant mcp add kromatic-innovation-fermi -t streamable-http -u 'https://fermi.krobar.ai/mcp/sse/'
{
"mcpServers": {
"kromatic-innovation-fermi": {
"type": "http",
"url": "https://fermi.krobar.ai/mcp/sse/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Aug 26 0
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 20 Sept 2026 · Probed https://fermi.krobar.ai/mcp/sse/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=krobar.ai | CN=WE1,O=Google Trust Services,C=US | 2 Aug 2026 | 31 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | dd8d140e1fd09a0c13b71fe1f83c645f |
| SANs: krobar.ai, *.krobar.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of fermi.krobar.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| krobar.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 405 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://fermi.krobar.ai/mcp/sse/ | Verified | 200 | |
| http (plaintext) | http://fermi.krobar.ai/mcp/sse/ | HTTPS enforced | 301 | https://fermi.krobar.ai/mcp/sse/ |
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 →
buy_credits ~153
Purchase credits using a saved payment method (off-session). Requires a prior Stripe Checkout session to have saved a card. Credits are $0.50 each. Use GET /api/v1/billing/pricing to confirm the current price. Args: credits: Number of credits to purchase (minimum 1). api_key: Your Fermi API key from POST /api/v1/accounts. Required. Returns: Dict with credits_purchased, new_balance, and payment_status. Raises: ValueError: if authentication fails, no payment method is on file, or the card is declined.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | – |
| credits | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
estimate ~568
Return a calibrated probability distribution for a natural-language question. Args: question: The natural-language question (e.g. "What will the price of Bitcoin be in 6 months?"). unit: The unit the answer should be expressed in (e.g. "USD", "people", "meters"). target_horizon: When the estimate applies (e.g. "6 months", "2030", "current"). disclaimer_acknowledged: Must be true. Confirms you understand estimates are probabilistic decision-support only, not financial/medical/legal advice. requested_tier_id: Tier (1=fast sync, 2=grounded sync, 3=deep research async). Default 1. context: Optional extra context to condition the estimate. coverage_probability: Width of the confidence interval (0, 1). Default 0.9 (90% CI). source_inputs: Optional list of structured inputs (files, tables) for the model to consider. Each item needs source_type ("qualitative_text", "spreadsheet", or "structured_file") and either content (text) or structured_data (dict/list). callback_url: Optional webhook URL. When set, the completed or failed result is POSTed here with an HMAC signature, so you don't need to poll for async tiers. api_key: Your Fermi API key from POST /api/v1/accounts. Omit to use the anonymous tier. provider: Optional LLM provider selector ("openai" or "anthropic"). When omitted the server uses its configured default. Tier 1 supports both providers; tiers 2-3 currently accept "openai" only. model: Optional model id for the selected provider. Must match the model configured for (tier_id, provider); omit to accept the default. Returns: EstimateSuccessResponse as a dict: estimation_interval, distribution_family, distribution_parameters, point_estimate, re…
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | – |
| callback_url | – | – | – |
| context | – | – | – |
| coverage_probability | number | – | – |
| disclaimer_acknowledged | boolean | yes | – |
| model | – | – | – |
| provider | – | – | – |
| question | string | yes | – |
| requested_tier_id | integer | – | – |
| source_inputs | – | – | – |
| target_horizon | string | yes | – |
| unit | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
feedback ~193
Submit feedback, a feature request, or a bug report to the Fermi team. An email is sent to the team and a copy is sent to the address you provide. Args: feedback_type: One of "feedback", "feature_request", or "bug". message: Your feedback or request (10-5000 characters). Be specific. sender_email: Your email address. A confirmation copy is sent here. sender_name: Your name (optional). api_key: Your Fermi API key (optional). If provided, your account ID is attached to the message for context. Returns: Confirmation with status "sent". Raises: ValueError: if validation fails or email delivery fails.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | – |
| feedback_type | string | yes | – |
| message | string | yes | – |
| sender_email | string | yes | – |
| sender_name | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the io.github.Kromatic-Innovation/fermi MCP server?
io.github.Kromatic-Innovation/fermi is an MCP server listed in the public MCP registry as io.github.Kromatic-Innovation/fermi. Calibrated probability distributions from natural-language questions via REST and MCP. This page covers its hosted endpoint (https://fermi.krobar.ai/mcp/sse/).
Is the io.github.Kromatic-Innovation/fermi MCP server safe to use?
io.github.Kromatic-Innovation/fermi scores 66 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 io.github.Kromatic-Innovation/fermi MCP server expose?
io.github.Kromatic-Innovation/fermi exposes 3 tools: estimate, feedback, buy_credits. Their descriptions and schemas cost roughly 914 tokens of context every time the server is loaded.
Does the io.github.Kromatic-Innovation/fermi MCP server require authentication?
No. We connected to io.github.Kromatic-Innovation/fermi without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.Kromatic-Innovation/fermi MCP server still maintained?
io.github.Kromatic-Innovation/fermi is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.