keith-apis-mcp
Related Servers
Alternatives to keith-apis-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceFetch any web page as clean Markdown or plain text, split it into heading-aware, token-bounded RAG chunks, convert raw HTML, and read page metadata. Uses the Web2MD API on RapidAPI with your own key (free BASIC plan).44153 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and LLM pipelines to fetch and crawl web pages, extract readable content, and convert it into clean Markdown with preserved links while minimizing token usage.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to read clean Markdown from any URL and assess source quality with AI-readability scores.629 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to fetch public web pages and return their main content as clean Markdown, including JavaScript-rendered pages with navigation, ads, and boilerplate stripped. Supports OAuth sign-in and a read-only tool for pulling docs, articles, and product pages into chat or knowledge bases.289 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI editors and agents to read public web pages as clean Markdown and convert URLs, HTML, or Markdown into PDF, Word, Markdown, HTML, or JSON documents.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to extract clean LLM-ready markdown and readable articles from web pages, parse metadata, tables, links, feeds, and contact info, audit paywalls, SEO, and XSS, and access these tools via Streamable HTTP or a stdio bridge.112MIT
TDQS
Scored across 11 tools
Within each domain cluster the tools are clearly distinct: parse_job_posting vs parse_job_postings_batch (single vs batch), fetch_url_as_markdown vs html_to_markdown (fetch vs local convert), rate_matches vs predict_match. The only mild confusion is fetch_url_as_markdown vs html_to_markdown, but descriptions clarify that one fetches and one doesn't.
Almost all tools use snake_case verb_noun phrasing (parse_resume, get_link_preview, generate_og_image, match_resume_to_job). Minor deviations are noun-first names like html_to_markdown, but overall the convention is predictable and readable.
11 tools is a well-scoped count and each tool earns its place within its own cluster. The issue is not the number but the unrelatedness of the clusters, so the count itself is reasonable.
The recruiting pipeline (parse resume, parse job posting, batch, match) and the web-content cluster (fetch, convert, preview, OG image) are fairly complete, and the ratings trio is self-contained. However, the server is a grab-bag of three unrelated domains with no tool bridging them, making overall 'purpose' coverage hard to assess and leaving each domain somewhat shallow.