Meteor Shower Watch Tracker

io.github.mrfentmen由 GitHub 帳號 mrfentmen 發布v1.0.0更新於 Nov 21, 2026

Real local JSON analysis of meteor shower watch in the Stargazing lane. 25 MCP tools, no paywall.

發布方自己的服務:watch.diy – DIY Store Finder

已驗證STDIO僅桌面位置與生活資料與分析

概覽

AI 產生的概覽

透過 25 個工具稽核本機 JSON 中的流星雨觀測物品清單,評估就緒度、涵蓋度、缺口、風險與後續步驟。

可以做什麼
  • 盤點並評分物品清單:依類別計數、花費、新鮮度與 0-100 就緒度
  • 對照設定目標稽核涵蓋度、缺口、限制、基準線與相依關係
  • 排序風險、重複項目、變異與速效項目,並依影響除以成本排列修正優先順序
  • 驗證任意物品 JSON、測試邊界情況,並評估稽核結果的可信度
  • 比較不同日期的快照,列出新增、移除與變更項目,並回顧趨勢
  • 匯出完整稽核,並產生檢查清單、取捨說明與待解問題
適用情境
適合你維護一份結構化的觀星或流星雨觀測裝備 JSON 清單,並希望助理協助稽核:缺少什麼、哪些過期、重複或超預算,以及該先修什麼。它分析你提供的資料,不會取得即時天象或天氣資訊。
執行需求
以本機 stdio 程序執行,從 npm 套件安裝;安裝與建置需要 Node.js 與 npm。未宣告驗證、環境變數或請求標頭,也未說明需要網路存取。物品 JSON 需由你自行提供。
安裝前請注意
這些工具會讀取並分析你提供的 JSON,輸出報告、清單與匯出內容;分享匯出的稽核結果前請先檢查。README 提到同一儲存庫中另有部分套件的工具仍只回傳「Not yet implemented」,使用前請確認本套件的工具能正常回應。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Meteor Shower Watch Tracker,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

awesome-servers

One repo for three families of servers, each subtree keeping its own layout and tooling so it can still be built, run and published on its own.

SubtreeWhat it holdsRun one
mcp/338 TypeScript MCP servers, plus 1107 published packages in published/cd mcp/servers/<slug> && npm install && npm run build
acp/79 Python ACP agentspython3 acp/agents/<name>/agent.py
a2a/37 Python A2A servers plus the shared a2a_kitpython3 a2a/servers/<name>/server.py
watchd/a threshold watcher that runs the feeds between editor sessionspython3 watchd/watchd.py --config conditions.json --loop
site/the published site: registry with search, the public-feed atlas, watchd planshttps://mrfentmen.github.io/awesome-servers/

Most servers read public data with no key of their own; the ones wrapping a vendor API take that vendor's key. Nothing in this repo asks a caller to pay. On 2026-10-17 the licence machinery was removed for good: the per-tool src/license.ts gates are gone from the MCP servers, and the A2A and ACP trees no longer carry the hosted licence-gateway half — the skills that used it now answer with an explicit not-implemented stub. Nothing here asks a caller to pay, and nothing they run is refused with a buy link.

Nothing here is generated: each subtree's README says what its servers read, and every server has its own unit tests (mcp/servers/<slug>/tests, acp/agents/<name>/tests, a2a/servers/<name>/tests) plus a live smoke check (tools/smoke*.py, a2a/tools/smoke_all.py).

Novel and original

Nearly all of this is first-of-its-kind work, not a port of an existing catalogue. Before each server or agent was built, it was checked against the official tool lists (the MCP registries, agentclientprotocol.com's agent list and registry) and a live GitHub search for the same domain, and the research logs record what was found and why it still counted as missing — see mcp/MISSING.md, acp/MISSING.md and a2a/docs/. Highlights:

  • The MCP side holds TypeScript servers, one npm package each, and 1039 published packages under published/; mcp/MISSING.md documents the check that preceded every build: what was searched, what was skipped and why the domain still counted as uncovered.
  • On the ACP side there were zero domain agents before this repo — every agent on the official list was a coding agent. These 79 Python agents are the first non-coding ACP agents, and several use protocol surfaces no other agent uses in production (session/request_permission for dataset reads, fs/write_text_file for a briefing file, session/cancel for a conditional watch, image content blocks, a live SSE push feed), each proved-unused in the wild by search at build time. Two more firsts carry their own proof: the orchestrator is an agent whose feeds are agents — it spawns sibling repo agents as real ACP child processes and merges their answers — and the nyc pack is the first multi-agency city surface.
  • acp/MISSING.md doubles as the public-feed atlas: every keyless feed probed live, with its date, what it answered and whether it still works. The published site renders that table at https://mrfentmen.github.io/awesome-servers/atlas.html.
  • The pattern across all three subtrees is the same thesis: wrap one real, keyless public dataset, answer honestly about what the feed did and did not say, and keep the whole thing small, tested and self-contained.

Publishing

  • MCP servers publish from mcp/servers/<slug> (its own package.json, version and README).
  • ACP and A2A servers are repo-run today (Python, no packaging step).

Built on top of it

Creatures that use this corpus as their world live in the sibling repo mrfentmen/superagents (public, with its own claim-check in MISSING.md):

  • polymath — routes your question to the most fitting agents of this repo, spawns each as a real ACP child process, and merges the answers into one brief with per-row citations; a sibling that fails appears as a named row, never silence. Its registry is a data file and its ranking is deterministic word-scoring, not a model opinion.
  • sentry — one plain sentence ("watch air quality in Denver over 150") becomes a tracked watch: a permission-asked protocol write produces the conditions file this repo's watchd/ obeys unchanged, plus the activation lines. Checks it can author today: air thresholds, quake magnitudes within a radius, river gauges at flood stage.
  • fedora hat guy — the persona agent in his own repo mrfentmen/fedora-hat: says "never miss" and means it — one sentence installs the full crown of watches (air + quakes, gauge-named flood) in one permissioned write, and your other questions are forwarded to the siblings above with every row cited.
  • instink — the instinct agent in his own repo mrfentmen/instink: compiles a skill into a reflex — a matcher plus the answer it fires, with hit/miss counters and honest promotion/demotion. The skill doc stays one step away, never deleted.
  • contextink — the context agent in his own repo mrfentmen/contextink: you say "do this" and it acquires the context from the repo, git, and recent files so you don't have to explain it; asks only the minimal high-information-gain questions when acquisition fails.
  • rewind — the replay agent in his own repo mrfentmen/rewind: replays agent runs and mutates one variable to see what would have happened. Replay + mutate + diff for agent traces.
  • scopink — the scope agent in his own repo mrfentmen/scopink: checks if an action is within the scope of what was asked. Detects scope creep in agent plans.
  • curious — the curiosity agent in his own repo mrfentmen/curious: proactively seeks information it doesn't have. Scans for knowledge gaps, seeks answers, learns facts.
  • bored — the idle agent in his own repo mrfentmen/bored: uses idle time productively. Consolidates memories, explores areas, prepares for tasks.

Point the polymath at a checkout of this repo with AWESOME_SERVERS_HOME=$PWD/awesome-servers and it federates across the two repos live.

Published snapshot (published/)

published/ holds one directory per npm package, byte-for-byte what the registry serves: 1039 packages, every version matching npm latest.

  • published/INDEX.md is generated from the tree by python3 scripts/index-published.py.
  • scripts/sync-published-snapshot.py re-downloads every package from npm; run it only when every local fix has been published, because it overwrites dist/ from the tarballs.
  • One package carries a licence gate (MCP_LICENSE_KEY): @mrfentmen/vg-resource-mcp. Another 495 still ship tools that answer Not yet implemented; published/INDEX.md lists every one of them.
  • Every package links to this repo (mrfentmen/awesome-servers) as its source.

servers/ holds the older per-server source that predates the snapshot. Where the two disagree, published/ is what users actually install.

來源:README.md,提交 cc63360

工具

25

inventory_stargazing_stargazing_meteor_shower_watch_track

Count the meteor shower watch item collection by category. Returns spend, quantity, freshness and days since activity.

輸入參數cwdpathitemstargetcontent

score_stargazing_stargazing_meteor_shower_watch_track_readiness

Score meteor shower watch item readiness from 0 to 100 for coverage, condition, data quality, freshness and days since activity.

輸入參數cwdpathitemstargetcontent

audit_stargazing_stargazing_meteor_shower_watch_track_coverage

Show category coverage for the meteor shower watch item collection as 0-1 ratios, plus unknown categories.

輸入參數cwdpathitemstargetcontent

flag_stargazing_stargazing_meteor_shower_watch_track_gaps

List missing categories, expired items, expiring items and dependency gaps for the meteor shower watch item collection.

輸入參數cwdpathitemstargetcontent

rank_stargazing_stargazing_meteor_shower_watch_track_risks

Rank risks: low coverage, expired stock, budget overruns, duplicates, worn items and missing data.

輸入參數cwdpathitemstargetcontent

check_stargazing_stargazing_meteor_shower_watch_track_constraints

Check the meteor shower watch item collection against item cap, budget, coverage, expiry and metric targets.

輸入參數cwdpathitemstargetcontent

compare_stargazing_stargazing_meteor_shower_watch_track_baseline

Compare category counts with the configured baseline and show surplus or shortfall.

輸入參數cwdpathitemstargetcontent

estimate_stargazing_stargazing_meteor_shower_watch_track_service_gap

Calculate days since activity for every meteor shower watch item, with mean and target pass count.

輸入參數cwdpathitemstargetcontent

find_stargazing_stargazing_meteor_shower_watch_track_quick_wins

Find low-effort fixes: small category gaps, missing data, expired items and duplicates.

輸入參數cwdpathitemstargetcontent

map_stargazing_stargazing_meteor_shower_watch_track_dependencies

Map collection dependencies: which configured groups are present, how many items cover them and what is missing.

輸入參數cwdpathitemstargetcontent

test_stargazing_stargazing_meteor_shower_watch_track_edge_cases

Test edge cases: empty collection, one item, duplicate ids, zero cost, expired items, missing dates and unknown categories.

輸入參數cwdpathitemstargetcontent

summarize_stargazing_stargazing_meteor_shower_watch_track_findings

Summarize the meteor shower watch item audit: counts, top gaps, top risks and data issues.

輸入參數cwdpathitemstargetcontent

prioritize_stargazing_stargazing_meteor_shower_watch_track_fixes

Rank fixes by impact divided by effort. Returns a shortlist and the next five actions.

輸入參數cwdpathitemstargetcontent

validate_stargazing_stargazing_meteor_shower_watch_track_inputs

Validate arbitrary meteor shower watch item JSON, report schema errors and warnings, and count valid items.

輸入參數cwdpathitemscontent

detect_stargazing_stargazing_meteor_shower_watch_track_duplicates

Group meteor shower watch item items with the same category and normalized name. Shows ids and extra copies.

輸入參數cwdpathitemstargetcontent

measure_stargazing_stargazing_meteor_shower_watch_track_variance

Measure days since activity spread, category-count variance and tag diversity.

輸入參數cwdpathitemstargetcontent

benchmark_stargazing_stargazing_meteor_shower_watch_track_options

Benchmark lean, balanced and full collection sizes, plus readiness, coverage, metric and data targets.

輸入參數cwdpathitemstargetcontent

explain_stargazing_stargazing_meteor_shower_watch_track_tradeoffs

Explain the real tradeoffs: size vs coverage, cost vs use, freshness vs stock and data quality vs speed.

輸入參數cwdpathitemstargetcontent

draft_stargazing_stargazing_meteor_shower_watch_track_checklist

Draft a practical checklist from gaps, high risks, missing data and budget.

輸入參數cwdpathitemstargetcontent

export_stargazing_stargazing_meteor_shower_watch_track_audit

Export the full meteor shower watch item audit: target, metrics, gaps, risks, constraints, duplicates, benchmark and next steps.

輸入參數cwdpathitemstargetcontent

track_stargazing_stargazing_meteor_shower_watch_track_changes

Compare two meteor shower watch item snapshots by item id and return added, removed and changed items.

輸入參數after必填before必填

review_stargazing_stargazing_meteor_shower_watch_track_history

Review dated meteor shower watch item snapshots and return readiness, cost and metric trends from first to last.

輸入參數targethistory必填

score_stargazing_stargazing_meteor_shower_watch_track_confidence

Score how much the audit can be trusted from data completeness, item count, cost coverage and quantity coverage.

輸入參數cwdpathitemstargetcontent

recommend_stargazing_stargazing_meteor_shower_watch_track_next_steps

Recommend the next five actions from the ranked fix list, with quick wins alongside.

輸入參數cwdpathitemstargetcontent

open_stargazing_stargazing_meteor_shower_watch_track_questions

List open questions that block a better audit: budget, data, expiry, duplicates and unknown categories.

輸入參數cwdpathitemstargetcontent

版本歷史

1
  1. v1.0.0最新Nov 20, 2026

評分

已滿足適用檢查項的 80%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分
  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。

其他 Watch 整合