Meteor Shower Watch Planner

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Nov 21, 2026

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

The publisher's own server: watch.diy – DIY Store Finder

VerifiedSTDIODesktop onlyLocation & LifestyleData & Analytics

Overview

AI-generated overview

Audits a local JSON collection of meteor shower watch items, scoring readiness, coverage, gaps, risks and next steps through 25 tools.

What you can do
  • Inventory and score the item collection: counts by category, readiness 0-100, coverage ratios, baseline comparison
  • Flag problems: missing categories, expired or expiring items, duplicates, dependency gaps, ranked risks
  • Check constraints and targets: item cap, budget, coverage, expiry and metric targets, days to expiry
  • Validate and test input JSON: schema errors and warnings, edge cases, variance and tag diversity
  • Plan and explain: benchmark lean/balanced/full options, tradeoffs, prioritized fixes, checklist, next five actions
  • Track and export: compare two snapshots, review dated history trends, export the full audit
When to use it
Useful when you keep a meteor shower watching plan or gear list as JSON and want an assistant to audit it: what is missing, what is expired, what it costs, how ready you are, and what to fix first. Also handy for comparing snapshots over time before a trip.
Requirements
Runs as a local stdio process installed from the npm package, so Node.js and npm are needed. No authentication, environment variables or headers are declared. The assistant supplies the item JSON to the tools.
Before you install
The tools analyze data you pass in; the README notes that some packages in the same repository still ship tools that answer "Not yet implemented", so verify the tools respond before relying on them. No credentials, payments or third-party data transfer are declared.

Installation

In SourceWeft

  1. Open Meteor Shower Watch Planner in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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.

Source: README.md at commit cc63360

Tools

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.

Parameterscwdpathitemstargetcontent

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.

Parameterscwdpathitemstargetcontent

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.

Parameterscwdpathitemstargetcontent

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.

Parameterscwdpathitemstargetcontent

rank_stargazing_stargazing_meteor_shower_watch_plan_risks

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

Parameterscwdpathitemstargetcontent

check_stargazing_stargazing_meteor_shower_watch_plan_constraints

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

Parameterscwdpathitemstargetcontent

compare_stargazing_stargazing_meteor_shower_watch_plan_baseline

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

Parameterscwdpathitemstargetcontent

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.

Parameterscwdpathitemstargetcontent

find_stargazing_stargazing_meteor_shower_watch_plan_quick_wins

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

Parameterscwdpathitemstargetcontent

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.

Parameterscwdpathitemstargetcontent

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.

Parameterscwdpathitemstargetcontent

summarize_stargazing_stargazing_meteor_shower_watch_plan_findings

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

Parameterscwdpathitemstargetcontent

prioritize_stargazing_stargazing_meteor_shower_watch_plan_fixes

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

Parameterscwdpathitemstargetcontent

validate_stargazing_stargazing_meteor_shower_watch_plan_inputs

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

Parameterscwdpathitemscontent

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.

Parameterscwdpathitemstargetcontent

measure_stargazing_stargazing_meteor_shower_watch_plan_variance

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

Parameterscwdpathitemstargetcontent

benchmark_stargazing_stargazing_meteor_shower_watch_plan_options

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

Parameterscwdpathitemstargetcontent

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.

Parameterscwdpathitemstargetcontent

draft_stargazing_stargazing_meteor_shower_watch_plan_checklist

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

Parameterscwdpathitemstargetcontent

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.

Parameterscwdpathitemstargetcontent

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.

Parametersafterrequiredbeforerequired

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.

Parameterstargethistoryrequired

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.

Parameterscwdpathitemstargetcontent

recommend_stargazing_stargazing_meteor_shower_watch_plan_next_steps

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

Parameterscwdpathitemstargetcontent

open_stargazing_stargazing_meteor_shower_watch_plan_questions

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

Parameterscwdpathitemstargetcontent

Version history

1
  1. v1.0.0LatestNov 20, 2026

Score

80% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Watch integrations