Meteor Shower Watch Planner

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 由助手传入工具。
安装前请注意
这些工具只分析你传入的数据;README 提到同一仓库中仍有部分包的工具只返回“Not yet implemented”,使用前请先确认工具能正常响应。未声明需要凭据、付费或向第三方传输数据。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Meteor Shower Watch Planner,将其添加到工作区。
  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_plan

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

输入参数cwdpathitemstargetcontent

score_stargazing_stargazing_meteor_shower_watch_plan_readiness

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

输入参数cwdpathitemstargetcontent

audit_stargazing_stargazing_meteor_shower_watch_plan_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_plan_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_plan_risks

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

输入参数cwdpathitemstargetcontent

check_stargazing_stargazing_meteor_shower_watch_plan_constraints

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

输入参数cwdpathitemstargetcontent

compare_stargazing_stargazing_meteor_shower_watch_plan_baseline

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

输入参数cwdpathitemstargetcontent

estimate_stargazing_stargazing_meteor_shower_watch_plan_days_to_expiry

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

输入参数cwdpathitemstargetcontent

find_stargazing_stargazing_meteor_shower_watch_plan_quick_wins

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

输入参数cwdpathitemstargetcontent

map_stargazing_stargazing_meteor_shower_watch_plan_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_plan_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_plan_findings

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

输入参数cwdpathitemstargetcontent

prioritize_stargazing_stargazing_meteor_shower_watch_plan_fixes

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

输入参数cwdpathitemstargetcontent

validate_stargazing_stargazing_meteor_shower_watch_plan_inputs

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

输入参数cwdpathitemscontent

detect_stargazing_stargazing_meteor_shower_watch_plan_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_plan_variance

Measure days to deadline spread, category-count variance and tag diversity.

输入参数cwdpathitemstargetcontent

benchmark_stargazing_stargazing_meteor_shower_watch_plan_options

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

输入参数cwdpathitemstargetcontent

explain_stargazing_stargazing_meteor_shower_watch_plan_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_plan_checklist

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

输入参数cwdpathitemstargetcontent

export_stargazing_stargazing_meteor_shower_watch_plan_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_plan_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_plan_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_plan_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_plan_next_steps

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

输入参数cwdpathitemstargetcontent

open_stargazing_stargazing_meteor_shower_watch_plan_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 集成