Home / MCP registry index / com.little-works/discover

Little Works

com.little-works/discover in the official MCP registry. Endpoint https://little-works.com/mcp.

The registry describes it as: Discover: source people by skill, projects, recipes, music, materials, book, doctors, requests.

We read its 72 tools on 2026-11-14. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again about every two weeks.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code
claude mcp add --transport http discover https://little-works.com/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "discover": {
      "url": "https://little-works.com/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"discover","type":"http","url":"https://little-works.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard
claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

discover_capabilities discover_browse_types discover_search discover_browse_places source_people who_can_do get_person_proof find_doctors listen_music query_outcomes get_outcome list_coverage sample_before_after export_outcome_schema export_outcomes list_projects get_project list_recipes get_recipe list_requests get_request list_appointments get_appointment list_music get_music get_profile get_listing_by_url list_materials get_material search_materials list_materials_places source_materials_for_job quote_materials_cart list_manufacturers get_manufacturer materials_order_status materials_commerce_capabilities get_anything get_anything_capabilities list_booking_services get_booking_slots get_booking_confirm_link match_proof hire_trade start_recipe start_project list_cook_starters list_build_starters get_public_share_url get_seo_summary list_sitemap_priorities list_credentials list_work_experience list_portfolio list_info_pages get_hold_status create_booking buy_project buy_recipe buy_material and 12 more

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-14): a18ce7ea3995eca7. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/com-little-works-discover/badge.svg)](https://lazaretto.dev/mcp-registry/com-little-works-discover)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Music and podcasts MCP servers

Profullstack
com.profullstack/profullstack
153 tools, nothing matched
2026-11-12
Podcast Parser
io.github.pipeworx-io/podcast-parser
52 tools, nothing matched
2026-10-30
Pod Researcher
io.github.pipeworx-io/pod-researcher
52 tools, nothing matched
2026-10-30
PodPitch
io.github.nealshulman/podpitch
51 tools, nothing matched
2026-11-11
Fyyd
io.github.pipeworx-io/fyyd
51 tools, nothing matched
2026-11-12
Spotify
io.github.pipeworx-io/spotify
50 tools, nothing matched
2026-10-30