World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Checks the most important factual claims in AI output against live web sources by default.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 4/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 8/8 | The cloud endpoint answered at the last check |
| Usage score | 24/100 |
Quality: Passed 3/5 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Faultline. Follow https://mcp.popnx.com/i/nxtg-ai-faultline.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/5 checks · What you ask goes through the maker’s server (faultline-api.fly.dev) · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude · about 5 min
You need a Faultline key (create it on the maker’s site) · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
CustomizeConnectors
Copy each value into the field with the same name in Claude, then click Continue
Faultlinehttps://faultline-api.fly.dev/mcpUnder Request headers, add this name and value
X-API-Key<paste your key here>Paste the key only into the app’s field, never into a chat or to anyone
Click Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add
+ConnectorsFaultline
Use Faultline and tell me what you can do for me, then show me one thing✓ If Claude says it is using Faultline or shows a Faultline tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Faultline yet
Faultline needs your own key to connect, but OpenAI’s help page only describes OAuth sign-in; there is no key option we could verify
A · Use an app that can connect Faultline
B · Others in Other that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code · about 5 min
You need a Faultline key (create it on the maker’s site)
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --transport http --scope user faultline https://faultline-api.fly.dev/mcp --header 'X-API-Key: your-value'Replace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
You should see Faultline listed as connected
Use Faultline and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Faultline or shows a Faultline tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor · about 5 min
You need a Faultline key (create it on the maker’s site)
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
In the Faultline settings, X-API-Key is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Faultline and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Faultline or shows a Faultline tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code · about 5 min
You need a Faultline key (create it on the maker’s site)
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
In the Faultline settings, X-API-Key is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Faultline and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Faultline or shows a Faultline tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
https://faultline-api.fly.dev/mcpJSON settings are under “For developers” below
Claude Code
claude mcp add --transport http --scope user faultline https://faultline-api.fly.dev/mcp --header 'X-API-Key: your-value'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"faultline": {
"url": "https://faultline-api.fly.dev/mcp",
"headers": {
"X-API-Key": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"faultline": {
"type": "http",
"url": "https://faultline-api.fly.dev/mcp",
"headers": {
"X-API-Key": "your-value"
}
}
}
}Descriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
The server asks you to sign in before it lists its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account nxtg-ai, which owns the repo
Code last changed yesterday
Uses Apache-2.0
Refused access (HTTP 401) without offering OAuth sign-in. It may need a key, or it may be blocking bots; not confirmed.
Needs a key or token that you copy and paste yourself
Not checked yet; we read the tool list when we check the endpoint
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/nxtg-ai-faultline)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: X-API-Key
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed yesterday, and the latest version (0.12.2) reached the registry 2 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| This one Faultline | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | Yes | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/5 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | Apache-2.0 | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Future-proof your agent stack. Independent of every model vendor: NXTG.ai does not build the models Faultline checks.
Faultline decomposes AI-generated output into atomic claims, verifies each against live evidence, and can fail a CI build on the result.
Release stage: alpha. Usable today, with sharp edges. Measured accuracy, not pre-registered: on 200 human-labelled Factcheck-Bench claims, the production engine (commit
ba11345, judge modelgemini-2.5-flash; its verify path is unchanged since) scored 0.755 balanced accuracy [95% CI 0.678, 0.829] on the 193 claims with a true or false label. Four runs on the same sample this week read 0.755 to 0.802. Supported counts as true and contradicted as false; mixed and unverified count as wrong. Method and rows:docs/research/2026-11-06-parallel-fast-vs-advanced.md, scorerscripts/accuracy-g0-score.py. Anything may change before 1.0.
The hosted API ships three governance records as code: a risk register export (POST /scan/risk-register), a tamper-evident audit log manifest (GET /audit/log/manifest, admin keys only), and human sign-off records (POST /scans/:id/approve, GET /scans/:id/approvals). In the manifest, each chain hash is the SHA-256 of the entry hash followed by the previous chain hash. You can recompute the chain with openssl dgst -sha256 alone, with no Faultline tooling.
| Item | State | How checked |
|---|---|---|
| CLI on npm | @nxtg/faultline 0.11.1 | npm view @nxtg/faultline version |
| Hosted API | https://faultline-api.fly.dev, version 0.11.1 | curl https://faultline-api.fly.dev/health |
| Web app | https://faultline.nxtg.ai (separate repo, faultline-web, on Vercel) | live pricing page read 2026-10-01 |
| Plans | Free 5 scans/month. Personal $19/mo, 100 scans. Pro $49/mo, 500 scans. Enterprise: custom, scan allowance set in the contract | https://faultline.nxtg.ai/pricing |
| Multi-model consensus | Enterprise only. The API returns 403 consensus_not_in_plan to any caller below Enterprise, before the stream opens | packages/api/src/plugins/consensus-entitlement.ts; live check by fp 2026-10-01 (pro, personal and free 403, enterprise 200, mock provider) |
POST /critique | Needs an API key. Rate limited. Covered by the provider-spend cap and written to the spend ledger | packages/api/src/routes/critique.ts |
| Provider-spend cap | $100/month. The ledger records every managed scan and critique. Enforcement ships dormant (FAULTLINE_PROVIDER_SPEND_CAP=on turns it on) and is off in production | docs/provider-spend-cap.md; GET /usage showed providerBudget.enforced=false on 2026-10-01 |
| Per-key monthly scan cap (API side) | Dormant (FAULTLINE_USAGE_CAP). Plan limits above are enforced by faultline-web | docs/usage-cap.md |
| Capability | Description |
|---|---|
| Atomic claim extraction | Decomposes AI output into fact / opinion / interpretation with importance scoring |
| Per-claim verification | Verdict: supported / contradicted / mixed / unverified + confidence score |
| Scan comparison | POST /scan/compare + faultline compare — new/removed claims, verdict changes, trust score delta |
| CI gate | faultline compliance-report --ci exits 1 when the scan's overall risk is high or critical, an article check in the report has failed, the report's domain checklist item has not passed, or the report score is below --threshold; --strict also fails on partly met article checks and on checklist items not assessed. Otherwise it exits 0 |
| Weakest-link detection | Per-claim fragility scoring — finds the claim that most undermines the argument |
| Claim dependency graph | Mermaid and Graphviz DOT visualizations |
| Rules engine | YAML-defined rules; built-in PII, bias, toxicity rulesets |
| CI gate | --fail-on high returns exit code 1; SARIF output for GitHub Code Scanning |
| Enterprise API | REST API (about 190 routes) with key management, audit trail, rate limiting, webhooks, batch scanning, caching |
| One provider per scan | A hosted scan runs on Gemini (Enterprise may name another provider) and never falls back to another provider; a circuit breaker returns 503 for 5 minutes after 5 failures |
| Monitoring | GET /health/deep, GET /metrics (Prometheus), GET /status (HTML dashboard) |
| Scheduled jobs | POST /jobs — recurring scans on a cron schedule with webhook delivery |
| Integrations | Python client source in sdks/python, MCP server packages/mcp, Terraform provider packages/terraform-provider, GitHub Action nxtg-ai/faultline-action (see SDKs) |
| Multi-tenant | Tenant CRUD, API key association, per-tenant usage aggregation |
| Cost tracking | Per-scan token/cost estimation; GET /costs with provider/tenant/date filters |
| Scan history | GET /scans/search — full-text across your API key's past scans (admin key: all), cursor pagination |
| Rule templates (HIPAA, SOX, FERPA, Gov) | HIPAA / SOX / FERPA / Gov templates; POST /scan/compliance/:template |
| Bulk import | POST /scan/bulk — ZIP of documents, async job, GET /jobs/:id/progress |
| Swagger UI | GET /docs — interactive OpenAPI 3.0 spec with Try-it for every endpoint |
| Claim explainability | GET /claims/:id/explain — reasoning chain, evidence found, actionable suggestions |
| Scan diff | POST /scan/diff — scan two texts, inline diff (added/removed/changed/unchanged) |
| Deadline list | GET /compliance/deadlines — a list of upcoming regulatory dates with days until each; no assessment |
| Deadline keyword check | POST /compliance/scan-check — match claim text against keywords tied to those dates |
| i18n | Accept-Language: es/fr/en — localized error messages and report labels (EN/ES/FR) |
| Property-based tests | fast-check oracle coverage: confidence bounds, dedup invariants, cost aggregation, sort stability |
| GDPR data requests (Article 15 export, Article 17 erasure) | Article 15 export (GET /tenants/:id/export → ZIP) + Article 17 erasure (DELETE /tenants/:id/data) covering scan history, audit log, notifications, webhooks, costs, schedules |
| Multi-model consensus | POST /scan/stream with pipelineConfig.consensus: true. Enterprise only, enforced server-side (403 below Enterprise) |
| Claim critique | POST /critique: critique plus improved prompt for failed claims; API key, rate limit and provider-spend cap apply |
| Real-time scan streaming | GET /scan/stream?text=...&provider=mock — Server-Sent Events; progressive per-claim delivery via onClaimVerified callback; streams start → claim_verified × N → complete; no polling required |
| Mutation-tested core | Stryker gate (CRUCIBLE Gate 6, threshold 80%): cli/scan.ts 81.97%, stream.ts 88.64%, compliance-report.ts 80.81%, GDPR stores 80.94% to 96.81%. Last measured 2026-03-21 to 2026-04-17 per docs/mutation-testing.md; not re-run since |
| Provider | Requires | Best For |
|---|---|---|
| Gemini | GEMINI_API_KEY | Live web grounding (free key available) |
| Perplexity | PERPLEXITY_API_KEY | Real-time search-native verification |
| OpenAI | OPENAI_API_KEY | Training-data verification, GPT ecosystem |
| Claude | ANTHROPIC_API_KEY | Training-data verification, reasoning-heavy docs |
| Mock | None | CI pipelines, unit tests, offline development. Returns synthetic verdicts and verifies nothing; the CLI never falls back to it silently |
Switch providers with --provider . No code changes required. With no provider key and no FAULTLINE_API_KEY, the CLI says nothing was checked and exits instead of inventing a verdict (since v0.10.1). With FAULTLINE_API_KEY set, scan --input, scan --file, guard and the MCP server run the scan on the hosted API with server-side provider keys (since v0.12.2 for scan). The batch modes --dir and --templates run on your own provider key.
faultline scan --file document.pdf or POST /scan/upload; powered by pdf-parse + tesseract.js--input doc.txt--dir ./docs --glob "*.md"POST /scan/reportjson — programmatic processing, CI pipelinesmarkdown — PRs, reports, documentationhtml — browser-readable audit reportssarif — VS Code Problems panel, GitHub Code Scanning (--sarif shorthand writes results.sarif)POST /keys, GET /keys, GET /keys/:id, PATCH /keys/:id, DELETE /keys/:id; soft-disable/enable; scoped permissions (scan / report / upload / admin / pro)GET /keys/dormant), expiry notifications (7d/1d thresholds), bulk delete/disable/enable, usage analytics (GET /keys/usage), hygiene dashboard (GET /keys/usage/view)GET /audit/log (query + filter), GET /audit/log/stats, GET /audit/log/export (NDJSON); tenant-scoped viewGET /usage (admin keys also see the provider-spend budget)X-RateLimit-* headers402) and a fleet provider-spend cap (503), both dormant until switched on; the spend ledger records every managed scan and /critique call either wayPOST /tenants); all resources scoped by tenant: scan history, notifications, webhooks, audit log; GET /tenants/:id/usageGET /costs (keyId/provider/date filters + aggregate)GET /dashboard: live scan feed, provider health, active keys, scan counts (today/week/month), risk distributionPOST /webhooks; scan.complete / scan.failed / job.complete events; HMAC-SHA256 signing; per-webhook retry config (maxAttempts 1–5, retryDelayMs); rate limiting (FAULTLINE_WEBHOOK_RATE_LIMIT); circuit breaker (FAULTLINE_WEBHOOK_CIRCUIT_THRESHOLD/COOLDOWN_MS); delivery log + dashboardPOST /scan/batch (1–10 texts, concurrent, partial failure semantics); see docs/ci-integration.mdPOST /scan/compare: diff two scan results (new/removed claims, verdict changes, trust score delta)FAULTLINE_CACHE_TTL_MS); X-Cache: HIT/MISS header; GET /cache/stats, DELETE /cachePOST /jobs: recurring scans on a */N * * * * cron schedule; results dispatched to webhookUrl