AgentWire is an index of shipped agent tooling, and each entry can carry a curated list, a Hacker News thread, or repository velocity as evidence. Engineers use it to find repositories that exist, were released, and can be inspected before choosing a tool.
The problem
A repository can collect four hundred stars for two years without anyone revisiting it. A single Hacker News thread can come from the author's friends.
Announcements, roadmaps, specifications without implementations, placeholders, and abandoned archives all attract attention. None proves that somebody can clone the repository today.
AgentWire keeps those signals attached to the entry instead of treating one popular signal as enough.
How AgentWire works
AgentWire currently brings together New tools, Context Window, ToolDrift, and StillShipping. The site uses Next.js, React, TypeScript, and Supabase, with committed JSON files as fallbacks for the main index.
AgentWire reads agentwire_posts from Supabase in pages of up to 1,000 rows. If the database read fails, it uses src/data/posts.json.
AgentWire reads ctxwindow_posts, tooldrift_tools, tooldrift_changelog, tooldrift_leaderboard, and stillshipping_tools in parallel. A failed read returns an empty list for that section.
AgentWire converts each source row into a shared record with a section, type, title, detail, date, status, and searchable text.
The front page merges the four section records by date and keeps 24 rows per section list.
The board reads the verification record for each New tools entry. Its score uses the last commit, commits in 90 days, last release, issue close time, licence, and the first install command in the README.
check-verified.mjs rejects records with impossible values, missing source URLs, stale readings, or a score that does not match its band.
The index keeps the source description and the operational reading separate. The first comes from the repository owner, while the second records what the health check read and where it read it.
A worked example
The health record for KnockOutEZ/wigolo records npx wigolo as a resolved npm install command. The record also keeps the registry source URL, the package name, the version, and whether the repository has an examples directory.
That gives an entry two different kinds of information. The index can show why the repository appeared, while the verification record can show whether its documented install package resolved when AgentWire checked it.
How it compares
AgentIndex is a directory for AI agents, MCP servers, and .cursorrules. It offers category search, install commands, daily updates, editor picks, and a comparison view. Pick AgentIndex when you want to search a broad catalogue and copy an install command.
Awesome MCP Servers is a hand-curated, link-checked catalogue focused on Model Context Protocol servers. It keeps structured data in data/servers.json, publishes a JSON API, and lists client configurations for hosted servers.
AgentWire covers MCP servers alongside coding-agent harnesses, agent frameworks, and related tooling. Its own entry rule requires two independent signals, while its health record stays explicit about what it did not test.
Limits
AgentWire does not run, benchmark, or review the tools it shares. It does not state that an entry works or holds up.
The index reflects what its source accounts published. A reader still needs the repository, documentation, and tests for a technical evaluation.
Try it
Start with AgentWire's search page and enter a repository name. The result can lead you to the entry, its signals, and the verification record.
Next up: Tools worth trying
Friday's edition is next. 🔗 Explore the editions →
Top comments (0)