Infobroker
NPM · INFOBROKER
Multi-provider research MCP server: unified web search, fact-checking, personal knowledge base.
Available components
Last scanned (8 hours ago)
Scores higher than 72% of npm servers
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 32 of 116 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to flukeatzerocool/infobroker). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2680 tokens (~382/item across 7 items; 7 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- Package version: 2026.10.28 → 2026.11.4 functional
- 3 Nov 26 +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.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
- Security disclosure: fail → unverified ▼ functional
- 28 Oct 26 +29
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.00 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 2026.10.22 → 2026.10.28 functional
- 23 Oct 26 0
- Stability: Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare. security
- Tool safety: Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan. security
- Schema quality: Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess. functional
- Capabilities: Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake. functional
- Tool coverage: Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess. functional
- 22 Oct 26 0
- Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 2026.10.20 → 2026.10.22 functional
- 21 Oct 26 0
- Package version: 2026.10.2 → 2026.10.20 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 5 Nov 2026 · Analysed npm/infobroker@2026.11.4
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | flukeatzerocool/infobroker |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/flukeatzerocool/infobroker/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3692349626 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:e45bb851f1f4057739d3c203176225c9b43c9637771f40a01bbce4d80f596e49751853426af25187ff6be1adebb74ae3d92316adba465d5eac6d2aa79 |
Background: How many MCP packages publish verified provenance →
Dependencies 116 packages
| Packages resolved | 116 |
|---|---|
| Deprecated | 1 |
| Stale | 32 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
infobroker_fetch_page Fetch Page Content ~481
Fetch a URL and extract clean content via a renderer (Jina Reader by default; native-HTTP, Wikipedia, Internet Archive, arXiv, and Stack Exchange alternatives). Use when you have a URL and need readable text, passages ranked against a question, or the page's last-updated date. Do NOT use for topic search (use infobroker_search_web) or cross-source claim verification (use infobroker_verify_claims). `question` returns passages ranked against it, sized by `passage_size` and capped by `max_passages`; `crawl` bounds the same-origin crawl to config caps; `extract` adds JSON-LD, OpenGraph, and microdata; `renderer` selects the backend, and native_fetch is the keyless fallback when Jina is throttled or anti-bot challenged. `max_length` truncates the returned text only; a truncated page is written in full to a temp file. Makes external HTTP calls and needs no API key. A fresh knowledge-base copy is returned before an outbound fetch when available. Fetched pages auto-index into the knowledge base unless the content policy flags them (see infobroker_manage_kb): flag mode returns without storage, block mode refuses. Unreachable URLs return an [ERROR] envelope with remediation; success returns an [OK] envelope with status, provider, results, and meta.
| Name | Type | Req | Description |
|---|---|---|---|
| crawl | boolean | – | Bounded same-origin crawl: recursively fetch same-origin pages up to config caps (default off) |
| detect_date | boolean | – | Detect and report the page's last-updated date (default from config) |
| extract | boolean | – | Return structured metadata (JSON-LD, OpenGraph, microdata) alongside the content (default off) |
| max_length | number | – | Maximum characters to return (default 50000) |
| max_passages | number | – | Number of passages to return (default from config) |
| passage_size | number | – | Target words per passage (default from config) |
| question | string | – | Question to extract ranked passages for, instead of returning the whole page |
| renderer | string | – | Renderer: jina (default), native_fetch, wikipedia, internet_archive, arxiv, or stack_exchange |
| url | – | yes | URL to fetch: a single URL, or up to five URLs fetched in parallel |
No output schema declared.
No examples provided.
infobroker_get_citations Get Citations ~177
Return academic references for a query as BibTeX citations with title, authors, year, venue, and URL. Use when scholarly writing needs a reference list. Do NOT use for general web search (use infobroker_search_web) or contested-claim verification (use infobroker_verify_claims). `query` is a natural-language topic; `max_results` sets the reference count, and larger values take longer and span more sources. Needs no API key when at least one scholarly source is reachable; if every source fails it returns an [ERROR] envelope with remediation, and queries respect per-provider rate limits. Returns an [OK] or [ERROR] JSON envelope.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | number | – | Maximum references to return (1-30, default 8) |
| query | string | yes | Search query |
No output schema declared.
No examples provided.
infobroker_inspect_providers Inspect Providers ~234
Inspect configured search providers: list their state, run a live health check, or report build and spec identity. Use when searches return empty or slow results and you want provider status, quota, or latency, or when choosing which backend to trust. Do NOT use to search (use infobroker_search_web) or to read a page (use infobroker_fetch_page). Read-only: it never modifies configuration, providers, or stored data. `list` snapshots provider state (including each provider's derived privacy posture) and `status` filters it; `health` runs a live outbound probe against `provider` (required for the `health` action; subject to that provider's rate limits, so it can be slow); `spec` reports build and spec identity plus local state health (config drift, backend capabilities, update status). Returns an [OK] or [ERROR] JSON envelope with status, provider, and results.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Operation to perform |
| provider | string | – | Provider slug (required for health) |
| status | string | – | Filter for list action |
No output schema declared.
No examples provided.
infobroker_manage_kb Knowledge Base ~670
Manage the local knowledge base: search cached content, ingest text or URLs, list/get/delete entries, view stats, read persisted claim records, and manage at-rest encryption. Use when you need to archive a generated report (ingest with source_type 'report' and save_to 'kb'), revisit stored content, or manage encryption keys. Do NOT use for fresh external search (use infobroker_search_web) or to fetch a new page (use infobroker_fetch_page). The delete action is destructive and cannot be undone; a lost encryption key makes the store unrecoverable by design. Parameter semantics: `action` selects the operation; `query` for search, `text`/`url` plus `title` and `collection` for ingest, `source_url` for get/delete, and `operation` with `key_file` for the encryption sub-actions; `source_type` and `freshness_tier` tag an ingest and filter search/list; `save_to` defaults to 'kb', `format` to 'markdown', `max_results` to 8; `last_updated` is auto-detected from fetched URLs when omitted; `receipt` attaches a claim-to-source manifest to a report ingest and `verify_report` rechecks it offline. Responses carry an [OK] or [ERROR] envelope: search/list/get return entries, stats returns counts, delete reports the chunks removed.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Operation to perform |
| collection | string | – | Collection name |
| format | string | – | File format for disk save |
| freshness_tier | string | – | Freshness tier tag on ingest (e.g. 'report', 'evergreen') |
| key_file | string | – | Path to a key file (generate_key writes here and refuses an existing path; rekey reads the target key from here). Never pass the secret itself — only a file path. |
| last_updated | string | – | Source last-updated date to store (e.g. '2026-08-24'); auto-detected from fetched URLs when omitted |
| max_results | number | – | Maximum results to return (search/claims action; 1-50, default 8) |
| operation | string | – | Sub-operation for the 'encryption' action |
| query | string | – | Search query (search action) or claim-text filter (claims action) |
| receipt | object | – | Optional verification receipt for a report ingest (REQ-110): claims with cited sources and optional report metadata (REQ-114). The server computes the report hash, per-source hashes, and the digest;… |
| save_to | string | – | Where to save (ingest action): kb, disk, or both. Default kb |
| source_type | string | – | Source type (tag on ingest; filter on search/list) |
| source_url | string | – | Source URL filter (get/delete/claims action), the report identity for verify_report, or identity for ingest |
| text | string | – | Raw text to index (for ingest action) |
| title | string | – | Document/report title |
| url | string | – | URL to fetch and index (for ingest action) |
No output schema declared.
No examples provided.
infobroker_reload_config Reload Configuration ~241
Re-read the configuration file and apply provider, rate-limit, and knowledge-base changes without restarting; active connections are preserved. Use when you have edited config.json or config.local.json, or when passing `patch` to change configuration programmatically. Do NOT use to inspect configuration or provider state (use infobroker_inspect_providers). `patch` deep-merges a partial config into the user layer (config.local.json), rejecting unknown top-level keys, backing up the previous layer, and validating the merged result before writing; `migrate` true backs up and applies registered user-layer migrations before reloading. The call re-reads the startup configuration source and reports any user-layer schema drift. If the new configuration is invalid, the previous configuration stays active and an error is returned. Returns an [OK] or [ERROR] JSON envelope.
| Name | Type | Req | Description |
|---|---|---|---|
| migrate | boolean | – | Back up and apply registered user-configuration-layer migrations before reloading (default false) |
| patch | object | – | Partial configuration deep-merged into the user layer (config.local.json) before reloading; unknown top-level keys are rejected and the previous layer is backed up |
No output schema declared.
No examples provided.
infobroker_search_web Web Search ~587
Search the web, encyclopedia, academic, and code sources through one interface with automatic provider selection and a fallback chain. Use when you need broad or batched search, query autocomplete (suggest), query expansion (expand), ranked passages from the top pages (deep), or a multi-variant research compile that deep-reads each variant (research), and optional in-process analysis of the returned results (analyze: topics, entities, clusters, timeline). Do NOT use for a URL you already have (use infobroker_fetch_page), for high-stakes claim verification (use infobroker_verify_claims), for stored-report recall (use infobroker_manage_kb search), or for academic citations (use infobroker_get_citations). Caches results in the local knowledge base, enforces per-provider rate limits, and needs no API key for the free providers. `fresh: true` skips KB recall and searches external providers. Returns a JSON envelope prefixed `[OK]` or `[ERROR]` with status, provider, results, and meta.
| Name | Type | Req | Description |
|---|---|---|---|
| analyze | boolean | – | Attach in-process analysis to the response: topic terms, entity mentions, semantic result clusters, and a dated timeline. Derived from the returned results only; adds no outbound request (default fal… |
| content_type | string | – | Source kind to search: docs, issue, changelog, blog, spec, or all (default all) |
| deep | boolean | – | Read the top results and return each page's ranked passages against the query |
| expand | boolean | – | Return query-expansion strings instead of search results |
| fresh | boolean | – | Skip the knowledge-base recall shortcut and search external providers (default false) |
| language | string | – | Preferred result language (ISO 639-1, e.g. 'de'). Providers that cannot honor it report it in meta.ignored_params |
| max_results | number | – | Number of results to return (1-30, default 8) |
| page | number | – | Results page number (default 1) |
| priority | string | – | Route by intent: speed, quality, privacy, or free_only |
| provider | string | – | Provider slug (auto-select if omitted) |
| query | – | yes | Search query: a single string, or up to five strings searched in parallel |
| region | string | – | ISO region/country code (e.g. 'us-en', 'DE') |
| research | boolean | – | Research compile: fan out to derived query variants and deep-read each, returning passages grouped by variant (default off) |
| safe_search | string | – | Safe-search filtering: on, off, or strict (default on) |
| suggest | boolean | – | Return query-autocomplete strings instead of results (default false) |
| time_range | string | – | Restrict results to day, week, month, or year |
No output schema declared.
No examples provided.
infobroker_verify_claims Verify Claims ~290
Verify a contested claim against independent sources and return confidence-scored findings. Use when a claim is high-stakes or contested and you need agreement, contradiction, and gaps surfaced with confidence scores. Do NOT use for simple lookups or broad search (use infobroker_search_web) or citation formatting (use infobroker_get_citations). The loop recalls prior findings from the knowledge base, then searches providers and writes findings back; `max_iterations` bounds the refinement passes and per-provider rate limits apply. `query` states the claim plainly; `priority` routes the pool by intent (speed, quality, privacy, free_only); `providers` restricts the pool and omitting it uses the full dispatch chain; `confidence_threshold` sets the bar for confirmation, and findings below it are reported unverified. Returns an [OK] or [ERROR] envelope listing confirmed, contested, and unverified findings with per-source claims and confidence scores.
| Name | Type | Req | Description |
|---|---|---|---|
| confidence_threshold | number | – | Minimum confidence to report a finding as confirmed (0-1, default 0.8) |
| max_iterations | number | – | Maximum search-refinement passes (1-10, default 5) |
| priority | string | – | Route the corroboration pool by intent |
| providers | array | – | Optional array of provider slugs to limit the search to |
| query | string | yes | Search query |
No output schema declared.
No examples provided.
How do I install the Infobroker MCP server?
Infobroker runs locally as an npm package, launched with npx -y infobroker. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · infobroker
claude mcp add flukeatzerocool-infobroker -- npx -y infobroker
What is the Infobroker MCP server?
Infobroker is an MCP server listed in the public MCP registry as io.github.flukeatzerocool/infobroker. Multi-provider research MCP server: unified web search, fact-checking, personal knowledge base. This page covers its npm package (infobroker).
Is the Infobroker MCP server safe to use?
Infobroker scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Infobroker MCP server expose?
Infobroker exposes 7 tools: infobroker_search_web, infobroker_fetch_page, infobroker_inspect_providers, infobroker_verify_claims, infobroker_manage_kb, and 2 more. Their descriptions and schemas cost roughly 2,680 tokens of context every time the server is loaded.
Is the Infobroker MCP server still maintained?
Infobroker is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Infobroker MCP server under?
Infobroker declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.