Outreacher

A working server exists but somebody other than the vendor built it. It can be abandoned without the vendor noticing. The status was established on 2026-09-12 and the MCP URL has not been probed live yet.

mcp_status, verbatim from the file:

community

mcp_url, verbatim from the file:

https://github.com/technicallypete/outreacher

• https://github.com/technicallypete/outreacher

A tool below is one the server NAMES. Nobody has called it. That is the same two tier honesty rule the rest of the directory runs on: a named tool is research, and BENCH-TESTED stays the only claim that anybody ran anything.

This list came from a repo the vendor does not own. Those are that author's tools for the vendor's API, not the vendor's own published surface, and the two must not be read as the same thing.

• create_campaign
  No description was recorded with the name.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• create_followup_note
  No description was recorded with the name.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• debug_env
  No description was recorded with the name.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• get_campaign
  No description was recorded with the name.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• get_company
  No description was recorded with the name.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• get_lead
  No description was recorded with the name.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• import_csv
  No description was recorded with the name.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• import_csv_file
  No description was recorded with the name.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• import_leads
  No description was recorded with the name.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• import_leads_file
  No description was recorded with the name.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• list_campaigns
  No description was recorded with the name.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• rename_campaign
  No description was recorded with the name.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• search_companies
  No description was recorded with the name.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• search_leads
  No description was recorded with the name.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface
• update_lead_status
  No description was recorded with the name.
  evidence: in the server source · calling it reads · from a third party repo, so these are that author's tools, not the vendor's published surface

141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. Every name across every server is on the tools index.

No CLI found by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence.

api_gate, verbatim from the file:

unknown

949 of 1252 entries carry an unknown gate. Unknown is a legal answer and it ships as unknown rather than as a guess.

https://github.com/docs

No documentation text is reproduced anywhere on this site. Read the vendor page for the prose. The structured docs digest specced in SPEC section 3 has not been built or crawled: docs_digest is null on every entry in this build.

Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.

The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.

A github.com URL already appears somewhere in this entry, which is a seed for that rail and not a measurement of repo health:

• https://github.com/developers
• https://github.com/docs
• https://github.com/technicallypete/outreacher

No GitHub organisation could be tied to github.com with evidence on 2026-09-15.

Recorded by the harvest: not checked: gh CLI missing or not logged in.

No job tag on this entry.

981 of 1,252 entries are untagged. An empty list here means nobody has tagged this, not that the tool does nothing. The vocabulary is closed, so a tool whose job is genuinely not in it stays blank rather than being forced into the nearest tag.

• https://github.com/technicallypete/outreacher
• https://github.com/docs
• https://github.com/developers

3 source URLs. Raw sources field, verbatim:

https://github.com/technicallypete/outreacher, https://github.com/docs, https://github.com/developers

Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.