timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Verification harness for LLM agent outputs — catches the silent failures agents ship as done.
Skills that teach the AI this kind of work; they work alongside this one
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…
scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 16/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 | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 28/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: 17 (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 FailLoud. Follow https://mcp.popnx.com/i/yalakala-naveen-failloud.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/3 checks · Runs on your computer · ✓ Commands checked Nov 18, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server FailLoud for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "failloud": { "command": "uvx", "args": [ "failloud", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the FailLoud tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
SettingsDeveloperEdit Config
{
"mcpServers": {
"failloud": {
"command": "uvx",
"args": [
"failloud",
"mcp"
]
}
}
}Use FailLoud and tell me what you can do for me, then show me one thing✓ If Claude says it is using FailLoud or shows a FailLoud 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 FailLoud yet
FailLoud runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect FailLoud
Works with Claude Code, with some setup first
Install Python (uv) on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server FailLoud for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user failloud -- uvx failloud mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the FailLoud tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user failloud -- uvx failloud mcpYou should see FailLoud listed as connected
Use FailLoud and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using FailLoud or shows a FailLoud 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, with some setup first
Install Python (uv) on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server FailLoud for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "failloud": { "command": "uvx", "args": [ "failloud", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the FailLoud tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Use FailLoud and tell me what you can do for me, then show me one thing✓ If Cursor says it is using FailLoud or shows a FailLoud 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, with some setup first
Install Python (uv) on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server FailLoud for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "failloud": { "type": "stdio", "command": "uvx", "args": [ "failloud", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the FailLoud tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Use FailLoud and tell me what you can do for me, then show me one thing✓ If VS Code says it is using FailLoud or shows a FailLoud 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
Claude Code
claude mcp add --scope user failloud -- uvx failloud mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"failloud": {
"command": "uvx",
"args": [
"failloud",
"mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"failloud": {
"command": "uvx",
"args": [
"failloud",
"mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"failloud": {
"type": "stdio",
"command": "uvx",
"args": [
"failloud",
"mcp"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
pypi: failloudBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
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 20, 2026
The registry name was verified with the GitHub account Yalakala-Naveen, which owns the repo
Code last changed 3 days ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked yet
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/yalakala-naveen-failloud)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 3 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.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 3 days ago, and the latest version (0.6.0) reached the registry 2 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)
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
Keyword research, site audits, rank tracking and AI visibility for your AI agent.
Official Exa MCP for web search, content fetching, and multi-step research.
Official Microsoft Learn MCP Server – real-time, trusted docs & code samples for AI and LLMs.
Search and read Empryo's documentation. Read-only, no auth, no local access.
cotal.ai actions: product overview, site search, build log, feedback, Cloud waitlist, updates, calls
| This one FailLoud | OpenSEO | Exa | Microsoft Learn MCP | Docs | COTAL actions (cotal.ai) | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | 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 | No | No | No | No | No | No |
| Add with + in Claude | No | Yes | Yes | Yes | No | No |
| Basic checks | 3/3 | 5/5 | 2/4 | 4/4 | 4/4 | 4/4 |
| License | MIT | MIT | MIT | CC-BY-4.0 | NOASSERTION | Apache-2.0 |
| 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.
A verification harness for LLM agent outputs. It catches the silent failures agents ship as `done`.
Agents rarely fail loudly. They return status: "done" with an empty payload. They claim they sent, posted, and published — and nothing in the output proves any of it happened. They plan from state that went stale two steps ago, report counts their own itemized record contradicts, and deliver files with silent holes inside them. Every dashboard stays green, because the agent graded its own homework.
FailLoud reads an agent's output the way a skeptical reviewer would — and produces a failure report instead of a shrug.
Built by a Forward Deployed Engineer from production failures — every check in this tool exists because a real agent failed this way in production and the miss became a rule.
▶ Try it in your browser: [FailLoud Playground](https://yalakala-naveen.github.io/failloud/) — paste an agent output, get the failure report. No install, nothing uploaded.
| Check | Name | What it catches |
|---|---|---|
| FL001 | placeholder_shipped | Output declared done while the payload is empty or still holds draft scaffolding — lorem ipsum, unrendered {{template}} braces, "coming soon". *A page once went live, launch marked complete, with placeholder copy still in the body. Nothing crashed; every signal said success.* |
| FL002 | unbacked_claim | A claimed action (sent, posted, published, updated…) with no evidence — no message id, URL, receipt, or artifact. *A run once reported a batch as sent while a bounce sat unrecorded; "sent" was asserted by the same component that did the sending.* |
| FL003 | stale_state | Work based on state/context already older than allowed, state with no freshness timestamp at all, or a state-version skew between handover and run. *A pipeline planned flawlessly from a snapshot of a world that no longer existed.* |
| FL004 | count_mismatch | A reported count that disagrees with the itemized record in the same document, or a total that isn't the sum of its parts. *Reports counted actions attempted; audiences read them as actions completed. Only the list was ever true.* |
| FL005 | missing_components | Required fields present-but-empty, and dead stretches inside segmented deliverables (zero-length segments, silent gaps). *A delivered video passed every existence check while one segment inside it was silent.* |
| FL006 | unsupported_answer | A RAG answer whose citations resolve to nothing that was retrieved, whose cited sources are empty, or whose numbers appear in no source. *Retrieval gets checked by every dashboard; whether the answer is backed by what was retrieved is checked by nobody.* |
These are not eval scores. FailLoud never asks a model whether an output "looks good" — every verdict is deterministic, reproducible, and explainable line by line. No LLM sits in the verdict path.
pip install failloud # CLI + library (stdlib-only core, zero dependencies)
pip install "failloud[mcp]" # + the MCP server
Or from a clone: pip install . (add .[mcp] for the server).
The same six checks also ship as a SKILL.md — a judgment playbook an agent runs on its own output before claiming done, for Claude Code, Cursor, Copilot and other SKILL.md-compatible agents. Listing copy and worked examples live in skill/.
The repo ships a realistic agent output that commits the first five failures (examples/failing_output.json) and its corrected twin (examples/passing_output.json):
$ failloud check examples/failing_output.json
FAILLOUD — agent output verification Source: examples/failing_output.json Verdict: FAIL (8 error(s), 1 warning(s))
[FL001] placeholder_shipped — FAIL ✗ $.output.body — Placeholder content shipped as final output: matched 'coming soon', 'lorem ipsum', '{{', '}}'. [FL002] unbacked_claim — FAIL ✗ $.claims[1] — Claimed action 'card_published' has no evidence — no id, URL, receipt, or artifact in the claim backs that it happened. [FL003] stale_state — FAIL ✗ $.state.context_updated_at — State timestamp is 77.1h old at run time (limit 24h) — the run worked from context older than allowed. ✗ $ — Run based itself on state version 9 but the state it carried is version 7 — the handover and the work disagree about the world. [FL004] count_mismatch — FAIL ✗ $.counts.delivered — Count for 'delivered' is reported as 12 but the itemized record at $.items.delivered contains 9 item(s) — the report overstates what the record supports. ✗ $.counts.sent — Count for 'sent' is reported as 12 but the itemized record at $.items.sent contains 9 item(s) — the report overstates what the record supports. [FL005] missing_components — FAIL ! $.output.archive_url — Field 'archive_url' is present but empty while its siblings carry content — verify it was meant to be blank. ✗ $.segments[1] — Segment 1 has zero length (4s–4s) — a component that occupies a slot and contains nothing. ✗ $.segments[2] — Dead stretch of 5.5s before segment 2 (gap limit 2s) — the deliverable goes silent where content should be. [FL006] unsupported_answer — PASS
$ echo $? 1
$ failloud check examples/passing_output.json FAILLOUD — agent output verification Source: examples/passing_output.json Verdict: PASS (0 error(s), 0 warning(s))
[FL001] placeholder_shipped — PASS [FL002] unbacked_claim — PASS [FL003] stale_state — PASS [FL004] count_mismatch — PASS [FL005] missing_components — PASS [FL006] unsupported_answer — PASS No silent failures found. The output backs its claims.
Exit codes are the CI contract: 0 pass, 1 verification failed (the agent output failed, not the tool), 2 the tool itself could not run.
--format md produces the artifact you attach to a run, an issue, or a PR:
$ failloud check examples/failing_output.json --format md --out report.md
# FAILURE REPORT
Verdict: FAIL — 8 error(s), 1 warning(s)
| Check | Name | Result | Findings |
|---|---|---|---|
| FL001 | placeholder_shipped | FAIL | 1 |
| FL002 | unbacked_claim | FAIL | 1 |
| FL003 | stale_state | FAIL | 2 |
| FL004 | count_mismatch | FAIL | 2 |
| FL005 | missing_components | FAIL | 3 |
| FL006 | unsupported_answer | PASS | 0 |
*Why it matters: The claimed number is what travels into dashboards and decisions; the itemized record is the only part that was ever true.*
$.counts.sent — Count for 'sent' is reported as 12 but the itemized record at $.items.sent contains 9 item(s) — the report overstates what the record supports.
Run FailLoud in CI on every agent output your pipeline produces. The Action wraps failloud check and follows the same exit contract — the job fails when the output fails:
name: Verify agent outputs
on: [push, pull_request] jobs: failloud: runs-on: ubuntu-latest steps:
The step exposes a verdict output (PASS / FAIL) for downstream steps. Exit codes: 0 the output passed, 1 verification failed (the output, not the tool), 2 FailLoud could not run.
If your project's agent outputs pass FailLoud in CI, say so — add this badge to your README:
[](https://github.com/Yalakala-Naveen/failloud)
It renders as:
The badge is a claim, and FailLoud's whole point is that claims need evidence — only add it while a FailLoud check actually runs and passes in your CI.
A report says what FailLoud found; a receipt proves it. Seal any run into a hash-chained receipt file:
$ failloud check examples/failing_output.json --receipt-out receipts.jsonl
$ failloud check examples/passing_output.json --receipt-out receipts.jsonl $ failloud verify-receipts receipts.jsonl Receipt chain OK — 2 receipt(s) verified in receipts.jsonl.
Each receipt embeds the full result and two SHA-256 hashes: result_hash seals the result and its source, and receipt_hash seals every receipt field including prev_hash — the previous receipt's hash. Edit a verdict, erase a finding, drop or reorder a receipt, and verify-receipts (exit 1) names the break. Anyone holding the chain can re-verify it offline, stdlib only — the audit trail an orchestrator needs before one agent's "done" becomes the next agent's input. In Python: create_receipt, verify_receipt, verify_chain; over MCP: create_verification_receipt, verify_receipt_chain.
FailLoud works on any JSON an agent produces — the checks are shape-tolerant heuristics, not a schema straitjacket. They verify the most when the output follows this envelope (every field optional; each one present is one more thing that gets checked instead of trusted):
{
"task": "Send the weekly digest and publish the summary card", "status": "done", "generated_at": "2026-11-11T14:05:00Z", "summary": "Sent the digest to 9 subscribers and published the summary card.", "claims": [ {"action": "email_sent", "target": "subscriber-list", "evidence": {"message_id": "msg_8f42"}}, {"action": "card_published", "target": "community-feed", "evidence": {"post_id": "post_2481", "url": "https://…/posts/2481"}} ], "counts": {"sent": 9, "delivered": 9}, "items": {"sent": [ … ], "delivered": [ … ]}, "state": {"context_updated_at": "2026-11-11T13:40:00Z", "version": 9}, "based_on": {"expected_state_version": 9}, "output": {"subject": "…", "body": "…", "archive_url": "https://…"}, "segments": [{"start": 0, "end": 4}, {"start": 4, "end": 9}] }
Enforce your own required fields with --require output.archive_url,output.body or a JSON Schema (--schema schema.json; the required/properties/items subset is supported). Thresholds are flags: --max-state-age-hours, --max-segment-gap-seconds. Run a subset with --only FL002,FL004. --format json gives machines the same verdict.
One-shot checks verify a snapshot. Pipelines produce outputs over time — a runner overwrites the same file as it retries, results land in a directory one by one. failloud watch polls a file or a directory of *.json outputs and re-verifies each one when its content actually changes (SHA-256 of the bytes, so a touch that changes nothing produces no duplicate verdict):
$ failloud watch runs/ --receipt-out receipts.jsonl # continuous; Ctrl-C stops
$ failloud watch runs/ --once # one sweep, CI-style exit code $ failloud watch agent_output.json --once # a single file works too
New files in the directory are picked up on the next poll, deleted files are forgotten, and a file that is mid-write or temporarily invalid JSON is reported as an error and retried when its bytes change — one bad file never kills the watcher. With --receipt-out, every verdict is sealed into th